What caused the X outage on January 15?

The cause is under investigation; some reports link it to Cloudflare infrastructure issues, but X has not provided an official explanation.

How widespread was the outage and which areas were affected?

Tens of thousands reported issues, with over 53,000 to 70,000 reports peaking around 9:30-10:45 a.m. ET, heavily concentrated in U.S. cities like New York, Los Angeles, Dallas, Houston, Chicago, and across the UK and Europe.

What symptoms did users experience during the outage?

Users saw blank screens, error messages like 'Something went wrong', login failures, feed loading issues, and Cloudflare error pages.

Has X provided any updates on the outage status?

No public status update or response from X; their developer status page showed all systems operational despite user reports.

Is this outage related to recent X issues?

It follows a similar disruption earlier in the week and comes amid scrutiny over Grok AI chatbot issues and content moderation failures since Musk's 2022 acquisition.

3 sources

•

1M ago

X Down Across U.S. and Europe: Tens of Thousands Report Outage

X suffered a widespread outage Jan. 15, leaving tens of thousands across U.S. cities and Europe unable to access the platform; cause under investigation now.

Overview

A summary of the key points of this story verified across multiple sources.

Tens of thousands of users reported problems accessing X Friday morning, with DownDetector logging more than 53,000 to 62,000 reports between 9:30 and 10:45 a.m. ET.

Major U.S. hubs — New York, Los Angeles, Dallas, Houston and Chicago — saw heavy concentrations of reports; outages were also reported across the UK and Europe.

Cloudflare experienced issues the same morning, and some reports linked those infrastructure problems to X's outage, though X has not provided an official explanation.

X has faced repeated outages since Elon Musk's 2022 acquisition and rebrand, and recently drew scrutiny over Grok, its AI chatbot, and content-moderation failures.

X did not immediately respond to media inquiries; the outage disrupted posting and app access for many users and followed a similar disruption earlier in the week.

Written using shared reports from

3 sources

Report issue

Analysis

Compare how each side frames the story — including which facts they emphasize or leave out.

Center-leaning sources frame X’s outage as part of broader accountability and ethical concerns, linking technical problems to prior controversies around Grok and adversarial media relations. They emphasize watchdog data, regulatory probes, and nonresponses while using evocative details (e.g., “Legacy Media Lies,” media antagonism) to foreground skepticism and institutional risk.

How we categorize media bias

Sources (3)

Compare how different news outlets are covering this story.

Sort By

FAQ

Dig deeper on this story with frequently asked questions.

: The cause is under investigation; some reports link it to Cloudflare infrastructure issues, but X has not provided an official explanation.
Sources:
The Economic Times
: Tens of thousands reported issues, with over 53,000 to 70,000 reports peaking around 9:30-10:45 a.m. ET, heavily concentrated in U.S. cities like New York, Los Angeles, Dallas, Houston, Chicago, and across the UK and Europe.
Sources:
TechRadar
: Users saw blank screens, error messages like 'Something went wrong', login failures, feed loading issues, and Cloudflare error pages.
Sources:
The Economic Times
: No public status update or response from X; their developer status page showed all systems operational despite user reports.
Sources:
The Economic Times
: It follows a similar disruption earlier in the week and comes amid scrutiny over Grok AI chatbot issues and content moderation failures since Musk's 2022 acquisition.
Sources:
Data Center Dynamics

History

See how this story has evolved over time.

This story does not have any previous versions.