CDN Traffic Unit Cost Calculator turns workload and billing inputs into a practical planning estimate. Use it to compare the main result with supporting cost, capacity, or efficiency measures before changing infrastructure. The calculation uses only the assumptions you enter, so it works across vendors and pricing models without treating any current rate as universal.
The main result applies the labeled cost, workload, growth, utilization, or headroom inputs in sequence. Percent inputs are converted to decimal factors before multiplication.
Use the main result as a comparable planning figure, then review the secondary results to identify which assumption drives the estimate. A provider invoice may use tiers or service-specific adjustments that are outside this model.
Planning estimate only. Confirm regional rates, billing tiers, service limits, and contractual terms with your provider before committing resources.
$4,200 ÷ 350 TB = $12.00 per delivered TB; at an 88% hit ratio, origin traffic is 42 TB.
Use the billed costs that correspond to the same measurement period and workload. Keep one-time migration or setup charges separate unless you intentionally want an all-in figure.
Yes. The calculator accepts decimals where partial capacity, traffic, time, or cost is meaningful.
Use a representative period that includes normal peaks and quiet intervals. Avoid comparing inputs taken from different billing or monitoring windows.
No. Enter actual net billed cost or an explicit discount where the calculator provides one. It does not assume a provider or price schedule.
Rounding, tiered pricing, regional rates, minimum charges, sampling, and excluded services can create differences. Treat the result as a planning estimate and reconcile it with detailed billing data.
| Output | Meaning |
|---|---|
| Cost per delivered GB | Calculated from the entered workload and cost assumptions. |
| Cost per million requests | Calculated from the entered workload and cost assumptions. |
| Estimated origin traffic | Calculated from the entered workload and cost assumptions. |