{"id":671028,"date":"2025-05-23T17:20:22","date_gmt":"2025-05-23T14:20:22","guid":{"rendered":"https:\/\/en.buradabiliyorum.com\/x-continues-to-suffer-bugs-following-thursday-outage\/"},"modified":"2025-05-23T17:20:22","modified_gmt":"2025-05-23T14:20:22","slug":"x-continues-to-suffer-bugs-following-thursday-outage","status":"publish","type":"post","link":"https:\/\/buradabiliyorum.com\/en\/x-continues-to-suffer-bugs-following-thursday-outage\/","title":{"rendered":"X continues to suffer bugs following Thursday outage"},"content":{"rendered":"
\n

For over 24 hours, many X users, including this reporter, have been experiencing issues with the site\u2019s basic functionality. Some messages won\u2019t load, timelines won\u2019t update, and certain posts can\u2019t be seen without a webpage refresh (or several).<\/p>\n

The trouble started Thursday afternoon, according to Downdetector<\/a>, a crowdsourced platform for flagging web outages. Beginning at 2:12 p.m. Eastern, thousands of users submitted reports about bugs ranging from an inability to sign in to disapp<\/a>earing direct messages. <\/p>\n

X\u2019s official Engineering account acknowledged<\/a> the degraded service in a post on Thursday, claiming it was related to a data center outage.<\/p>\n

\u201cX is aware some of our users are experiencing performance issues on the platform today,\u201d wrote the account. \u201cWe are experiencing a data center outage and the team is actively working to remedia<\/a>te the issue.\u201d<\/p>\n

Wired reported<\/a> that a fire broke out Thursday at an X-leased data center near Portland, Oregon. It\u2019s unclear if it\u2019s related to the ongoing outages.<\/p>\n

\n
\n
\n

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.<\/p>\n

\u2014 Engineering (@XEng) May 22, 2025<\/a><\/p><\/blockquote>\n<\/div>\n<\/figure>\n

The\u00a0last major service disruption X\u00a0suffered was in March, when users worldwide were abruptly disconnected from the social network and subsequently had trouble accessing their feeds, sending messages, and engaging with content. Musk, without evidence,\u00a0blamed the disruption on a cyberattack<\/a>. <\/p>\n

Prior to that outage, X experienced large-scale connectivity issues in\u00a0December 2022\u00a0and July 2023. More recently, in May, X timelines briefly stopped updating for many users.<\/p>\n

After Musk acquired X, formerly known as Twitter,\u00a0for $44 billion in 2022, he promptly slashed the company\u2019s workforce by about 80%, from 7,500 employees to 1,300 workers. X had just 550 full-time engineers as of January 2023,\u00a0according to CNBC<\/a>. A\u00a0new wave of layoffs<\/a>\u00a0hit the company in November 2024, primarily affecting X\u2019s engineering department.<\/p>\n

Since Musk\u2019s purchase of X, the company has also reportedly made security snafus<\/a>, improperly configuring servers that might\u2019ve left the site vulnerable to denial of service attacks.<\/p>\n<\/div>\n