X formerly Twitter announces 1 million dollar prize for top article in 2026 to boost long form creators

X (Formerly Twitter) Hit by Major Global Outage on January 16, 2026

New York / Washington DC, January 17, 2026 – Elon Musk’s X platform (formerly Twitter) faced a significant global disruption on Friday, January 16, 2026, marking the second major outage in under a week. The issues primarily hit US users hard, with peak reports exceeding 200,000 globally and tens of thousands in the US alone. Here’s a detailed, EST-based timeline of the event based on Downdetector spikes, user reports, and tech coverage.

EST Timeline of the January 16, 2026 X Outage

  • Around 9:30–10:00 AM EST — Initial surge in outage reports begins. Users start seeing blank screens, endless loading spinners, “Something went wrong” errors, and inability to refresh feeds, post, or load timelines on both the X app (iOS/Android) and web (x.com/twitter). Downdetector shows early spikes, with problems affecting app (~56-59%), website (~26-33%), and server connections (~10-15%).
  • ~10:00–10:15 AM EST — Outage peaks sharply. Downdetector records over 77,000–78,000 US reports at 10:15 AM EST, with some sources citing peaks up to 200,000+ globally (including high volumes from New York, Los Angeles, Chicago, Dallas, and Houston). Grok AI chatbot also impacted, with separate spikes in reports. Cisco ThousandEyes noted over 600 problematic X servers worldwide.
  • ~10:15–10:45 AM EST — Issues persist at high levels. Reports drop slightly to around 63,000 in the US by 10:45 AM EST. Users report intermittent partial loads (e.g., old posts visible but no new content), Cloudflare errors in some cases (though not confirmed as root cause), and widespread frustration. Many turn to Bluesky or Reddit for outage memes and updates.
  • ~10:45–11:25 AM EST — Recovery begins. Downdetector figures decline rapidly—down to ~5,700–6,000 US reports by 11:25 AM EST. Most users regain access to feeds, posting, and Grok, though some experience lingering glitches (e.g., delayed notifications or slow refreshes).
  • By ~11:45 AM–12:00 PM EST — Service largely restored for the majority. Reports fall to low thousands globally. X appears stable for most by early afternoon EST, with no major recurrences reported through the rest of the day.

Total Duration: Bulk of the outage lasted ~1.5–2 hours (from ~10:00 AM to ~11:45–12:00 PM EST), with intermittent issues for some users slightly longer.

Key Impacts and Details

  • Affected Areas: Heaviest in the US (top cities: New York, Los Angeles, Chicago, Dallas, Houston), but global—including UK, Canada, India, Australia, and Japan.
  • Symptoms: Blank/error screens, timelines not loading, failed posts/refreshes, Grok unavailability.
  • Cause: No official explanation from X or Elon Musk as of January 17, 2026. Likely internal backend/server issues or infrastructure strain (possibly from reduced engineering staff post-2022 acquisition). Not linked to cyberattacks or major external providers like Cloudflare this time (unlike November 2025 incidents).
  • Context: Followed a smaller outage on January 13, 2026 (~28,000+ reports, resolved in ~1 hour). Amid ongoing platform scrutiny, including Grok controversies.

X remains stable as of January 17, 2026 (early morning EST / afternoon IST). For real-time checks, use Downdetector or X’s status updates.

Sources: Downdetector data, Reuters, TechRadar, Tom’s Guide, The Verge, Mashable, Variety, USA Today, and user reports. No official X postmortem released.

I’m Ethan, and I write about the tech that’s actually going to change how we live — not the stuff that just sounds impressive in a press release. I cover AI, EVs, robotics, and future tech for VFuture Media. I was on the ground at CES 2026 in Las Vegas, walking the show floor so I could give you a real read on what matters and what’s just noise. Follow me on X for daily takes.

You made it to the end, which means you actually care about this stuff. So do we. Check out our AI and EV sections for more stories worth your time.

Post navigation

Leave a Comment

Leave a Reply

Your email address will not be published. Required fields are marked *