Estimate what your traffic could give back
Four inputs, modelled on the ranges DTEA members have validated on live traffic. The result is a direction, not a promise — the coefficients and their conditions are printed underneath.
Everything you send to users and to other networks, per month.
One blended rate. Origin egress and edge delivery are priced differently in practice.
Share of requests served without going back to origin.
Encoding gains only apply to the part of your traffic you encode.
$17,876
Egress cost avoided per year
- 18.6
- TB / month
- 15.5%
- Reduction
- $1,490
- $ / month
- Delivery & caching7.2 TB
Hit ratio 76% → 82.0%
- Per-title encoding8.9 TB
12% of video bytes
- Transport tuning2.5 TB
2.4% of remaining bytes
A directional estimate from published member ranges — not a quote, a forecast or a benchmark. The coefficients and their conditions are listed below.
What this model assumes
Delivery & caching
1.0 – 6.0 pp
Up to six percentage points of cache hit ratio is recoverable from retention and routing changes on head content, scaled by the gap to full caching. Long-tail content moves far less.
Per-title encoding
8 – 18% of video bytes
Applied at the 12% midpoint of the range members reported. It does not apply to live or event traffic you have not encoded yet, and it is excluded if you tick the box.
Transport tuning
1.5 – 4.0% of bytes
Connection reuse, pacing and removing speculative fetches reduce retransmission and setup overhead. Applied at 2.4% to the bytes the other levers leave in place.
Every coefficient sits inside a range published in the resource library, where the baseline, population and interval for each result are stated in full. This tool applies the midpoints and blends your costs into a single rate per terabyte.
Read it as a way to size where to look first, not as a number to put in a budget. If you want the estimate tested against your own traffic, that is what the workstreams do.