Bandwidth Egress Cost
Data-transfer bill from GB per month, an average Mbit/s or requests × payload, with a free allowance and up to three graduated per-GB tiers you enter.
GB per month, the GB in each tier with its cost, transfer and per-request totals, the effective price per GB and the usage as an average rate — no provider prices embedded.
Example: 15,000 GB with 100 GB free, 0.09 up to 10 TB and 0.085 to 50 TB: 9,900 × 0.09 + 5,000 × 0.085 = 1,316 (0.0877 per GB). 50 Mbit/s averaged over 30 days is 16,200 GB.
Usage in GB,
priced tier by tier.
How usage becomes GB, how graduated tiers are applied, and why no prices are built in.
Usage
A monthly GB figure is used as is; an average rate becomes GB = Mbit/s × 86,400 × days ÷ 8 ÷ 1000; a request count times an average response size becomes GB ÷ 10⁹. GB is decimal here because that is how providers bill, and the same usage is echoed as an average Mbit/s so a rate-based line item can be sanity-checked.
Graduated tiers
A free allowance comes off first; then tier 1 prices the GB up to its bound, tier 2 the GB between the bounds, and tier 3 everything above — each price applies only to the GB inside its band, which is how most cloud and CDN price lists are written. The table shows the GB and cost per band and the effective price per GB overall; a per-request price is added for request-based usage.
Prices
None are embedded. Region, destination (internet, same region, another cloud), CDN versus origin and committed-use discounts each change the rate, and price lists change; read the row that matches your traffic and type it in. Nothing leaves the browser; the same four anonymous usage counts as the rest of the site apply.
SOURCES
- GB from a rate = Mbit/s × 86 400 × days ÷ 8 ÷ 1000; from requests = count × bytes ÷ 10⁹; graduated tiers price only the GB inside each band (the usual price-list structure); prices are yours
Last reviewed 21 September 2026. How results are checked: How we verify.