X Outage History

Users around the world were unable to access the X login page or complete sign-ins. The outage appears to have begun with early user reports around 7:45 PM UTC, with a rapid surge by 8:45 PM UTC as more people reported login failures. Symptoms included pages showing as down, login errors, or the sign-in flow failing to load, effectively blocking access to X accounts and related features for many users.

Status updates were not published on an official status page. StatusGator recorded an Early Warning Signal at 7:59 PM UTC noting login page unavailability ahead of any provider acknowledgment. The incident was described by user reports as global in scope and ongoing through the latest observations, with no restoration timeline published on a provider page.

Impact and scope: The user reports indicate a broad outage affecting the sign-in experience for an extended period, with the login page repeatedly returning down messages or failing to initialize as of 9:00 PM UTC. The issue appeared global rather than region-specific, limiting access to X accounts and related features for many users during the incident.

Global users reported that X’s website would not load and core interactions—posting, timelines, and login—were unreliable. The outage began around 2:56 PM UTC based on StatusGator’s early-warning signal and spread across regions, with activity peaking around 3:15 PM UTC as more users encountered loading errors and missing content in feeds and timelines. The impact was broad, affecting users across North America, Europe, Africa, and beyond, and persisted for most of the afternoon.

An outage hit X, preventing the feed and posts from loading for many users across the globe. Web and mobile clients displayed blank pages and error messages, making it difficult to view or interact with posts. StatusGator logged an Early Warning Signal when the issue began around 8:50 PM UTC, and the disruption persisted for about two hours, with conditions improving by 10:37 PM UTC.

Users worldwide were unable to load X's feed or sign in to the app and website. The outage began around 1:15 PM UTC and rapidly affected users across many regions, with reports of feeds not loading, login errors, and blank screens. StatusGator detected activity on the issue at Feb 16, 2026 1:28 PM UTC, roughly 13 minutes before the first wave of user reports. The impact persisted for a couple of hours and appeared to ease as network activity stabilized, with the Early Warning Signal ending at 3:24 PM UTC.

Users across multiple locations could not load the X feed, leaving posts and updates unavailable. The disruption began with an Early Warning Signal around 1:04 AM UTC and drew a flood of user reports as the issue spread. People described the feed not loading, posts not appearing, or the server not responding, with the problem affecting loading across devices and regions. The outage persisted for about 45 minutes, with visibility returning around 1:49 AM UTC.

A global outage on X left users unable to load feeds and post content. The disruption began around Feb 1, 2026 4:15 PM UTC and affected both web and mobile experiences, with timelines for feeds and posts not loading across regions. StatusGator recorded an Early Warning Signal for feed loading at Feb 1, 2026 4:22 PM UTC, and the issue persisted until Feb 1, 2026 4:33 PM UTC when services appeared to recover. The reach appeared global, with reports spanning North America, Europe, Africa, Asia, and beyond. There was no official status page published by X during the incident.

X users could not load content or posts in the X app, with the feed and individual posts failing to render. The outage appeared global, affecting users across regions. The disruption began around 3:47 AM UTC and persisted for several minutes, with reports peaking near 3:50 AM UTC before conditions began to ease around 3:53 AM UTC. StatusGator detected the issue at Jan 31, 2026 3:47 AM UTC.

X has no official status page in the data, so there were no provider updates captured during the incident and the exact cause remains unconfirmed. The rapid, global spread of reports underscores a broad impact on the user experience, with many unable to view posts, comments, or profiles during the outage.

Users worldwide faced desktop loading failures on X, with many reporting the site not loading, spinning wheels, or stuck login prompts. Some mobile users could still access X, indicating a desktop-specific issue. The impact began around 1:03 AM UTC and lasted for about an hour and a half, tapering by 2:28 AM UTC. Reports came from North America, Europe, Australia, and other regions, suggesting a broadly distributed problem rather than a single local outage.

X has no official status page providing updates, and no formal acknowledgment appears on a public page. StatusGator flagged the issue at Jan 24, 2026 1:03 AM UTC as an Early Warning Signal, indicating user-reported problems preceded official responses. The pattern of reports and the desktop-specific symptoms imply a widespread desktop experience disruption across multiple regions.

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.