Pay-As-You-Go CDN Pricing: How Usage-Based Billing Works

<span id="hs_cos_wrapper_name" class="hs_cos_wrapper hs_cos_wrapper_meta_field hs_cos_wrapper_type_text" style="" data-hs-cos-general-type="meta_field" data-hs-cos-type="text" >Pay-As-You-Go CDN Pricing: How Usage-Based Billing Works</span>

A pay as you go CDN bills only for the data it delivers each month, priced per GB or per TB on volume tiers, with no volume commitment beyond a small monthly floor. At 100 TB a month, BlazingCDN lists $415 as of November 2026, while Amazon CloudFront's pay-as-you-go rates for the US and Europe come to $6,965 for transfer alone, before request fees (list price checked November 2026). Most of that spread comes from tier structure, request fees and regional rates, and those three variables decide most usage-based bills.

How we compared, and who is writing. BlazingCDN publishes this blog and is one of the providers compared in this article. Every price is the provider's own published list price at the stated volume, before negotiated discounts, read on the official pricing pages linked below; the check date stands next to each figure. Price tables are ordered by that list price, lowest first, and a price order is not a measurement of delivery quality. Treat the BlazingCDN figure like every other figure here: a published number to verify on your own traffic.

Sources: bunny.net pricing, CDN77 pricing, KeyCDN pricing, Amazon CloudFront pricing, Amazon CloudFront flat-rate pricing, Cloudflare pricing, BlazingCDN pricing.

Key numbers

  • $0.005 per GB equals $5 per TB: convert every per-GB list before comparing.
  • A commit priced 25% below your pay-as-you-go rate only wins if you use more than 75% of it every month.
  • Below 50 TB a month, flat plans such as Amazon CloudFront Pro at $15 can undercut usage-based tiers (checked November 2026).

How usage-based CDN pricing is calculated per GB and per TB

Usage-based CDN pricing multiplies delivered bytes by a rate per GB or per TB, then layers on tier breaks, regional rates, request fees and a monthly minimum. The headline rate is the least useful number on the page. The effective rate at your volume, after every line item, is the one to budget against.

Tiers come in two forms. Marginal tiers work like tax brackets: each rate applies only to traffic inside its range. Whole-volume tiers reprice the entire month once you cross a threshold, which creates a cliff where 101 TB can cost less than 99 TB. Also confirm whether a TB means 1,000 or 1,024 GB, because binary units add 2.4% to every line.

Worked example on marginal tiers at 200 TB: 5 TB at $5.00 ($25), 20 TB at $4.50 ($90), 75 TB at $4.00 ($300) and 100 TB at $3.50 ($350), for $765 a month, an effective $3.83 per TB. Those are BlazingCDN's tiers as of November 2026: from $5 per TB down to $2.50 per TB at volume, one rate for the US, Europe and Asia, no request fees, no regional multipliers and a $25 monthly minimum. The multi-vendor CDN price comparison places those tiers next to other published lists.

What 100 TB a month costs on published list prices

The table is sorted by published list price for 100 TB a month delivered in North America and Europe, lowest first.

ProviderList cost at 100 TB a monthBilling modelStrengthLimitation
BlazingCDN$415 (as of November 2026)Marginal tiers, $5 to $2.50 per TB, $25 minimumOne rate for US, Europe and Asia; no request feesNo HTTP/3, WebSockets or edge compute
bunny.net (Volume network)$500 (checked November 2026)$0.005 per GB for the first 500 TB, $1 minimum$1 minimum suits small projectsStandard network lists $1,000 at 100 TB
CDN77$990 (checked November 2026)Flat plan up to 250 TB, $3.96 per TB overageFixed monthly figure up to 250 TBFull $990 applies at any volume in the plan
KeyCDN$2,600 (checked November 2026)Per-GB tiers, $0.04 to $0.02Pure usage, no plan to sizeAsia priced higher
Amazon CloudFront (pay as you go)$6,965 transfer only (checked November 2026)Per-GB tiers, $0.085 to $0.060, first 1 TB at no chargeNative fit for S3 origins and AWS teamsRequests billed on top of transfer

At 100 TB the published list prices range from $415 to $6,965 a month before request fees, so billing model moves the budget more than any traffic optimization will.

Disclosure: BlazingCDN publishes this blog. The order above follows the stated key only and is not a quality ranking.

When a pay as you go CDN beats a committed contract

A commit trades a lower per-TB rate for a promise to pay for a fixed volume whether you use it or not. It beats usage-based billing only when monthly traffic stays above a share of the commit equal to one minus the discount, every month, for the whole term.

