X Outage History

The X premium analytics page experienced an outage, preventing access for users. The issue began at 6:04 PM UTC and was resolved by 7:00 PM UTC, lasting roughly 56 minutes. Reports from multiple regions described errors like 'X will not load' or 'cannot find the page,' indicating a problem with this feature rather than a full service outage.

StatusGator detected the issue at Dec 5, 2025 6:04 PM UTC based on user reports, ahead of any provider acknowledgement; there were no published official status updates from X during the incident. The impact appears focused on the premium analytics page rather than the entire X service.

An outage on X disrupted the timeline and posting features, with users reporting signup failures and posts not loading. The outage lasted about one hour, from 8:42 PM UTC to 9:42 PM UTC, and complaints came from multiple regions, indicating broad impact.

StatusGator triggered an Early Warning Signal at Dec 3, 2025 8:42 PM UTC based on user reports, ahead of any official acknowledgment. X has no official status page, so no provider updates were published during the incident. The pattern of reports from different locales—United Kingdom, United States, and beyond—suggests a widespread disruption to timeline and posting functionality.

X users experienced sign-in problems, with reports beginning around 2:45 PM UTC and continuing until 3:50 PM UTC. The outage lasted about 1 hour and 5 minutes and prevented many users from authenticating or accessing their accounts during the period.

X did not publish any public status updates during the incident. StatusGator recorded an Early Warning Signal for sign-in problems, and the signal ended when the incident resolved at 3:50 PM UTC.

Based on the available reports, there is no clear regional outage pattern; one report mentioned India, but data is limited. Overall, this appears to be a temporary sign-in degradation rather than a full service outage.

The outage affected X users globally, with errors loading content and pages during the incident. The service was unavailable from Nov 23, 2025 4:04 PM UTC to Nov 23, 2025 4:09 PM UTC, lasting about 5 minutes. Reports indicated the issue spanned multiple regions, including North America and Europe, suggesting a broad impact.

X does not publish an official status page, and no post-incident updates were issued by the provider. StatusGator logged an Early Warning Signal at Nov 23, 2025 4:04 PM UTC based on user activity before any official acknowledgement. A noticeable volume of user reports pointed to a brief disruption across the globe before service was restored.

Users worldwide experienced an outage on X where tweets, timelines, and post content would not load. Reports described failures loading posts or the main page, with users across multiple regions including North America, Europe, Asia, and the Middle East affected. With no official status page available for this incident, there were few formal confirmations from X beyond user-reported symptoms, indicating a broad impact on core functionality.

X experienced a global outage preventing users from loading content or posting across devices. The service interruption began at 11:31 AM UTC and was resolved by 3:32 PM UTC, lasting roughly 4 hours and 1 minute. StatusGator detected the issue at Nov 18, 2025 11:31 AM UTC, ahead of any official acknowledgment. X has no official status page, so this timeline is based on user observations and StatusGator signals. Symptoms included timelines and posts failing to load, app downtime, and widespread interaction issues across regions, indicating a global impact. User reports surged in the UTC afternoon window and then tapered as recovery occurred.

X experienced login issues due to repeated YubiKey prompts, affecting users attempting to sign in. The incident appeared global, with reports from multiple regions spanning North America, Europe, and beyond, indicating widespread reach. StatusGator detected the issue based on user reports starting at Nov 12, 2025 6:07 PM UTC and the problem persisted until Nov 12, 2025 8:28 PM UTC. There were no official status updates published by X during the incident, as X has no official status page. The login workflow was affected, with users reporting loops and repeated YubiKey prompts; the incident lasted roughly 2 hours 21 minutes, with a broad distribution of reports peaking around 19:00 UTC across regions including the United States, United Kingdom, Bulgaria, Poland, Pakistan, Mexico, Sweden, Brazil and Canada.

X users experienced an outage where the X app became inaccessible and stopped refreshing, affecting users across Europe and parts of the Middle East. The outage lasted about 1 hour and 3 minutes, from 8:09 AM UTC to 9:12 AM UTC.

StatusGator detected an Early Warning Signal based on user reports starting at 8:09 AM UTC, and there were no official status updates from X during the incident. Report activity surged through the window, indicating widespread impact across multiple regions.

The X website experienced an outage starting at 9:36 PM UTC due to a server error, with users unable to access the site and encountering issues such as HTTP 500 errors and failing to load posts or feeds. The disruption appeared global, with reports spanning multiple regions in North America and Europe, indicating widespread impact. StatusGator detected the issue at Sep 3, 2025 9:36 PM UTC, ahead of any official acknowledgment. The outage lasted about 37 minutes, with restoration noted by 10:13 PM UTC.

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.