X outage history

Across Europe, X users faced connectivity issues as servers did not respond and apps failed to load. The disruption began at 3:51 PM UTC and was resolved by 4:37 PM UTC. StatusGator detected the issue at Oct 23, 2026 3:51 PM UTC, indicating the signal appeared ahead of any official acknowledgment.

Reports from cities across Europe — including London, Zurich, Prague, and Berlin — show the issue affected both web and mobile access, with users seeing server timeouts, not loading pages, or slow performance. The surge in reports around the onset suggests a broad impact before service restoration.

There were no provider status updates during the incident, and users generally regained access after the incident window closed. The event lasted roughly 46 minutes and affected multiple regions across Europe.

Users on X were unable to load posts or receive notifications for a short period, disrupting typical interaction with timelines and alerts. Impact began at 7:59 PM UTC and was resolved by 8:10 PM UTC, lasting about eleven minutes. Reports came in from across regions, with examples from the United States and France indicating a broader but transient disruption to core platform features.

Users of X worldwide experienced an outage affecting feeds, posts, and sign-ins. Impact began around 8:43 PM UTC with feeds not loading and passwords failing for some users, and reports of posts not appearing. Geographic spread covered North America, Europe, Latin America, and the Middle East, indicating a global disruption to core X functionality.

StatusGator recorded an Early Warning Signal at 8:43 PM UTC, signaling issues before X acknowledged them. The disruption lasted roughly an hour, with stability gradually improving by 9:50 PM UTC, as some users regained feed loading, posts appearing, and sign-in working again. X has no official status page in the data, and updates during the incident were limited to user-reported symptoms such as "Not loading", "Accounts not loading", and "Passwords not working", underscoring the broad impact across the platform's primary features.

Users across the globe were unable to load posts or comments, and the main feed failed to update, effectively halting new activity on X for many accounts. The issue began around 7:44 AM UTC, as StatusGator logged an Early Warning Signal from user reports, and persisted for most of the day. The earliest user report appeared at 7:30 AM UTC, with complaints continuing until around 4:10 PM UTC when activity started returning to normal for many users.

Users on X experienced a global outage in which posts, timelines, and search results failed to load on both website and mobile apps. The disruption, felt across continents, left feeds empty and errors when attempting to view posts or search. The issue began around 12:45 PM UTC and intensified into the early afternoon, with a noticeable spike in reports around 1:30 PM UTC and continuing through 2:01 PM UTC. StatusGator detected issues at Jun 26, 2026 12:48 PM UTC, ahead of any official acknowledgment. There is no official status page for X in this incident, so public updates were not available. The volume and spread of reports suggested a broad, global impact rather than a regional issue.

Users across the globe reported that X’s feed would not load, with posts not displaying, timelines stuck, or the home page showing the who-to-follow screen instead of content. The issue affected core user experience across devices and platforms, leaving many unable to view posts or engage with the feed. The geographic spread of reports indicates a worldwide disruption rather than a localized problem.

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.