This utilization test is this blog's own framework. If the commit rate is the pay-as-you-go rate times (1 minus d), a month using U of a committed C costs C times (1 minus d) on contract against U on pay-as-you-go. The contract wins only when U divided by C exceeds 1 minus d: a 20% discount needs 80% utilization, a 35% discount needs 65%.

Worked example, with illustrative rates rather than any provider's quote: a 12-month commit of 200 TB a month at 25% off. A steady 190 TB month pays for 150 TB-equivalents of pay-as-you-go spend and saves about 21%. A catalog running 130 TB for eleven months plus one 260 TB launch month loses 20 TB-equivalents in each quiet month, gains at most 65 in the launch month, and ends the year about 9% behind pay-as-you-go.

Criterion (this blog's thresholds)Usage-based fits whenCommit or flat plan fits when
Peak month over trough monthAbove 1.5 timesBelow 1.2 times
Trough traffic against the offered commitBelow 1 minus the discountAbove 1 minus the discount
Monthly volumeAbove 50 TB, or growing fastUp to 50 TB with requests inside a flat allowance
Vendor horizonRe-evaluation likely within 12 monthsVendor settled for the full term

If two or more rows land in the middle column, usage-based billing is the lower-risk default, and a commit is worth negotiating only after six months of measured traffic.

Risk and switching cost: shortfall, true-ups and lock-in

Commits carry shortfall billing, annual true-ups, auto-renewal and notice periods, and each one turns a forecast error into a fixed cost. A monthly minimum is different: it is a floor, not a term, and you can leave after any month.

Switching cost on usage-based billing is mostly engineering time (cache rules, signed URL schemes, purge hooks, log pipelines) plus a temporary rise in origin egress while the new cache warms. A weighted DNS split ramped over weeks caps that spike. BlazingCDN can run as a second CDN behind DNS with a weighted split, includes origin shield, request coalescing and cache warm-up through the API, and onboarding takes about one hour.

When another provider fits better

Up to 50 TB a month, published flat plans can cost less than BlazingCDN's $215 at 50 TB (as of November 2026): Amazon CloudFront Pro at $15 a month when traffic fits its 10 million request allowance (50 TB needs an average response of about 5 MB or larger), Cloudflare Pro at $25 a month for traffic its terms allow, and Amazon CloudFront Business at $200 a month between about 46 and 50 TB (checked November 2026). Projects under 5 TB a month fit bunny.net's $1 minimum better than BlazingCDN's $25. Teams needing a web application firewall (WAF), bot management, DDoS mitigation or edge compute from one vendor belong on Cloudflare, Fastly or Akamai; HTTP/3 and WebSockets are not supported by BlazingCDN. A finance team that requires one fixed monthly figure may prefer CDN77's $990 plan covering up to 250 TB (checked November 2026).

FAQ: pay-as-you-go CDN pricing for procurement and finance

Is a pay-as-you-go CDN more expensive than a committed CDN contract?

Only when you actually consume the commit. A commit at discount d beats pay-as-you-go CDN billing only when monthly traffic stays above 1 minus d of the committed volume, so a 25% discount needs 75% utilization every month of the term. Seasonal, launch-driven or fast-changing traffic usually fails that test, and shortfall is billed regardless.

How do I convert CDN pricing per GB into a monthly budget?

Multiply the per-GB rate by 1,000 for a per-TB rate, then apply each tier only to traffic inside it: $0.005 per GB is $5 per TB. Add request fees, regional rates outside North America and Europe, and origin egress on cache misses, then divide the total by delivered TB to get the effective rate.

What does usage-based CDN pricing charge besides bandwidth?

The common extras are per-request fees, regional multipliers, monthly minimums and origin egress on cache misses. Amazon CloudFront bills requests on top of transfer on its pay-as-you-go rates, checked November 2026. Small-object workloads feel request fees most, while large-file delivery is driven by the per-TB rate and regional mix.

Do pay-as-you-go CDN plans have a monthly minimum?

Many do, but the floors are small next to commits. As of November 2026, BlazingCDN's monthly minimum is $25, covering the first 5 TB at $5 per TB, and bunny.net's is $1 (checked November 2026). A minimum is not a commitment: you can leave after any month, while a commit bills shortfall for its full term.

Run the utilization test on 12 months of egress

Export monthly delivered TB per region and request counts for the last 12 months from your CDN billing or logs. Note the trough, median and peak month, then divide the trough by any commit you have been offered: if the result sits below 1 minus the discount, the commit costs more than usage-based billing. Price each month on two or three published lists, requests included, and bring the effective per-TB rate to the budget meeting.

If that math points to usage-based billing, the BlazingCDN CDN cost calculator prices the same monthly volumes on its progressive tiers from $5 per TB, as of November 2026.

Heavy traffic.
Light bill.

The CDN for video and large traffic