Cookie Settings

Choose which cookies to allow.

Full list in our Privacy Policy.

CDN Cost: What You’re Actually Paying for and How to Track It in Real Time

Lightning bolt with rising arrows on a blue background, featured image for a post on CDN costs and pricing

CDN pricing looks simple on the provider’s website. A per-gigabyte rate, maybe a plan tier, a free allowance to get you started. Then the monthly bill arrives and tells a different story, one written in bandwidth tiers, request fees, regional multipliers, origin egress, and add-on charges for WAF, bot management, and logging that no one totaled up at purchase. The gap between the headline rate and the actual invoice is where most teams’ frustration with CDN cost lives.

This guide closes that gap in two halves. First, what CDN cost is actually made of and how the major pricing models differ, so the bill stops being a mystery. Then the operational half, the one that matters once you’re already running a CDN: why the bill changes month to month, and how real-time spend tracking lets you catch a cost problem while it’s happening instead of explaining it after the invoice lands.

What Makes Up Your CDN Cost?

A CDN bill is rarely one number. It’s five, stacked, and understanding each is the first step to controlling the total.

Edge Bandwidth (Data Transfer)

The core charge: bytes delivered from CDN edge servers to your users, almost always the largest line item. Most providers price this per gigabyte on a tiered basis that drops as volume rises. As of 2026, published first-tier rates for North America and Europe run around $0.085/GB on AWS CloudFront and roughly $0.12/GB on Fastly, while volume-priced independents sit far lower. The notable exception is Cloudflare, which doesn’t meter bandwidth at all; its Pro and Business plans bundle unlimited cached-content bandwidth into a flat fee, which changes the cost math entirely and is worth understanding before you compare rates.

Request Fees

Some providers charge per HTTP or HTTPS request on top of bandwidth, and for the right workload this dominates the bill. CloudFront, for instance, adds on the order of $0.01 per 10,000 HTTPS requests. That sounds trivial until you run an API or small-object workload: a service averaging a few kilobytes per response at high volume can generate billions of requests a month, and the request fees alone can rival or exceed the bandwidth charge. A workload averaging 5 KB per response at 100 TB/month generates roughly 20 billion requests, where per-request charges alone can run into five figures monthly. Small payloads are where request-based pricing quietly hurts, and it’s the single most underestimated line for API-heavy stacks.

Origin Egress (Cache Fill)

When the CDN doesn’t have content cached, it fetches from your origin, and that cache-fill traffic is billed as egress by your cloud provider (one of the biggest CDN egress costs), commonly $0.05 to $0.09 per GB from AWS depending on region. This is technically not a CDN fee, which is exactly why it’s so often missed in cost modeling, and it’s directly driven by your cache hit ratio: every point the ratio drops is more origin fetches and more egress. One provider quirk worth knowing is that CloudFront pulling from an AWS origin in the same region incurs no transfer charge, a genuine advantage for all-AWS architectures.

Regional Pricing Multipliers

Where your traffic lands changes what it costs, often dramatically. Most providers charge substantially more to serve some geographies, and the spread is not small: CloudFront’s South America rate runs roughly $0.17/GB against about $0.085/GB for North America, and India sits near $0.109/GB, while Fastly‘s Brazil rate is more than double its NA/EU rate. Serving traffic in South America, Africa, or parts of Asia Pacific commonly costs two to five times more per GB than North America or Europe, which means a shift in where your users are, not how many, can move your bill. Some providers give you a lever here: CloudFront’s Price Classes, for example, let you restrict which regional edge locations serve your content, so a US and EU audience isn’t quietly paying South American rates for traffic it never generates.

Security and Feature Add-Ons

The base delivery rate is rarely the whole product. WAF, bot management, advanced DDoS protection, real-time logging, image optimization, and edge compute each add cost on top, and they’re frequently the difference between the quote and the invoice. A CDN comparison done on bandwidth rate alone ignores the layer where a lot of the money actually accumulates.

CDN Pricing Models Compared

Balance scale weighing coins on a blue background, illustrating a comparison of CDN pricing models

