Network
CDN & Caching review
Score: 10/10The reason Cloudflare exists, and still best-in-class.
The breakdown explains the score. It is not an average. How to read these.
Last updated
This is the product Cloudflare was built on, and it shows. Every plan gets the global anycast network and unmetered bandwidth. Cache Rules also give you proper control over caching without the guesswork of Page Rules.
Tiered Cache reduces origin load with one click. Cache Reserve adds long-lived persistence backed by R2. The analytics show what is served and from where, while purging by URL, tag, or hostname is fast and reliable.
Like DNS, the highest compliment I can pay is that it disappears into the background. Serving heavy static assets to a global audience without a bandwidth bill is something you stop appreciating until you price out the alternatives.
Status page incidents
Published under CDN/Cache, CDN Cache Purge, Cache Reserve, plus incidents whose title names it.
- Last 3 years
- 116
- 9 from the title
- Major or critical
- 12
- Median time open
- 1.7 h
- Since January 2019
- 239
CDN/Cache is the component Cloudflare reaches for when the edge itself misbehaves, so this count sweeps up a lot that is not really caching: single-file purge delays, regional 5xx spikes, and configuration propagation.
Counts what Cloudflare published, not what broke: time open is how long the status entry stayed open, and nothing before January 2019 is tracked at all. Incidents Cloudflare tagged against nothing but named in the title are counted too. The caveats in full.