X Outage History

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 Nov 18, 2025 11:31 AM UTC due to connection errors and the early warning signal running until 3:32 PM UTC. Impact began around 11:30 AM UTC 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 6:07 PM UTC, signaling the issue before any provider updates were visible. The disruption began around 6:00 PM UTC and persisted until about 8:28 PM UTC, 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 8:09 AM UTC. StatusGator logged an Early Warning Signal at 8:09 AM UTC, 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 9:12 AM UTC.

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 Sep 3, 2025 9:36 PM UTC, 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 10:13 PM UTC, 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 2:30 PM UTC and persisted for about an hour, with service returning toward normal by 3:33 PM UTC. A surge in user reports around 3:00 PM UTC to 3:15 PM UTC indicated broad impact across locations.

StatusGator recorded an Early Warning Signal at 2:36 PM UTC, 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 3:33 PM UTC 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 9:30 PM UTC and persisted for roughly two to three minutes, during which users could not load new posts. StatusGator detected an Early Warning Signal at Jul 24, 2025 9:37 PM UTC, with the issue resolving by 9:40 PM UTC.

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 12:15 PM UTC and intensified through the afternoon, lasting for several hours. StatusGator detected the issue starting at Jul 15, 2025 1:26 PM UTC and the Early Warning Signal remained active until 4:27 PM UTC.

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.

Users across the globe encountered sign-in failures and posts loading issues on X's web platform beginning around 2:17 AM UTC. Reports described errors when signing in and attempting to load timelines or post content, effectively preventing many from using the service for hours. With no official status page available, X did not publish public updates during the incident, leaving users without formal guidance.

StatusGator detected the Early Warning Signal for problems loading posts and signing in on the web platform at 2:17 AM UTC and it remained active through 4:27 PM UTC. A broad pattern of user reports from multiple regions indicates a global impact on authentication and content interaction. The incident persisted through the afternoon with users in many time zones unable to sign in or load posts.

X experienced a brief outage where users worldwide could not load the site. Reports from North America, Europe, and Australia indicate widespread impact on accessibility across web and mobile clients. The disruption began around 1:53 PM UTC and was resolved by 2:09 PM UTC, lasting roughly 15 minutes. StatusGator recorded an Early Warning Signal at 1:53 PM UTC ahead of any provider acknowledgment. With no official status page updates from X, the community relied on user reports and StatusGator for visibility.