WAFGOPreparing your page
CDN billing guide

CDN billing: traffic, regions and delivery scope

Prepare CDN pricing requirements around traffic, bandwidth, regions and security scope, distinguishing delivery usage, requests and origin costs.

Overview

Monthly usage is only a starting point when discussing a CDN plan with WAFGO. Audience location, short traffic peaks and additional protection needs all shape the scope and cost model.

No universal CDN unit price, free allowance or minimum spend is published here. Confirm billing units, charging methods, taxes and overage rules in the agreed quote and terms.

01

Start with the billing basis

Transferred data, peak bandwidth and request count are different measures. Quotes should state the measurement basis, units and billing period, including whether data is expressed in GB or GiB.

Start with the billing basis
DimensionInformation to prepare
Data deliveryMonthly transfer, typical object sizes and download versus page traffic
Regional distributionPrimary audience countries and any regional delivery restrictions
Traffic peaksEvent windows, peak duration and concurrent downloads
Security and supportProtected entry points, policy scope and operational support
02

Make estimates reproducible

For transfer-based billing, group usage by region, apply confirmed rates and add explicitly agreed charges. Bandwidth-based billing requires the agreed sampling and aggregation method; the transfer formula does not apply.

  • Transfer estimate: sum regional usage multiplied by its confirmed rate, then add agreed service charges.
  • Track edge delivery and origin egress separately; cache hits do not eliminate every network charge.
  • Consider repeat downloads, purges, agreed attack-traffic treatment and changes in event demand.
03

Use clear limits and reconciliation

A low unit price does not describe the complete cost. Confirm regions, request-related charges, minimums, support and usage controls instead of assuming every feature is included.

Budget alerts

Confirm available thresholds, notification recipients and the distinction between an alert and automatic suspension.

Usage reconciliation

Record periods, time zones, regional usage and hostname scope, then reconcile reports on the same basis.

Plan changes

Check when plan or regional changes take effect and how mid-period adjustments are billed.

Implementation & checks

  1. 01

    Gather usage

    Provide existing invoices or comparable usage samples.

  2. 02

    Agree on scope

    List regions, security, support and additional requirements.

  3. 03

    Review the quote

    Confirm units, periods, overages and change rules.

Frequently asked questions

Do not assume so. Plans may use different billing dimensions; follow the confirmed quote.

Not necessarily. Regions, peaks, scope and commitment terms all influence the quote.

Start with your requirements

Make the architecture work for your business

Share your audience regions, content types and current challenges with WAFGO to clarify prerequisites, service scope and validation.

Discuss my requirements