Edge cache hit ratio
The percentage of requests answered by the edge cache instead of your real server. Higher usually means less origin work.
See it
What it is
Edge cache hit ratio is the percentage of requests the edge answers from a stored copy. If 9,500 of 10,000 eligible requests are hits, the ratio is 95 percent and only 500 need an origin fetch. Some dashboards instead divide by every request, including uncacheable traffic, so write down the denominator before comparing numbers.
Watch it by route and content type, not only as one site-wide score. A high ratio on JS, CSS, images, and public pages means the CDN is taking real work away from the origin. Authenticated APIs may correctly stay at zero because their responses must never enter a shared cache.
Gotcha: the headline percentage can improve while users get slower. Bots can inflate hits on cheap files, byte-heavy misses can still dominate origin bandwidth, and a cache key that ignores personalization can create excellent metrics while serving the wrong content. Pair request hit ratio with byte hit ratio, origin requests, and latency. Cloudflare's analytics reports cached requests and cached bandwidth as two separate numbers for exactly this reason, and they routinely disagree.
Ask AI for it
Build a cache-hit dashboard from Cloudflare Logpush HTTP request logs. Record CF-Cache-Status and route template for every public request, count only HIT as definitely origin-free, and report HIT divided by cache-eligible requests per route and content type. Show BYPASS, DYNAMIC, MISS, EXPIRED, and REVALIDATED separately rather than hiding them in one denominator. Also chart origin request count, transferred bytes, p50 latency, and p95 latency for the same time window, with alerts on sudden ratio drops.