Underneath the line items, providers follow one of a few pricing philosophies, and matching the model to your traffic matters more than chasing the lowest headline rate.

Pay-as-you-go, used by AWS CloudFront, Fastly, and volume-priced independents, bills you for exactly what you transfer. It’s transparent and scales precisely with usage, which also means the bill fluctuates every month and a traffic spike lands directly on your invoice. Flat-rate subscription, the Cloudflare model, charges a fixed monthly fee ($0, $25, or $200 across Free, Pro, and Business) with bandwidth included, giving you predictable cost, though add-ons and enterprise features still raise the total. Commit-and-discount, typical of enterprise agreements with Akamai and Fastly, trades a committed minimum for a lower per-GB rate, which rewards steady high volume and penalizes you if you under-use. And hybrid models pair a base subscription with usage-based overage above an included allowance.

The practical consequence: the same traffic can cost wildly different amounts depending on model fit. A high-traffic, highly cacheable static site can run on a Cloudflare flat plan for a fixed fee that a per-GB provider would bill thousands for, while an all-AWS architecture with modest volume may be cheapest on CloudFront thanks to free same-region origin transfer. To make that concrete: 50 TB per month from a non-AWS origin runs a few thousand dollars on a per-GB provider at first-tier NA/EU rates, versus a flat plan fee on Cloudflare for the same cacheable traffic. The cheapest provider on paper is often not the cheapest for your workload, and the only way to know is to run your actual traffic shape against each provider’s full rate card, not just its headline number.

Why Your CDN Bill Keeps Surprising You

Understanding the components explains the bill you expected. It doesn’t explain why this month’s is different from last month’s, and that difference is where operational teams actually get hurt. Five causes account for most of it.

Cache Hit Ratio Drops Nobody Noticed

An edge configuration change quietly reduced caching effectiveness, more requests fell through to origin, and egress climbed, and nobody connected the change to the cost until the invoice arrived. Because cache-fill egress scales directly with your miss rate, a hit-ratio drop is one of the most expensive things that can happen to your bill without anything appearing to break.

Traffic Spikes and Bot Activity

A legitimate traffic surge, a DDoS attempt, or aggressive bot scraping generated bandwidth and request costs nobody budgeted for. On pay-as-you-go pricing, this lands directly and immediately, and bot traffic in particular is insidious because it often targets uncached, dynamic endpoints that maximize origin cost per request.

Configuration Changes Without Cost Impact Awareness

Someone adjusted a cache TTL, modified a WAF rule, or changed a routing policy. The change was operationally justified, and it had a cost consequence nobody tracked because the two live in different systems. This is the mechanism behind most surprise invoices: an ordinary change with an untracked financial tail.

Multi-CDN Cost Fragmentation

Teams running multiple CDN providers receive multiple invoices in different formats, with different metering methods and different pricing units. Comparing or consolidating that cost data is manual, error-prone work that rarely happens consistently, so multi-vendor cost visibility degrades into a per-invoice reaction rather than a coherent view.

Regional Traffic Shifts

Your user base gradually shifted toward more expensive regions, and because per-GB rates vary two to five times by geography, your blended cost per GB climbed even though your total traffic didn’t. Without regional cost tracking, this drift is invisible until the average has already moved.

How to Track CDN Costs in Real Time

Radar scan icon on a blue background, illustrating how to track CDN costs in real time

The common thread in every surprise above is latency, between the event and your awareness of it. Real-time cost tracking removes that lag. Five practices make it work.

Stop Relying on Monthly Invoices

By the time the invoice arrives, the money is spent and the cause is weeks old. Real-time spend tracking shows cost accumulating as traffic flows, which gives your team the one thing an invoice never can: the chance to intervene while a spike is still building rather than after it has fully landed.

Map Spend to Infrastructure Behavior

