X appears to eventually recover from a power outage in the data center, which brought scenes to some users on Thursday and led to lingering problems on Friday. On the company’s developer platform page, “Power Outage in Scope” started Thursday, May 22 at 11 a.m. and was “solved” as of 10:35 a.m. on Friday.
The developer’s website notes that X is still experiencing “downgraded performance” of some of its login features. The company has not formally commented on ongoing technical issues since the update Thursday afternoon, when the company said the data center disruption caused “performance issues” for some users.
X knows that some of our users are experiencing performance issues on the platform today. We are experiencing disruptions in our data centers and the team is actively working to resolve the issue.
– Project (@xeng) May 22, 2025
At that time, when tracking reports of online service outages, users reported issues accessing direct messages and other features. While the company has not detailed the reasons for the extended interruption, the timing is aligned with the reported fire at the Oregon X data center. according to Firefighters made a fire at 10:21 a.m. Thursday at the data center rented by X near Portland, Oregon. The extent of the damage is not known, but firefighters reportedly stayed on the scene for several hours. Batteries are obviously a contributing factor in the fire.
X has not answered questions about fire or data center disruptions. However, this is not the first data center-related headache X faces. Shortly after Elon Musk took over the company in 2022, he insisted that the company’s servers be removed from a California factory out of a space in Oregon to save money. Although Twitter engineers insist that the process will take months, Musk insists on moving it in a few weeks among Musk’s biographers.
Although Musk was able to achieve the goal of quickly relocating servers, his accidental approach to the move led to technical problems for the company and the Federal Trade Commission.
Updated, May 23, 2025, 12:00 pm: This post has been changed to reflect X’s latest update on the interrupt. It has been updated several times before, and the information is now included in the story above.
