Definition
Bandwidth is the amount of data transferred over a network in a given time period, commonly measured and billed per GB.
Why it matters
High data transfer can drive material infrastructure costs and can quickly erode margins if not priced or controlled. The commercial question is not only what the vendor bill looks like, but how much of that cost the public pricing model can safely absorb.
What bandwidth does and does not tell you
Bandwidth tells you transfer volume and cost exposure. It does not tell you whether the right fix is included usage, overage, an enterprise path, or pass-through.
That decision depends on traffic shape, buyer tolerance, and how volatile the underlying delivery floor is.
Pricing implications
Separate storage from bandwidth in plans, use usage tiers to reflect marginal costs, and add overage rates for spikes. If the traffic mix is highly variable, the pricing structure may need guardrails rather than a single headline rate.
Common drivers
Large file downloads, streaming, API responses, and CDN cache misses are typical bandwidth drivers.
Measurement tips
Track bandwidth by product area, customer segment, and region to identify the highest cost contributors. If one cohort consistently drives the expensive tail, the pricing model should not pretend that cohort is average.
Common mistakes
- Using one average bandwidth rate for every product shape.
- Ignoring cache miss behavior and origin fetch costs.
- Publishing a simple rate without checking burst-heavy cohorts.
- Treating bandwidth as a technical metric only, not a pricing input.
How to use it with PricingNest tools
Use Bandwidth Pricing Guardrails when the public plan needs a clear threshold. Use CDN Cost Pass-Through when cost variability is too high to hide inside a single public rate.