What Happened — and Why It Brought Down So Much at Once

Cloudflare carries roughly 20 percent of all global web traffic. That number sounds abstract until you actually see what happens when its network stumbles — and on Monday, June 22, you didn't have to imagine it.

At 13:35 UTC, Cloudflare began reporting increased error rates and latency across multiple services. By 14:37 UTC, the company said it had identified the issue and was pushing a fix. But in that roughly hour-long window, millions of people around the world lost access to some of the most-visited platforms on the internet.

The affected systems included Cloudflare's CDN, cache, analytics, and Durable Objects infrastructure — core components that an enormous portion of the web relies on just to function.

Which Platforms Went Down

The list of services users couldn't reach reads like a shortlist of the internet's most-used products. X (formerly Twitter), Reddit, Zoom, Discord, Canva, Fortnite, and the Epic Games Store all saw widespread disruption, according to Downdetector data and reports compiled across multiple outlets.

For a lot of people, that's not just inconvenient — it's a Tuesday morning that suddenly doesn't work. Video calls dropped. Feeds went blank. Login screens refused to budge.

Where the Outage Hit Hardest — and How Many People Noticed

The disruption was global, but it landed with the most force in six countries: the United States, the United Kingdom, India, Australia, Canada, and Germany.

X took the most visible hit. At the peak — around 7:38 p.m. IST, or roughly 10:08 a.m. ET — more than 35,000 users filed disruption reports on Downdetector. In the US alone, over 15,000 complaints came in just before 10 a.m. ET, concentrated heavily along the East Coast. New York, Boston, and Washington, D.C. bore the worst of it.

Users described a familiar, grinding set of symptoms: blank timelines, app crashes, login failures, and error messages that just said "Something went wrong. Try reloading." Not exactly helpful when you're trying to figure out what's happening.

X's Second Bad Day in a Row

Here's the thing — Monday wasn't even X's first rough stretch that weekend. The day before, on Sunday, June 21, Downdetector recorded around 2,600 disruption reports near noon ET.

Whether Sunday's problems and Monday's outage share the same underlying cause isn't clear. As of Monday afternoon, X hadn't issued any official statement about either incident, which left users to connect their own dots.

There's another piece to this that Cloudflare hasn't fully explained yet. The company had already scheduled maintenance at its Newark, New Jersey data center starting at 01:00 UTC on June 22 — the same day as the broader outage. In advance of that work, Cloudflare warned that traffic might be rerouted and some users in the region could see slightly higher latency.

Whether that planned maintenance touched off anything in the wider incident, or whether the two events were entirely separate, Cloudflare didn't immediately say. That gap in the explanation is the kind of thing that makes people uneasy about relying on a single provider for this much infrastructure.

This Isn't the First Time — A Pattern of Disruptions

Honestly, if this outage felt familiar, that's because it kind of is.

In November 2025, a bug in a configuration file caused what Cloudflare itself called a "significant outage," knocking out access to X, ChatGPT, and a range of other services for several hours. In February 2026, a separate problem with Cloudflare's Bring Your Own IP service pulled customer network routes entirely off the internet — for more than six hours.

The common thread across all of these is scale. Cloudflare handles traffic for millions of websites and applications. When you concentrate that much of the internet through one network, even a brief technical hiccup doesn't stay contained. It spreads. And the people who feel it aren't just Cloudflare's direct customers — they're every user of every product that happens to sit behind Cloudflare's infrastructure.