Social media platform
#X, formerly known as
#Twitter, suffered a major global outage starting around 6:22 PM Nepal Time on Friday evening, disrupting the experience for millions of users across the world.
While the
#platform’s homepage continued to load, users were unable to view timelines, fetch tweets, or access direct messages. The widespread error left feeds blank, prompting a wave of reports and confusion.
Outage Timeline and Impact
According to reports, the disruption began around 11:30 PM NST (May 23) and peaked by 1:16 AM NST (May 24). By early Saturday morning, users globally continued to face intermittent problems accessing their content feeds.
X confirmed the outage and attributed it to a data center issue, though further technical details have not been disclosed publicly. The company's engineering team is reportedly working to stabilize services.
Users Turn to Alternatives
With X down, frustrated users flocked to other platforms like Threads, Bluesky, and Mastodon to confirm the outage and share their reactions. The hashtag
#TwitterDown quickly trended on multiple services, reflecting the scale of the disruption.
No Localized Exception
The issue affected users globally — from Asia and Europe to the Americas — with no regional exceptions, according to third-party tracking services. Even mobile apps and third-party X clients failed to load content properly during the peak of the outage.
Company Response
X has not issued a full public statement via its blog or newswire but confirmed via limited platform updates that a data center problem was behind the disruption. No estimated time of full recovery was provided at the time of writing.
Social media platform #X, formerly known as #Twitter, suffered a major global outage starting around 6:22 PM Nepal Time on Friday evening, disrupting the experience for millions of users across the world.
While the #platform’s homepage continued to load, users were unable to view timelines, fetch tweets, or access direct messages. The widespread error left feeds blank, prompting a wave of reports and confusion.
Outage Timeline and Impact
According to reports, the disruption began around 11:30 PM NST (May 23) and peaked by 1:16 AM NST (May 24). By early Saturday morning, users globally continued to face intermittent problems accessing their content feeds.
X confirmed the outage and attributed it to a data center issue, though further technical details have not been disclosed publicly. The company's engineering team is reportedly working to stabilize services.
Users Turn to Alternatives
With X down, frustrated users flocked to other platforms like Threads, Bluesky, and Mastodon to confirm the outage and share their reactions. The hashtag #TwitterDown quickly trended on multiple services, reflecting the scale of the disruption.
No Localized Exception
The issue affected users globally — from Asia and Europe to the Americas — with no regional exceptions, according to third-party tracking services. Even mobile apps and third-party X clients failed to load content properly during the peak of the outage.
Company Response
X has not issued a full public statement via its blog or newswire but confirmed via limited platform updates that a data center problem was behind the disruption. No estimated time of full recovery was provided at the time of writing.
