Search & fact-check with cited sources for What caused the X (formerly Twitter) outage on June 26, 2026, how many users were affected, what core services were disrupted, how does this compare to the larger June 22 outage linked to a Zayo fiber cut affecting Cloudflare, what patte

The June 22 outage was an infrastructure domino — a physical fiber cut at Zayo degraded Cloudflare's routing, which in turn knocked out X and many other major platforms . The June 26 event was narrower in scope and lacks any confirmed external cause.

Pattern of Recurring Disruptions in 2026

X has experienced a marked increase in outages throughout 2026 . Documented major incidents include:

• January 13–14 — Global outage, over 22,900 US reports on Downdetector
• January 16 — Widespread outage, over 60,000–62,000 US reports
• February 1 — Service disruption, over 19,281 US reports
• February 16 — Major outage, over 40,000 reports; platform inaccessible for ~60 minutes
• April 1 — Reports of app and web malfunctions, timeline update failures
• May 31 — Login and app access issues reported on Downdetector
• June 22 — Zayo/Cloudflare-linked outage, ~35,000–36,000 reports at peak
• June 26 — Service issues, "thousands" of reports, no exact peak confirmed

Multiple outlets have characterized these as an abnormal frequency, with analysts and users noting the platform is "down like twice a week" . This recurring pattern has been described as an "infrastructure crisis" driven by reduced staffing and degraded reliability following mass layoffs and post-acquisition cost-cutting .

Official Explanation for June 26

No. As of the latest available reporting on June 26, 2026, X had not confirmed a widespread outage or issued any official statement explaining the cause . This contrasts with the June 22 event, where Cloudflare publicly acknowledged the fiber cut and provided status updates .