X Outage History

Users across the globe reported that content on X would not load or refresh. The disruption affected the core feed, timelines, and posting flow, with some posts loading briefly but then disappearing, and others showing empty content or errors. The outage began around 12:30 PM UTC and persisted into the afternoon, with reports spanning North America, Europe, and beyond. StatusGator logged an Early Warning Signal starting at 12:35 PM UTC for content not loading or refreshing, lasting through 3:02 PM UTC. There were no observed official status updates from X during the event.

Users reported login and sign-up failures across multiple locations, leaving many unable to sign in or create new accounts on X for several hours. The disruption appears to have begun around 8:15 PM UTC, with reports describing errors like 'can't login' and 'sign up down' during the period. StatusGator surfaced an Early Warning Signal at 9:13 PM UTC ahead of any official acknowledgement. The Early Warning Signal concluded at 11:36 PM UTC; with X lacking an official status page, users relied on StatusGator and community reports to infer scope and timing. The issues primarily affected authentication and sign-up workflows across the service, degrading the user experience for a substantial portion of the evening.

Users worldwide faced login failures beginning around 5:45 AM UTC, with a steady stream of reports throughout the morning. The disruption affected X's authentication service, preventing sign-in on multiple devices and blocking access to accounts for many users. The issue persisted for several hours and appeared to ease by 8:03 AM UTC as access began returning to normal.

StatusGator logged an Early Warning Signal at May 23, 2025 6:49 AM UTC for login issues affecting account access. X does not have an official status page in this incident, so provider updates were not publicly published. The pattern of user reports across regions indicated a broad impact on sign-in across devices. The incident concluded as sign-in stabilized by 8:03 AM UTC.

Users across Europe, North America, the Middle East, and Asia reported login failures, posting errors, and missing notifications as the Grok component struggled to handle normal activity. The outage began around 6:56 PM UTC and persisted for about two hours, with activity peaking in the 7:30 PM UTC– 8:45 PM UTC window as more users reported trouble and posts failed to publish. The disruption affected core features such as signing in, posting updates, and receiving notifications, with many users experiencing degraded or unavailable services across multiple regions.

Users on X experienced issues with loading and updating posts across feeds, with reports spanning continents from the United States to Europe and the Middle East. The problem prevented posts from loading or updating in the main feed, affecting the posting experience for a broad, globally distributed audience. Impact began around 1:55 PM UTC and was resolved by 3:36 PM UTC, lasting roughly 1 hour and 40 minutes.

StatusGator logged an Early Warning Signal as user reports surfaced before any formal updates, indicating widespread visibility of the issue across multiple regions. X does not publish an official status page for incidents, so public updates during the window were limited to user-reported activity and StatusGator's visibility of the situation. Affected components centered on the post feed, including loading and refresh behavior, with users in cities around the world reporting symptoms.

Users worldwide could not log in or load X pages as a global outage affected core authentication and content delivery. The first notable reports appeared around 6:45 PM UTC, and StatusGator issued an Early Warning Signal at Mar 28, 2025 6:55 PM UTC ahead of any official acknowledgment; that warning window ended at 7:05 PM UTC. The interruption persisted for about 20 minutes for many users.

Because X does not maintain an official status page, there were no provider updates captured to guide users through the outage. The spike in user reports within the 18:45 to 19:05Z window points to a broad, global impact, with experiences including login failures and pages failing to load.

X's Grok service experienced an outage that prevented content loading and posting for about 27 minutes. Impact began around 6:53 PM UTC and was resolved by 7:20 PM UTC as users reported the service returning to normal. During the window, users faced failures to load, timeouts, and posts that would not publish, with some describing the entire Grok experience as down.

Status information from X's side was not available on an official status page; however StatusGator issued an Early Warning Signal based on user reports indicating loading and response issues. The incident appeared to affect a wide portion of users attempting to load or post within Grok during the window, with activity dropping off as the service recovered.

X experienced a global disruption affecting content loading and access to profiles. The issue began at 8:34 AM UTC and persisted until 9:52 AM UTC, lasting about 1 hour and 18 minutes. Reports came from cities across Europe, the Americas, and Asia, including Istanbul, Belgrade, Baku, Tucson, Rancho Cordova (CA), Hong Kong, Norway, and Norwich, indicating widespread impact on core user experiences like loading content and viewing profiles.

X did not publish any official status updates during the incident. StatusGator detected the issue at Mar 11, 2025 8:34 AM UTC and the signal concluded at Mar 11, 2025 9:52 AM UTC, signaling an early detection ahead of any formal acknowledgment. With no official notices, users relied on informal reports while the incident ran, signaling a major disruption with broad geographic reach.