Users around the world, one origin. Without a CDN every request crosses the globe and hammers the origin. Turn the CDN on and users hit a nearby edge instead — latency drops per region and the origin is shielded. Then kill the origin and watch the edges keep serving cached content.
One origin server, users all over the world. Toggle the CDN and watch latency per region — then kill the origin and see who's still standing.
🗄️ Origin server (US-East)load 100%
Every request in the world lands here.
🇺🇸 N. America25 ms
→ all the way to US-East origin
🇧🇷 S. America120 ms
→ all the way to US-East origin
🇪🇺 Europe95 ms
→ all the way to US-East origin
🇮🇳 India170 ms
→ all the way to US-East origin
🇦🇺 Australia250 ms
→ all the way to US-East origin
Average latency ~132 ms — distant regions (India, Australia) suffer because every request crosses the globe to one origin.
What just happened
▹A CDN caches your content at edge locations spread around the world. Users hit the nearest edge instead of your distant origin, so latency drops dramatically for far-away regions — distance is the latency you can't optimize away in code.
▹It also shields the origin: most requests are answered at the edge, so origin load collapses. Fewer trips, cheaper bandwidth, calmer servers.
▹A CDN is a resilience layer too. If the origin is slow or down, edges keep serving cached content for its TTL — users may not even notice the outage. CDNs absorb both traffic spikes and origin failures.