X Outage History

Impact began around 6:34 AM UTC and persisted into the morning as X users reported that timelines and posts were not loading. The experience included blank timelines, missing posts, and in some cases login issues, with a rapid surge in reports around 7:15 AM UTC indicating a broad disruption to the core feed.

Users worldwide were unable to sign in via X's web login page, with error messages and pages indicating that the login surface was down. The issue appeared limited to the web login flow, while some users reported the mobile app remained usable, suggesting a partial outage rather than a full platform failure. Reports came from many regions, indicating a global impact on the sign-in experience. The disruption lasted for several hours, with activity peaking as more users attempted to log in.

X experienced a global disruption where the website and posting features failed to load or responded sluggishly. Status activity shows an Early Warning Signal beginning at 2:56 PM UTC and ending at 4:38 PM UTC, with user reports peaking between 3:15 PM UTC and 3:30 PM UTC. Reports described not loading timelines or posts, login difficulties, and inconsistent behavior across devices (for example, some users could load content on mobile but not on desktop). The pattern suggests a widespread impact affecting core user experiences globally.

No official status updates were provided in the data, and X does not have an available status page in this feed. The volume and spread of reports indicate a broad outage affecting a large portion of users across regions and time zones, rather than a localized issue. The situation appears to have begun to subside after the mid-afternoon window, with early warning indicators concluding by 4:38 PM UTC as activity started to normalize.

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.