New! Check service status instantly with our Chrome extension
Real-time social networking platform for sharing news and updates.
There were 52 X outages since March 2025 which are summarized below, including incident details, duration, and resolution information.
Not working for you?
A brief global outage on X disrupted posting and feed rendering, with users reporting posts not loading and error messages such as 'something went wrong.' The disruption lasted about five minutes, beginning around and ending by . StatusGator detected the outage at as activity spiked across multiple regions.
X experienced a global outage where tweets and posts failed to load across regions. Users reported the main feed, timelines, and other page content not rendering, and in some cases login content not appearing, effectively disrupting everyday usage for people around the world.
X users worldwide faced an outage that blocked posting and prevented posts from loading, with timelines and mobile/web apps failing to respond. The disruption appeared global, with reports of content not loading and apps not opening from regions across North America, Europe, and beyond. StatusGator flagged the issue, with the problem detected at due to connection errors and the early warning signal running until . Impact began around and persisted for several hours into the afternoon.
Users across the globe reported authentication problems as sign-in attempts were interrupted by repeated YubiKey prompts. StatusGator’s Early Warning Signal appeared first at , signaling the issue before any provider updates were visible. The disruption began around and persisted until about , with many users experiencing sign-in loops and repeated YubiKey prompts across multiple regions.
Users across multiple regions reported that the X app became inaccessible and would not refresh content, starting around . StatusGator logged an Early Warning Signal at , indicating the issue before formal acknowledgment, and many users in Europe, the Middle East, and beyond noted pages failing to load or update. The disruption persisted for about an hour and was resolved by .
Because X has no official status page, updates came primarily from StatusGator and user reports rather than a published incident note. The outage affected the app frontend and related page-loading and refresh functionality, causing experiences such as posts not posting and pages not loading correctly. With a global pattern of reports from cities across Europe, Asia, and the Americas, the outage appeared widespread before service restoration. Root cause has not been disclosed in the available communications.
On , StatusGator detected an outage when X's website became unavailable due to a server error. The disruption appeared global, with users reporting that the site was inaccessible and core features such as the timeline, posting, and login failed, often returning HTTP 500 errors. The incident lasted until , spanning roughly 37 minutes. This early detection occurred ahead of any official acknowledgment from a public status page.
X does not maintain an official public status page, so there were no provider updates published during the outage.
X experienced a content loading outage that prevented Indonesian users from loading posts or refreshing timelines. Reports described errors like failing to load content, inability to post or refresh, and in some cases DNS-related messages such as origin DNS errors or generic try again prompts. The disruption appeared concentrated in Indonesia, with users across several cities affected.
X users experienced an outage where posts, pages, and timelines would not load, affecting both mobile and desktop clients. The disruption began around and persisted for about an hour, with service returning toward normal by . A surge in user reports around to indicated broad impact across locations.
StatusGator recorded an Early Warning Signal at , reflecting early user reports before an official acknowledgement. There was no published official status page from X during the incident, and no public root-cause details were provided. The incident ended by as services resumed and posts and feeds loaded again.
A brief outage affected loading of posts on X, with user reports coming from multiple U.S. locations. The issue began around and persisted for roughly two to three minutes, during which users could not load new posts. StatusGator detected an Early Warning Signal at , with the issue resolving by .
Users around the world faced sign-in failures on X, with many unable to log in or reach the login screen. The authentication flow appeared to be the impacted component, producing errors such as 'Oops, something went wrong' and other login errors. The incident began with initial user reports around and intensified through the afternoon, lasting for several hours. StatusGator detected the issue starting at and the Early Warning Signal remained active until .
The outage was global in scope, with reports spanning multiple regions, including North America, Europe, and Asia, indicating broad authentication problems rather than a localized incident.
Looking for more X outage stats?
Get real-time insights and historical data on X outages.
X outage stats