The valuable question isn’t “how much did we spend,” it’s “why.” Connecting cost data to cache hit ratios, configuration state, and traffic patterns turns a billing line into an actionable signal, because it tells you which lever moved the number. This is exactly what Lelops Sentry does with its FinOps capability: it tracks every request and maps what your stack does to what it costs, so a cost change arrives already attached to the configuration or traffic behavior that caused it, rather than as an unexplained figure on a statement.

Set Anomaly Alerts on Cost, Not Just Traffic

Traffic alerts catch volume spikes; cost alerts catch efficiency drops, and those are different problems. A 10% traffic increase paired with a 30% cost increase tells you something changed in your efficiency, a hit-ratio drop, a regional shift, that a purely traffic-based alert would miss entirely. Alert on the cost signal and the divergence between cost and traffic, not just on volume.

Consolidate Multi-Provider Spend in One View

If you run Cloudflare, Akamai, and CloudFront, you need one view that normalizes cost across all three, because their different billing formats, metering intervals, and pricing units make manual consolidation both painful and unreliable. A unified view is what lets you see total spend, compare per-GB efficiency across providers, and find where optimization actually pays off.

Tie Cost Reviews to Configuration Change Logs

Make CDN cost review a standing item in your operational cadence, and wire it to your change history. When cost moves, the first question should be “what changed in our configuration this period,” and the data to answer it should already be at hand. Cost review disconnected from change history is guesswork; cost review joined to it is diagnosis.

Lelops Sentry maps what your edge stack does to what it costs, so you never get surprised by an invoice again: lelops.ai/product/sentry. See how Lelops pricing works for your infrastructure: lelops.ai/pricing

FAQ

How much does a CDN cost?

CDN cost varies enormously by provider, pricing model, and traffic profile. Per-GB providers like AWS CloudFront and Fastly charge roughly $0.085 to $0.12/GB in North America and Europe for first-tier volume, with rates two to five times higher in regions like South America and Asia Pacific, while Cloudflare uses flat-rate plans ($0, $25, or $200 monthly) with bundled bandwidth instead of per-GB billing. Request fees, origin egress, regional multipliers, and security add-ons all affect the total, so the same traffic can cost very differently across providers depending on how well the model fits your workload.

What are the hidden fees in CDN pricing?

The most commonly overlooked costs are origin egress for cache fill (billed by your cloud provider, often $0.05 to $0.09/GB from AWS), per-request fees that dominate small-object and API workloads, regional multipliers that make some geographies several times more expensive, and add-on charges for WAF, bot management, logging, and edge compute. Low cache hit ratios silently inflate origin egress, and these fees frequently turn a cheap-looking headline rate into a much larger real bill.

Why is my CDN bill higher than expected?

The usual causes are a cache hit ratio drop that increased origin fetches, a traffic or bot spike on pay-as-you-go pricing, a configuration change with an untracked cost consequence, or a gradual shift of traffic toward more expensive regions. Because these causes live in your configuration and traffic rather than on the invoice, connecting a bill increase to its root cause typically requires correlating cost with cache performance and configuration changes, which monthly invoices alone cannot do.

How do I compare CDN costs across providers?

Compare on effective delivered cost per GB using your own traffic, calculated as total invoice divided by total delivered GB, broken down by region and workload, rather than on headline rates. Pull several months of production data, including regional traffic mix, request counts, and cache hit ratio, then apply each provider’s full rate card including request fees, regional multipliers, and add-ons. Because pricing models differ so fundamentally, flat-rate versus per-GB versus commit-and-discount, the cheapest provider depends entirely on your specific traffic shape.

What is the best way to track CDN costs in real time?

Real-time tracking means monitoring spend as traffic flows rather than waiting for the invoice, mapping cost to the cache performance and configuration state that drive it, and alerting on cost anomalies distinct from traffic anomalies. For multi-provider stacks it also requires consolidating spend across vendors into one normalized view. The goal is to catch a cost problem while it is happening and trace it immediately to its cause, which a platform that ties traffic and configuration to cost delivers and monthly invoices cannot.

Get started

Connect Cloudflare. See where your edge stands today.

Your first configuration health report, with the fixes to make first, in minutes.

  • No credit card required