CDN Cost Guide: Diagnose the Bill, Choose the Right Calculator, and Validate the Model

Start with a calculator if you need a first-pass estimate, then use this guide to validate the assumptions and catch the billing traps.

This guide is the CDN bill-boundary page: edge bandwidth, request fees, and origin egress should be modeled as separate cost surfaces instead of one blurred delivery number.

Use this page when you need to decide what belongs inside the full CDN delivery bill before you compare providers, simplify to per-GB math, price requests, estimate traffic volume, or untangle origin egress.

First-screen triage: which CDN line item moved first?

1. What changed first: delivered edge GB, request units, or cache hit rate.
2. Which CDN line item moved: bandwidth, request fees, or origin-side leakage.
3. Which tool to use next: bandwidth calculator, request calculator, origin egress calculator, or the full CDN planner.
4. What to validate next: baseline vs peak windows, launch or incident behavior, and the real cache-hit assumption.

Short answer: what decides CDN cost first?

• If responses are large or regional delivery is expensive, bandwidth usually dominates.
• If responses are small and request volume is high, request fees can dominate.
• If cache hit rate is weak or unstable, origin egress can erase expected CDN savings.

Guide first or calculator first?

• Use this guide first when you still need to define the bill boundary.
• Use the full CDN planner when bandwidth, request, and origin surfaces all need to stay visible in one model.
• Use the narrow calculators when one line item is already clearly isolated and you need deeper math on that slice.

Keep the CDN guide cluster separated on purpose

Provider choice belongs on comparison. Blended bandwidth-rate math belongs on per-GB pricing. Request-fee math belongs on request pricing. Traffic evidence belongs on bandwidth measurement. Concept confusion belongs on origin egress vs CDN bandwidth.

High-value mistakes that make CDN pages look low-trust

• Mixing edge bandwidth and origin egress into one delivery number.
• Hiding request-unit mistakes inside a bandwidth estimate, especially per 10k vs per 1M confusion.
• Using a healthy cache hit rate from a calm week while budgeting for a launch or incident month.
• Comparing vendors with different traffic profiles, region mix, or cache assumptions.

CDN bill-boundary workflow

• Edge bandwidth: delivered GB from the CDN edge to viewers. Tool: bandwidth calculator.
• Request fees: billable request units. Tool: request calculator.
• Origin egress: bytes and refill overhead still paid by the origin. Tool: origin egress calculator.
• Full delivery model: when you need bandwidth share, request share, and origin egress share in one place. Tool: full CDN planner.

What to check before you trust one blended CDN number

• Keep one workload profile when comparing providers: same GB, requests, region mix, and hit rate.
• Split baseline and peak windows so a launch or incident does not disappear into the normal month.
• Validate whether the traffic question is really about bandwidth, requests, or cache-hit decay before changing architecture.
• Reconcile every major input back to billing, analytics, or a written planning assumption.

Monthly planning checklist

1. Confirm which CDN line item moved first.
2. Separate edge bandwidth, request fees, and origin leakage into their own rows.
3. Split baseline and peak windows, especially for launch, incident, or campaign planning.
4. Validate cache hit rate and origin-side traffic before using one blended total in a budget review.

Which calculator should you open next?

Failure patterns to catch before procurement

• One blended rate hides regional price spread and overstates savings.
• Edge delivery and origin leakage are merged into one number.
• Peak or launch behavior is ignored even though it is the first thing finance will ask about.
• Request pricing units are mixed in the same sheet without normalization.

Related tools

More CDN guides

Treat this page as a routing and validation workflow: confirm billable units, region mix, and cache-hit assumptions before you turn a blended CDN number into a committed budget.

Related guides

Related calculators

FAQ