Beata Zawrzel/NurPhoto via Getty Images
Follow ZDNET: Add us as a preferred source on Google.
ZDNET’s key takeaways
- X is suffering a widespread outage Friday morning.
- Problems started shortly before 10:30 a.m. ET.
- DownDetector showed problems all across the United States.
If you’re having problems with X today, you’re not alone.
Shortly before 10:30 a.m. ET, reports of problems surged on DownDetector, a popular site for tracking outages. When I tried for myself on the browser version, I got an error saying, “Connection timed out Error code 522.” The app version loaded, but no new content would load.
A DownDetector map showed problems all across the United States. This comes just a few days after another outage that took the social media site offline for many. (Disclosure: Downdetector is owned by Ziff Davis, the same parent company as ZDNET.)
DownDetector also showed a surge in reports of a Cloudflare outage at the same time, along with Grok, and AWS, so it’s possible the issue is greater than just X.
A Cloudflare system status page explains that scheduled maintenance is currently in progress. It was just last November when a massive Cloudflare outage took down huge portions of the web. Last year’s attack wasn’t malicious, and there’s nothing yet to indicate this issue is, either.
The specific error page many users are seeing is a Cloudflare error page, but it says that Cloudflare is working normally and the problem is with the host — in this case, x.com.
At 10:55 a.m. ET, the Cloudflare status site updated to read, “Identified – Cloudflare has identified an increased level of errors for customers running Workers scripts in Newark and Atlanta.” By 11:06 a.m., a status read, “A fix has been implemented and we are monitoring the results.”
More updates to follow shortly.
I’ve reached out to X for more details.
