Skip to content

CDN caching, explained Explained

How a CDN serves your files from edge POPs: the instant HIT path, the MISS path back to your origin, and how purges and TTLs keep copies fresh, each shown as a live animated diagram with a side-by-side comparison.

Animated diagrams · 3 flows

Compare all 3

Sort by any column to find the right fit. Click a name to open its details.

Cache MISSVisitor → edge → originNoHigh, first request onlyHTTP, backbone to originMediumFirst visitor of each URL
Edge HITEdge POP → visitorNo, a stored copyVery lowHTTP at the POPLowHot assets on repeat views
Purge + TTLOrigin → every edge POPNear real-timeSeconds, until propagatedPurge API or TTL expiryMediumFresh content after deploys