Skip to content

Why Doesn't Cloudflare Crash When 20 Million People Open the Same Website?

Millions of people can hit the same website in the same second without it falling over — because most of those requests never reach the origin. How edge caching, rate limiting, and traffic filtering do the real work.

By 2 min read
  • System Design Explained
  • CDN
  • Rate Limiting
  • Caching
  • System Design

Imagine a major product launch. Or the World Cup Final. Or Black Friday.

Suddenly...

Millions of people try to access the same website at almost the same time. Yet for many websites, everything continues working.

Why? Because the website isn't handling all those requests alone.

Why Doesn't Cloudflare Crash When 20 Million People Open the Same Website?

A simplified request journey looks like this:

  1. 🌍 You type a website into your browser.
  2. ⚡ Your request first reaches a nearby Cloudflare edge location.
  3. 🛡️ Suspicious traffic is identified and filtered before it reaches the website.
  4. 🚦 Rate limits protect critical endpoints from excessive requests.
  5. 📦 Cached content is served directly from the edge whenever possible.
  6. 🌐 Only legitimate requests that need fresh data reach the origin server.

Notice what's happening? The origin server isn't becoming more powerful. It's simply receiving far less work.

That's one of the biggest lessons in system design. Scaling isn't only about adding infrastructure. It's about preventing unnecessary traffic from reaching it.

Every cached response... Every blocked bot... Every rejected request...

Creates capacity for users who genuinely need the service.

That's why platforms protecting millions of websites don't focus only on speed. They focus on intelligent traffic management.

The next time a popular website survives a massive traffic spike, there's a good chance thousands of requests never reached its servers in the first place.

What's another internet-scale system you'd like to see broken down next?

Keep reading