X Gradually Recovers Following Outage Impacting Its Data Center
X is gradually recovering from a recent outage that impacted its data center operations. The disruption affected services for several users, but the company reports that systems are being restored step by step as technical teams address the underlying issues.
Tl;dr
- Major outage hit X, tied to data center fire.
- Key features remained disrupted for hours post-incident.
- Structural vulnerabilities date back to rapid server migration.
A Severe Outage Disrupts X
The social platform now known as X endured a significant disruption on Thursday, leaving users facing widespread service interruptions and once again spotlighting the network’s underlying technical weaknesses. Around 11 a.m. Pacific Time on May 22, developers reported what was described as a « site-wide outage », an event that would stretch over nearly twenty-four hours before the company cautiously announced a « gradual recovery » on Friday morning.
A Data Center Fire in Oregon: Unanswered Questions
Strikingly, this outage overlapped with a physical incident of its own: a fire broke out in a data center rented by X near Portland, Oregon. According to the publication Wired, emergency crews responded at 10:21 a.m. Thursday, with initial investigations suggesting faulty batteries might have sparked the blaze. While the flames were reportedly brought under control after several hours, precise details regarding damage remain elusive. Moreover, the platform has yet to issue any public statement clarifying the link—or lack thereof—between this fire and the technical meltdown experienced by its users.
Persistent Disruptions and Sparse Communication
Though access has gradually improved since Friday, several core functions—including direct messaging and logins—continue to show what developers call « performance degradation ». Users documented their frustrations en masse via downdetector.com, reporting issues such as:
Notably, since Thursday afternoon—when X‘s developer portal acknowledged « performance issues for some users »—the company has maintained radio silence regarding ongoing challenges.
A Tumultuous Backdrop: Hasty Migrations and Lingering Instability
To fully grasp the scope of this recent turmoil, it’s crucial to recall how quickly things changed after Elon Musk’s acquisition of the platform in late 2022. That period saw an abrupt overhaul of server infrastructure; servers were transferred from California to Oregon at breakneck speed, despite internal warnings that such a move required careful months-long planning. This risky maneuver—a point emphasized by Musk’s biographer—was followed by recurring outages over subsequent months and even prompted federal scrutiny from the Federal Trade Commission (FTC). The repercussions of these decisions linger, casting a long shadow over the network’s ability to maintain reliable service.
Ultimately, for both casual users and observers of digital infrastructure alike, these recent events underscore just how fragile even leading platforms can be in an age of complex migrations and unresolved technical debt.