X Outage History

X is experiencing a global outage affecting the feed and timelines on the X website and mobile apps. Users across multiple regions report that posts and timelines fail to load, and in some cases the app or site appears down. The issue began around 1:28 PM UTC and has persisted, with widespread reports from North America, Europe, Asia, and other regions. As of 1:52 PM UTC, the outage remains ongoing.

StatusGator recorded an Early Warning Signal at Feb 16, 2026 1:28 PM UTC indicating feed issues. There are no official status page updates from X in this incident, and the geographic spread of user reports suggests global impact. There is no estimated time to restore.

X's feed service suffered a global outage that prevented feeds from loading and disrupted search for about 45 minutes. The issue appears to have started around 1:04 AM UTC and was resolved around 1:49 AM UTC. User reports came in from across North America, Europe, and beyond, including locations like Orlando, Houston, Dublin, Paris, and Bogotá, all indicating not loading feeds or inability to load new content. The outage affected feed delivery and search functionality across the service.

X has no official status page, and no provider updates were published during the incident. StatusGator detected the issue at Feb 9, 2026 1:04 AM UTC, providing an early warning ahead of any acknowledgement.

The incident shows a global pattern of impact, with a surge of user reports around 01:30 UTC indicating widespread disruption rather than a localized problem. Recovery began by 1:49 AM UTC and services returned to normal within that window.

X users worldwide experienced a brief outage that prevented feeds, timelines, posts, and search results from loading. The issue began at 4:22 PM UTC and was resolved by 4:33 PM UTC, lasting about 11 minutes. StatusGator detected the problem at Feb 1, 2026 4:22 PM UTC, ahead of any official acknowledgment. There were no official status updates from X during the incident. The disruption appeared to be global, with reports spanning North America, Europe, Africa, the Middle East, and beyond.

Users reported that posts would not load and timelines were blank across mobile and web clients, indicating a widespread impact affecting core feed functionality.

The X app experienced a brief global outage with content not loading for users. The incident began at Jan 31, 2026 3:47 AM UTC and was resolved by Jan 31, 2026 3:53 AM UTC, lasting about 6 minutes. User reports started flowing in from multiple regions around 3:45 AM UTC, indicating a widespread impact on loading posts and feed content. StatusGator recorded an Early Warning Signal at Jan 31, 2026 3:47 AM UTC based on user observations; however, X has no official status page to acknowledge the incident or publish updates. There were no public updates from X during the outage, and the disruption appeared to be limited to content loading rather than a full service outage.

StatusGator detected a desktop loading issue on 2026-01-24 that prevented the X web interface from loading for many desktop users. Reports describe not loading, spinning wheels, and stuck login prompts on desktop, while mobile apps remained largely usable, indicating a desktop-specific partial outage with global reach. The incident lasted roughly 1 hour and 25 minutes, from Jan 24, 2026 1:03 AM UTC to Jan 24, 2026 2:28 AM UTC. User reports traced from multiple regions including the United States, Spain, the United Kingdom, Canada, Australia, and Uruguay, suggesting broad geographic impact.

X users worldwide experienced an outage where tweets and replies would not load, preventing engagement with posts and conversations. The issue appeared global, with reports from Europe, North America, Africa, and Asia, including the United Kingdom, United States, Morocco, Saudi Arabia, Australia, Japan, Canada, and Indonesia. Because X has no official status page in this dataset, there were no published updates from X during the incident, and the communication largely relied on user reports and third-party monitoring.

StatusGator detected the issue at Jan 23, 2026 1:38 PM UTC, with an Early Warning Signal that ended at Jan 23, 2026 2:13 PM UTC as activity from users indicated the problem. The volume of reports rose through the early afternoon, suggesting a widespread disruption rather than a regional outage. There were no official public updates from X during the incident in the data provided, reinforcing the impression of a globally distributed service disruption.

The outage began at 5:14 PM UTC according to StatusGator's Early Warning Signal after user reports of login failures and content-loading issues. Users globally reported being unable to log in, feeds not loading, and posts failing to appear. StatusGator detected the issue at Jan 22, 2026 5:14 PM UTC based on user reports, ahead of any official acknowledgment. The problem appeared brief, with a surge in reports through the next minutes and service restoration by 5:27 PM UTC (roughly 13 minutes).

With no official status page updates from X during the incident, the worldwide pattern of user reports shows a global disruption affecting sign-in and content delivery across multiple regions. The incident appears to have resolved by 5:27 PM UTC.

X experienced a global login outage that prevented many users from signing in, creating new accounts, or performing common actions such as password resets. Users in multiple regions reported authentication failures and errors ranging from inability to sign in to internal errors affecting posting and engagement features. The outage began at Jan 16, 2026 3:12 PM UTC and was resolved by Jan 16, 2026 8:55 PM UTC, lasting about 5 hours and 43 minutes. StatusGator detected the issue at Jan 16, 2026 3:12 PM UTC, ahead of any official acknowledgment. There were no official status updates published by X during the incident.

Starting at 1:21 PM UTC, users around the world began reporting that posts were not loading or displaying on X. The issue persisted for about 2 hours and 7 minutes, with users unable to view timelines or post new content until it was resolved by 3:28 PM UTC. StatusGator detected the issue at Jan 13, 2026 1:21 PM UTC, based on user reports ahead of any official acknowledgment.

Because X has no official status page for this incident, there were no published updates from the service during the outage. The situation was inferred from a high volume of global user reports, with peaks around 2:15 PM UTC to 2:45 PM UTC indicating broad impact on posting and feed loading.

StatusGator detected an Early Warning Signal at Jan 12, 2026 3:41 PM UTC based on user reports, indicating issues before any official acknowledgement. The outage began at 3:41 PM UTC and was resolved by 5:14 PM UTC, lasting about 1 hour and 33 minutes. Photos and videos were not loading for many users, with reports concentrated across the Philippines; there was also a report from Allen, Kansas indicating sign-in problems. The incident generated a substantial volume of user reports spanning multiple cities during the event.