CDN Cache Hit Ratio Calculator
Turn edge hits and misses into a cache hit ratio, origin offload and the origin egress the cache actually avoids.
Inputs
CloudFront and Fastly list prices start near $0.085/GB in North America and fall with volume commitments.
What your origin cloud charges to push a GB out to the CDN — around $0.09/GB on list pricing.
Cache Hit Ratio
92.00%
Cache Miss Ratio
8.00%
Traffic Served Without Touching Origin
460.00TB
Traffic Pulled From Origin
40.00TB
CDN Delivery Charge
$43,520.00
Origin Egress Charge
$3,686.40
Origin Egress Avoided by Caching
$42,393.60
Total Delivery Cost
$47,206.40
Step by step
Values used
Edge cache hits = 920 million requests; Edge cache misses = 80 million requests; Traffic delivered to users = 500 TB/month; CDN delivery price = 0.0850 USD/GB; Origin egress price = 0.0900 USD/GB
CDN Cache Hit Ratio
hit ratio = hits ÷ (hits + misses); origin offload = hit ratio × delivered traffic; origin traffic = (1 − hit ratio) × delivered traffic.
Cache Hit Ratio
= 92.00
Cache Miss Ratio
= 8.00
Traffic Served Without Touching Origin
= 460.00 TB
Traffic Pulled From Origin
= 40.00 TB
CDN Delivery Charge
= 43,520.00
Origin Egress Charge
= 3,686.40
How it works
The ratio is counted in requests, but the money is in bytes: every miss forces a fetch that you pay for twice, once as origin egress and again as CDN delivery. Multiplying the miss ratio by delivered traffic gives the origin pull, and the remainder is the offload that only costs the CDN rate. Cache hit ratio is the single lever that decides how much origin capacity and egress you buy — lifting 88% to 95% removes more than half the origin traffic. Confirm both the CDN and origin egress rates with your providers, because volume commitments move them a long way from list price.
Formula
CDN Cache Hit Ratio
hit ratio = hits ÷ (hits + misses); origin offload = hit ratio × delivered traffic; origin traffic = (1 − hit ratio) × delivered traffic.
- hit ratio
- Share of requests answered from an edge cache
- origin offload
- Traffic the edge served so the origin never saw it
- origin egress avoided
- Offloaded traffic priced at your origin egress rate
Frequently Asked Questions
How is CDN Cache Hit Ratio calculated?
hit ratio = hits ÷ (hits + misses); origin offload = hit ratio × delivered traffic; origin traffic = (1 − hit ratio) × delivered traffic. The ratio is counted in requests, but the money is in bytes: every miss forces a fetch that you pay for twice, once as origin egress and again as CDN delivery. Multiplying the miss ratio by delivered traffic gives the origin pull, and the remainder is the offload that only costs the CDN rate.
Why does CDN Cache Hit Ratio matter?
Cache hit ratio is the single lever that decides how much origin capacity and egress you buy — lifting 88% to 95% removes more than half the origin traffic. Confirm both the CDN and origin egress rates with your providers, because volume commitments move them a long way from list price.
What values do I need to enter?
This calculator takes 5 inputs: Edge cache hits, Edge cache misses, Traffic delivered to users, CDN delivery price, Origin egress price. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Should I measure hit ratio by requests or by bytes?
Track both. Request hit ratio tells you how well the cache key and TTLs are working; byte hit ratio tells you what you are paying, and it is usually lower because large objects are the ones most often missed or range-requested.
You might also need
- Cloudflare CDN Cost CalculatorCommonly used together
- Edge Storage CalculatorCommonly used together
- Cloudflare R2 Storage CalculatorCommonly used together
- CDN Bandwidth CalculatorCommonly used together
- Cloud Readiness Assessment CalculatorCommonly used together
- Edge Performance Score CalculatorCommonly used together