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

June 26, 2026 Outage — What We Know

Cause: The root cause of the June 26 disruption has not been publicly identified. As of the time of reporting, X had not confirmed a widespread outage or issued an official explanation . No independent technical post-mortem or company statement pinning the cause to a specific infrastructure failure has surfaced.

Users affected: Specific Downdetector peak numbers for June 26 have not been published in the available sources. Reports describe "thousands" of users experiencing issues, but no exact peak figure comparable to the June 22 outage has been cited .

Core services disrupted: Users reported problems loading timelines, refreshing feeds, sending posts, and accessing certain parts of the platform . These symptoms — blank timelines, failed posting, and feed refresh failures — overlap substantially with the June 22 outage profile but without the same volume or cross-platform breadth.

Comparison: June 26 vs. June 22 Outage

Aspect	June 22, 2026	June 26, 2026
Root cause	Zayo fiber cut in Eastern North America causing Cloudflare routing failures	Unknown; no cause determined or announced
Scale	~35,000–36,000 Downdetector reports at peak; "millions" estimated affected globally	"Thousands" of reports; no specific peak number available
Duration	~45 minutes to ~1 hour; began ~9:00 a.m. ET, largely recovered by 10:15 a.m. ET	Not clearly documented in available sources
Scope	Broad multi-platform cascade: X, Reddit, Zoom, Microsoft Teams, Discord, Canva, Fortnite, Robinhood, AWS	Appears limited to X alone
Official explanation	Cloudflare confirmed a third-party fiber cut; Zayo implicated as the network provider	No official explanation from X or any infrastructure partner

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 .