X Outage History

Users across the globe report that X's app feed, home page, and the who-to-follow interface are not loading or displaying posts. In many cases the feed appears blank or the app presents onboarding or follow-suggestions screens instead of content. The issue began around 9:45 PM UTC and has affected a broad set of users across regions, with a high volume of reports arriving within minutes. StatusGator issued an Early Warning Signal at 9:49 PM UTC as reports continued to come in, indicating an ongoing disruption before any official acknowledgment. As of 10:00 PM UTC the problem remains unresolved and there have been no published updates on X's official status page.

X users around the world faced a full outage where the website and mobile app would not load content. Many reported a black screen with the X logo, while others could sign in but could not access their timeline or load new posts. The disruption began around 7:30 PM UTC and intensified later in the evening, with a heavy surge in reports by 9:00 PM UTC. StatusGator detected the issue at 8:09 PM UTC, ahead of any official acknowledgment. Some users also experienced inability to play videos. The outage appeared to persist until around 9:28 PM UTC when service activity started returning to normal.

With no official status page from X, there were no provider updates to share root cause or remediation details. The pattern across reports suggested a broad reach, affecting users across multiple regions rather than a single locale. The rapid influx of reports around the peak hour indicates a widespread disruption that impacted core content delivery and user interactions on X.

Users around the world reported that content and feeds on X were not loading, and some users could not log in. The disruption began around 11:45 PM UTC and intensified into the early hours of 1:30 AM UTC, with a clear surge in reports across multiple regions. Web and mobile experiences were affected, preventing users from posting, refreshing feeds, or accessing timelines.

X does not maintain an official status page, so StatusGator relied on user reports and monitoring signals. StatusGator detected the issue at 12:43 AM UTC, ahead of any provider acknowledgment, and the event persisted until around 1:48 AM UTC. The incident appeared global, with reports from North America, Europe, Asia, and beyond, indicating widespread impact before any formal communication from X.

Users around the world experienced a disruption on X where posts, timelines, and feeds failed to load. Many couldn't post or view their timeline, and some reported login problems. The incident began near 9:00 PM UTC and, based on a surge in user reports, persisted through the early minutes of the window. StatusGator captured an Early Warning Signal from Apr 14, 2026 9:03 PM UTC to 9:17 PM UTC as the issue unfolded. The impact was evident across regions, with users in Europe, North America, Africa, and other areas experiencing degraded or unavailable service.

Users attempting to reach X were met with pages that wouldn’t load, showing a blank screen or a centered X logo. The disruption began to appear in user reports around 9:15 PM UTC and quickly spread across regions as more people tried to access the site. StatusGator issued an Early Warning Signal at 9:25 PM UTC, roughly 10 minutes after the first reports and ahead of any public notice from X, indicating a broad impact before provider communication existed. The main homepage and core site areas were notably affected, with many experiences stuck on a black screen or loading halts that prevented normal navigation.

By around 11:05 PM UTC, the issue had largely abated, with reporting activity subsiding and access returning to normal for most users.

X users experienced failures loading their feed and direct messages, with posts not loading and messages not retrievable across multiple regions. The issue appears to have started around 5:00 PM UTC and persisted through the evening as activity remained elevated in reports. StatusGator detected feed and message loading issues at 6:04 PM UTC, ahead of any provider communications, and the problem continued until around 11:12 PM UTC.

Users on X experienced an outage where feeds, posts, and comments would not load or refresh, impacting the core timeline and interaction features. The disruption appeared global, with reports from multiple regions indicating that the home feed, for-you feed, and comment threads were inaccessible for several hours. StatusGator logged an Early Warning Signal for feeds and posts not loading, which ran from 9:18 AM UTC to 1:06 PM UTC. Impact appears to have begun around 8:15 AM UTC, with user reports accumulating through the late morning as the issue persisted.

Users across North America, Europe, Asia, Africa, and Oceania reported that the X home feed would not load or refresh, leaving timelines stagnant and posts not appearing. The disruption began around 7:30 AM UTC and persisted for a little over two hours, with activity peaking as the day progressed. Experience varied, but many encountered slow loading, missing updates, and difficulties posting or replying.

Users across the globe were unable to load posts or access their feeds on X app and website, with timelines and profiles failing to load and posting features disabled. The disruption began at 12:37 AM UTC and grew over the next hour, as reports surged from regions including North America, Europe, the Middle East, and Asia-Pacific. The outage affected core social interactions, effectively preventing users from seeing new posts, loading timelines, or updating profiles.

X users reported that posts and news were not loading, and some encountered login issues, during a disruption that began around 8:15 PM UTC and intensified by 8:45 PM UTC. StatusGator issued an Early Warning Signal at Mar 31, 2026 8:16 PM UTC for posts and news not loading. The outage affected core features such as posting, feed loading, and profile pages, with some users seeing profile or account errors like "account does not exist" while viewing profiles. The disruption persisted for about an hour and a half before activity began to settle around 9:50 PM UTC.

X did not publish observable updates on an official status page during the incident, and there was a large surge in user reports indicating broad impact across the service. Users experienced degraded interactions, including posts and comments not loading, difficulties logging in, and profile pages failing to load or display errors.