X is still experiencing problems after data center outage

X is still experiencing performance issues a few days after a data center outage brought the site down, with feeds struggling to load on Saturday morning. The site went down for many users around 8AM ET, when downdetector shows a major spike in problem reports. It's since come back up, but performance remains spotty. In an update about the incident posted on Friday night, X's engineering team said, "We're still experiencing issues from yesterday's data center outage. Login and signup services are unavailable for some users, and there may be delays in notifications and Premium features. Our team is working 24/7 to resolve this." According to posts on the company's developer platform page, a "site-wide outage" began at 11AM PT on Thursday, May 22, had "been resolved" as of 10:35 AM PT Friday morning. But the developer site notes that X is still experiencing "degraded performance" of some of its login features. The company has yet to officially comment on the ongoing technical problems since an update Thursday afternoon, when the company said that a data center outage was causing "performance issues" for some users. X is aware some of our users are experiencing performance issues on the platform today. We are experiencing a data center outage and the team is actively working to remediate the issue.— Engineering (@XEng) May 22, 2025 At the time, reports on downdetector.com, which tracks online service outages, spiked as users reported issues accessing direct messages and other features. While the company hasn't elaborated on the cause of the prolonged outage, the timing lines up with a reported fire at an X data center in Oregon on Thursday. According to Wired, firefighters responded to a fire at a data center leased by X near Portland, Oregon at 10:21AM PT on Thursday. The extent of the damage is unclear, but the fire crews were reportedly on-scene for several hours. Batteries were apparently a contributing factor to the blaze. X hasn't responded to questions about the fire or the data center outage it disclosed. However, this wouldn't be the first data center-related headache X has faced. Shortly after Elon Musk took over the company in 2022, he insisted on moving the company's servers out of a facility in California to a space in Oregon in a bid to save money. And while Twitter engineers had insisted the process would take months, Musk insisted on moving them in a matter of weeks, in an incident detailed by Musk's biographer. While Musk was able to accomplish his goal of quickly relocating the servers, his haphazard approach to the move resulted in months of technical issues for the company and an investigation by the Federal Trade Commission. Update, May 24, 2025, 11:07AM ET: This post has been updated to reflect the ongoing issues with the site's performance and to include the latest update from X about the outage. It was previously updated multiple times, and that information is now included in the story above. This article originally appeared on Engadget at https://www.engadget.com/social-media/x-is-recovering-after-a-data-center-outage-204254431.html?src=rss

May 24, 2025 - 16:16
 0
X is still experiencing problems after data center outage

X is still experiencing performance issues a few days after a data center outage brought the site down, with feeds struggling to load on Saturday morning. The site went down for many users around 8AM ET, when downdetector shows a major spike in problem reports. It's since come back up, but performance remains spotty.

In an update about the incident posted on Friday night, X's engineering team said, "We're still experiencing issues from yesterday's data center outage. Login and signup services are unavailable for some users, and there may be delays in notifications and Premium features. Our team is working 24/7 to resolve this."

According to posts on the company's developer platform page, a "site-wide outage" began at 11AM PT on Thursday, May 22, had "been resolved" as of 10:35 AM PT Friday morning. But the developer site notes that X is still experiencing "degraded performance" of some of its login features. The company has yet to officially comment on the ongoing technical problems since an update Thursday afternoon, when the company said that a data center outage was causing "performance issues" for some users.

At the time, reports on downdetector.com, which tracks online service outages, spiked as users reported issues accessing direct messages and other features. While the company hasn't elaborated on the cause of the prolonged outage, the timing lines up with a reported fire at an X data center in Oregon on Thursday. According to Wired, firefighters responded to a fire at a data center leased by X near Portland, Oregon at 10:21AM PT on Thursday. The extent of the damage is unclear, but the fire crews were reportedly on-scene for several hours. Batteries were apparently a contributing factor to the blaze.

X hasn't responded to questions about the fire or the data center outage it disclosed. However, this wouldn't be the first data center-related headache X has faced. Shortly after Elon Musk took over the company in 2022, he insisted on moving the company's servers out of a facility in California to a space in Oregon in a bid to save money. And while Twitter engineers had insisted the process would take months, Musk insisted on moving them in a matter of weeks, in an incident detailed by Musk's biographer.

While Musk was able to accomplish his goal of quickly relocating the servers, his haphazard approach to the move resulted in months of technical issues for the company and an investigation by the Federal Trade Commission.

Update, May 24, 2025, 11:07AM ET: This post has been updated to reflect the ongoing issues with the site's performance and to include the latest update from X about the outage. It was previously updated multiple times, and that information is now included in the story above. This article originally appeared on Engadget at https://www.engadget.com/social-media/x-is-recovering-after-a-data-center-outage-204254431.html?src=rss