CDN Cache Hit, Regional Traffic & Request Billing Calculator
Compare two actual CDN quotes using the same regional usage, cache hit ratios and origin billing conditions.
Use your ledger and quotes. Blank means unknown; enter 0 for confirmed free items.
Compare CDN bills using the same traffic
This CDN cache hit, regional traffic and request billing calculator compares two actual quotes against one usage ledger.
It helps small business owners, online retailers and content operators check a renewal or reconcile an expected monthly bill.
Multiplying total GB by one advertised rate can miss request charges, origin costs and a monthly minimum.
Charging the entire server outbound volume again on top of CDN delivery can also count traffic that the cache already served as if it came from the origin.
This calculator separates delivery to viewers from estimated origin traffic caused by cache misses.
The result follows the contract inputs you provide and is an estimate for comparison, rather than a supplier invoice.
Decisions supported by the comparison
- Which quote has a lower monthly total for the same regional GB and requests
- How better byte and request cache hit ratios change origin costs and savings
- Whether allowances, minimum charges or pricing bands change the winner as traffic grows
- Which origin waivers and shared account allowances still require supplier confirmation
Prepare your usage ledger and contract rates
Use regional delivery volumes and request counts for the same billing period.
Supplier billing regions can differ from visitor countries in an analytics report, so name the regions to match the actual invoice groups.
Enter both quotes in one currency and align the treatment of taxes and included services.
If unit rates already include all applicable tax, an explicitly confirmed additional tax rate of 0 can avoid adding that tax again.
Usage evidence
- GB delivered to viewers and HTTP/HTTPS requests by billing region
- Byte cache hit and request cache hit percentages for the same period
- Average object size in KB, only when estimating missing request counts
- Billing period, quote currency, validity and applicable tax treatment
Terms for each quote
- Regional transfer and request allowances and the first paid band width
- Flat, graduated or all-units volume billing
- Fixed monthly fee, CDN monthly minimum and other monthly charges
- Origin transfer waiver and separately charged origin requests
The form supports three billing regions.
Explicitly enter 0 GB and 0 requests for unused regions.
Combining regions with different tariffs into one average rate can change how allowances and bands apply, so divide the scope when the original contract cannot be represented faithfully.
Byte hit ratio and request hit ratio are separate
The request hit ratio measures the share of requests served from the cache.
The byte hit ratio measures the share of delivered bytes served from the cache.
One large video and many small images contribute differently to these measures, so neither percentage should automatically replace the other.
With 1,000 GB and an 80% byte hit ratio, estimated origin transfer is 200 GB.
With 1,000,000 requests and a 90% request hit ratio, estimated origin requests are 100,000.
Origin GB = total GB × (1 − byte hit ratio / 100)
Origin requests = total requests × (1 − request hit ratio / 100)
Revalidation, request collapsing, multiple cache layers and Origin Shield can make actual origin calls differ from these simple miss estimates.
Use the model to compare like-for-like assumptions and check the metric definition and measurement location if origin logs show a large difference.
A better cache hit ratio does not automatically reduce CDN delivery to viewers or viewer request charges by the same percentage.
Align GB, KB and million-request units
The calculator uses decimal units: 1 GB is 1,000,000,000 bytes and 1 KB is 1,000 bytes.
Convert GiB or TiB ledgers to GB after checking the supplier billing unit.
Direct request mode uses the recorded regional request count.
Average object size mode estimates regional requests from delivered GB and one shared average size.
Estimated requests = GB × 1,000,000 ÷ average object KB
For 1,000 GB and a 1,000 KB average object, the estimated count is 1,000,000 requests.
This assumes the average represents the delivered objects, so prefer actual counts when available.
Fractional estimated requests remain expected counts and are not rounded up during calculation.
Enter regional request prices per million requests.
Multiply a price quoted per 10,000 requests by 100 to obtain the per-million rate.
Regional request allowances and paid band widths are also in millions of requests, while the origin free-request field uses individual request counts.
Check each field label before transferring a number between these units.
Allowances and two-band pricing
Let q be the paid quantity after subtracting the free allowance, and L the width of the first paid band.
A flat tariff applies the first rate to all paid quantity.
Graduated pricing splits the paid quantity between bands, while all-units volume pricing applies the final band rate to all paid units.
A volume bill can fall immediately after crossing a discount boundary, so confusing it with graduated pricing can change the preferred quote.
q = max(0, usage − free allowance)
flat = q × first rate
graduated = min(q, L) × first rate + max(0, q − L) × next rate
volume = q × (q ≤ L ? first rate : next rate)
For 1,000 GB, a 100 GB allowance, a first paid band of 500 GB and rates of 0.10 then 0.08 USD, q is 900 GB.
Graduated transfer costs 500×0.10+400×0.08=82 USD, while all-units volume pricing costs 900×0.08=72 USD.
Exactly at q=500, the first rate applies.
The band width in this form starts after the free allowance has been removed.
If a supplier defines bands against cumulative usage including free units, convert the contract into the appropriate paid widths before entering it.
Do not duplicate account-wide allowances
Check how much of a shared allowance has already been consumed by other distributions or services.
Allocate the remaining allowance to the billing regions once only, following the supplier rules.
Restarting a shared graduated band independently in every region can also misstate the bill.
The calculator does not automatically allocate shared benefits or reproduce account-wide cumulative pricing.
Origin waivers and the scope of a monthly minimum
Origin transfer is the data sent from the origin server to the CDN.
A confirmed transfer waiver makes that transfer charge zero without waiving separately billed storage or origin requests.
For an AWS origin-to-CloudFront waiver, verify the actual service and connection conditions.
Keep the waiver unknown when it has not been confirmed, and defer the final comparison.
Origin transfer = max(0, origin GB − free origin GB) × rate per GB
Origin request fee = max(0, origin requests − free request count) ÷ 1,000,000 × per-million rate
CDN subtotal = max(CDN minimum, fixed fee + regional transfer + regional requests)
Before tax = CDN subtotal + origin transfer + origin requests + other monthly fees
Monthly total = before tax × (1 + user tax percentage / 100)
The monthly minimum applies to the CDN subtotal only.
A contract applying its minimum to origin and other charges as well cannot be reproduced with the same inputs.
Check unlimited flat-rate plans, complex commitments and shared multi-band tariffs in the supplier calculator.
Separate discounts and taxes and confirm their calculation order before entering an invoice.
Step-by-step use and unknown fields
- Enter shared usage: start with monthly GB for the first region, then complete other regions, requests, hit ratios and billing period.
- Complete quote A: copy regional transfer and request tariffs, fixed fees, minimum and origin terms.
- Complete quote B: keep the same usage and enter the alternative rates and waiver conditions.
- Review totals and missing terms: compare identical rows and ask the supplier about the remaining unknowns.
- Check changing usage: inspect sensitivity and usage scenarios, then save the comparison as TXT.
A blank field means unknown; an explicit 0 means you have confirmed zero cost or quantity.
Confirm absent allowances or request fees by entering 0 where required.
Partial input shows known costs and unanswered questions separately, with final totals and price ranking deferred while required conditions are missing.
Irrelevant rates are not required when zero usage or a confirmed waiver already determines that charge.
Opening the hypothetical example preserves your current values, step, selected quote and region; returning restores that editing state.
Worked example: 1,000 GB and one million requests
These are hypothetical USD quotes, not current supplier tariffs.
Region 1 has 1,000 GB and 1,000,000 requests; other regions have zero usage; the byte hit ratio is 80% and request hit ratio is 90%.
Both quotes use an illustrative 10% tax and 1 USD=1,400 KRW; neither value is a built-in legal tax rate or a live exchange rate.
Quote A has a fixed fee of 10, a 100 GB allowance and graduated rates of 0.10 then 0.08 after a 500 GB paid band.
Quote B has a fixed fee of 20, zero allowance and a flat transfer rate of 0.07.
CDN request rates are 2 per million for A and 1 per million for B, with zero free requests.
| Charge | Quote A | Quote B |
|---|---|---|
| Fixed fee | 10.00 | 20.00 |
| Regional transfer | 82.00 | 70.00 |
| CDN requests | 2.00 | 1.00 |
| CDN subtotal (minimum 0) | 94.00 | 91.00 |
| Origin transfer | 10.00 | 0.00 |
| Origin requests | 0.10 | 0.10 |
| Before tax (other fees 0) | 104.10 | 91.10 |
| Illustrative tax 10% | 10.41 | 9.11 |
| Monthly total USD | 114.51 | 100.21 |
| Optional KRW conversion | 160,314 | 140,294 |
Quote A origin transfer is 200 GB×0.05=10 USD, while B has a confirmed origin transfer waiver.
Both have zero free origin requests and an origin rate of 1 USD per million, so 100,000 origin requests cost 0.10 USD each.
Quote B saves 14.30 USD per month, equivalent to 20,020 KRW at the example exchange rate.
Verify that rates and waivers cover the same services before using this difference to choose a supplier.
Read cache sensitivity and usage scenarios
Sensitivity increases both byte and request hit ratios by 10 percentage points, capped at 100%.
In the example, 90% byte hits and 100% request hits produce A=108.90 USD and B=100.10 USD.
Viewer delivery and request charges remain, while origin miss costs change.
This scenario does not predict performance improvements or guarantee that the higher hit ratios can be achieved.
| Usage multiplier | Quote A | Quote B |
|---|---|---|
| 0.5× | 61.655 | 61.105 |
| 1× | 114.51 | 100.21 |
| 2× | 215.82 | 178.42 |
| 5× | 519.75 | 413.05 |
| 10× | 1,026.30 | 804.10 |
The 0.5× row retains three decimal places for checking; the interactive final amount displays up to two decimals.
Usage scenarios scale both traffic and requests while holding the regional mix, average object size and hit ratios constant.
Update the shared inputs when growth changes the customer geography or delivered object mix.
A change in the preferred quote between scenarios signals a pricing change within that range.
Monthly minima and all-units discounts can be discontinuous, so joining two points with a line does not establish an exact break-even volume.
Practical comparison scenarios
Image-heavy online shops
Many small objects can make request fees significant even at modest transfer volumes.
After compression reduces GB, check the request ledger again instead of assuming requests fell at the same rate.
Growing international traffic
Check the new billing region rate separately from allowances in existing regions.
Reclassify a country-level ledger when suppliers use different regional groups so that both quotes cover the same traffic.
Changing the origin and CDN combination
A transfer waiver available with the current combination may disappear when switching CDNs.
Compare the combined monthly total after origin charges, even when the advertised CDN delivery rate falls.
Renewal and minimum commitments
The CDN minimum can determine the bill in low-traffic months.
Verify promotion expiry, remaining allowances and separate commitment or cancellation costs, then include confirmed charges where appropriate.
For server specifications, operating labor, migration and outage costs over a longer horizon, use the Cloud Server vs Managed Hosting TCO Calculator.
Align the scopes so the same CDN charge is not added again to total server outbound costs.
Scope, rounding and saved results
- The model focuses on GET/HEAD downloads.
Add confirmed upload or CDN-to-origin, WAF, invalidation, edge function, logging, storage and Origin Shield charges as other monthly fees. - No legal tax rate or live exchange rate is supplied.
The optional exchange rate is KRW per one unit of quote currency, and a native-currency comparison is possible without it. - Both quotes use the same tax basis.
If suppliers tax different components, reconcile the quote scope before using the common tax percentage. - Intermediate calculations are not rounded.
Display rounding can differ from a supplier rounding every invoice line or applying minimum billing increments. - Inputs are calculated in your browser.
The saved TXT contains conditions and results, so review any contract names or sensitive customer details before sharing it.
Entering an unverified zero or applying a low band rate to all traffic can produce a complete-looking table without a valid contract comparison.
Leave unknown conditions unanswered and use the missing-item checklist to request the evidence needed for a decision.
Frequently asked questions
Does a 90% cache hit ratio reduce the CDN bill by 90%?
No.
Viewer delivery and requests can still be billable.
This calculator changes estimated origin usage according to byte misses and request misses separately.
Does an origin transfer waiver also waive origin request fees?
Confirm them separately.
Transfer waivers and storage GET or other request fees are different charges.
Selecting a transfer waiver does not automatically remove required origin request rates or allowances.
Can I repeat an account-wide free allowance in all three regions?
No.
Subtract other account usage, allocate only the remaining allowance once and check supplier allocation rules.
Automatic distribution of shared graduated bands is outside this model.
Should I use visitor countries or CDN billing regions?
Use supplier billing regions.
If the two suppliers group countries differently, reclassify the ledger to compare the same traffic scope.
Renaming different usage groups does not make them equivalent.
What if I do not know the request count?
Average object size mode estimates requests as GB×1,000,000÷average object KB.
Varying object sizes and error responses can affect that estimate, so use actual request counts when available.
Why are a blank field and zero treated differently?
Blank means unknown, while zero is a confirmed quantity or cost.
Required unknowns defer final totals and ranking.
Rates that cannot affect a known zero charge or confirmed waiver are not required unnecessarily.
Do usage scenarios find the exact volume where prices reverse?
They compare totals and the preferred quote at 0.5×, 1×, 2×, 5× and 10× usage.
Minimum charges and all-units discounts can be discontinuous, so they do not guarantee an exact reversal point between scenarios.
What should I check when the estimate differs from the invoice?
Check period and currency, GB versus GiB, HTTP/HTTPS, remaining allowances, origin waiver scope, taxes, per-line rounding and extras such as WAF and logs.
Do not add a charge again if it is already included in another line.
Official sources and update policy
Reference year: 2026; official documentation checked on 2026-11-21.
Sources establish billing structures and caching concepts; no current supplier price preset is supplied.
Recheck public pricing monthly and actual terms at every renewal or invoice review.
The AWS pricing page has differing request allowances in its table and some worked examples, so the calculator does not turn an example into an automatic entitlement and prioritizes your account and contract.
- AWS CloudFront pay-as-you-go pricing — regional delivery, requests and origin transfer terms
- AWS Caching and availability — request cache hit ratios and origin load
- bunny.net CDN Pricing — regional rates, monthly minimum and request billing structure
Match the conditions on your actual bill
Start with monthly delivery in GB and leave unverified terms blank.
Use the hypothetical example to understand the calculation, then return to your original inputs and enter confirmed contract values.
Review allowance allocation, transfer waivers, request charges and taxes with the supplier before choosing and saving your comparison.
Related calculators
- Cloud Server vs Managed Hosting TCO CalculatorCompare cloud infrastructure and managed hosting across resource, support, labor, migration, outage, and contract costs.
- Colocation Rack, Power & 95th Percentile Bill CalculatorAudit actual IDC rack, power, bandwidth and one-off charges using traffic samples and confirmed contract rules.
- Dedicated Line vs Business Internet SLA TCO CalculatorCompare dedicated, single business-internet, and primary-plus-backup options across contract cost, outage impact, SLA credits, and failover.
- Server Rack Count, Power, Cooling and Cost CalculatorSize server racks by U, IT power, cooling, redundant circuits, PUE energy, growth, and supplier quotes.