X Outage History

Users on X experienced an outage affecting the ability to load tweets and replies. The disruption began around 1:38 PM UTC and appeared to ease by 2:13 PM UTC. Reports spanned multiple regions worldwide, indicating a broad impact on a core interaction feature, while other parts of the platform remained accessible in some contexts.

X has no official status page to publish updates during the event. An Early Warning Signal was detected as tweets and replies failed to load, with activity starting at 1:38 PM UTC and ending around 2:13 PM UTC. The outage lasted roughly 34 minutes, after which functionality appeared to recover.

An outage on X left users globally unable to log in and unable to load or post content. The disruption began around 4:15 PM UTC as authentication and page load failures were first reported, with many users experiencing blank screens or posts not going through. The impact intensified through the late afternoon as a broad mix of locations reported similar issues, affecting the core user experience across devices. A sharp uptick in reports around 5:15 PM UTC indicates the problem was widely felt across regions, with login and posting functions most affected and timelines not updating as expected. X did not publish any official status updates on a public page, leaving users with limited visibility into the incident while signs of ongoing disruption continued. StatusGator issued an Early Warning Signal, with issues detected at 5:14 PM UTC, about 13 minutes before official acknowledgment. This signal provided a heads up ahead of formal provider updates, but as of the latest information the incident remained unresolved on X's side and continued to impact user activity.

An outage affected X's authentication and sign-in capabilities, preventing many users from logging in or creating accounts. Web and mobile access were disrupted, with login failures and internal error messages reported across multiple regions, indicating a global impact. The disruption began around Jan 16, 2026 3:12 PM UTC and persisted for roughly five hours and 40 minutes, with a surge of user reports starting around 3:15 PM UTC and continuing through the incident. The issue was resolved by Jan 16, 2026 8:55 PM UTC.

Users on X experienced a global outage that prevented posts from loading or displaying and halted timeline updates. The impact was widely felt across regions, with reports of posts not loading, feeds not updating, and pages failing to reload. The disruption began in the early afternoon UTC and was most evident into the mid-afternoon, peaking around 2:30 PM UTC. StatusGator detected the issue starting at 1:21 PM UTC and the Early Warning Signal ran until 3:28 PM UTC as user reports surged before any official acknowledgment. There was no public official status page from X to communicate updates during the incident, and the geographic footprint appeared global based on the dispersed locations of reports.

Photos and videos on X were not loading for many users, and a number of posts and pictures failed to render. StatusGator detected the issue at Jan 12, 2026 3:41 PM UTC, ahead of any official acknowledgment from X. The earliest user reports appeared around 3:15 PM UTC, with a clear regional pattern: a large share of reports came from the Philippines (Quezon City and Metro Manila area), while a smaller set came from other regions. The disruption lasted for about 5:14 PM UTC. No official status page updates were published by X during the incident. The narrative is based on user reports and StatusGator monitoring. The pattern suggests a media delivery problem affecting the display of photos/videos rather than a complete service outage.

Users of X experienced an outage affecting the premium analytics page, with the page failing to load starting at 6:04 PM UTC and reports of 'Cannot find the page' errors. The disruption lasted about an hour, with activity tapering after 7:00 PM UTC. Reports originated from multiple regions, including North America and Europe, signaling broad reach within the premium analytics audience.

StatusGator detected the issue at Dec 5, 2025 6:04 PM UTC, ahead of any official acknowledgment from X. Because X has no official status page, users relied on StatusGator updates for visibility into the incident. The outage appears isolated to the premium analytics page rather than the entire X service.

X users faced an outage that prevented loading of timelines and posts and disrupted signup flows. The issue affected both web and app usage, with complaints of posts not loading and signup errors. Impact began around 8:30 PM UTC and persisted for a little over an hour, affecting users globally.

Users faced sign-in problems starting around 2:45 PM UTC, with authentication failures preventing login for some accounts. The issue persisted for about an hour and appeared to resolve by 3:50 PM UTC. StatusGator logged an Early Warning Signal for sign-in problems at 3:50 PM UTC.

X does not publish an official status page, so there were no provider updates to confirm root cause or remediation. The impact was limited to login access for a subset of users rather than a full service outage.

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 4:00 PM UTC and ending by 4:09 PM UTC. StatusGator detected the outage at Nov 23, 2025 4:04 PM UTC 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.