Estimate gaming stream delivery capacity from peak viewers, average bitrate, usable egress per server, and a traffic reserve. The result is a network-throughput estimate; encoding load and CDN architecture require separate checks.
Estimated origin/edge servers is calculated directly from the entered scenario. Read it together with the supporting figures so the assumptions remain visible.
Planning estimate only. Verify important athletic, financial, or infrastructure decisions with qualified staff and real-world measurements.
At 25,000 viewers and 6 Mbps, raw traffic is 150 Gbps. A 25% reserve raises planned traffic to 187.5 Gbps, requiring five 40-Gbps servers.
It uses the values shown in the calculator panel and applies only the formula documented on this page.
Zero is accepted where it represents a valid absence of cost, volume, allocation, or activity; fields that form a divisor must remain above zero.
No. The result is a scenario estimate based on your inputs, not a guarantee of athletic, financial, or technical performance.
Change one assumption at a time, calculate again, and compare the main result with the secondary metrics.
Real outcomes can vary because of measurement error, changing participation, individual condition, infrastructure overhead, or other factors outside this simplified model.
| Input | Unit | Role |
|---|---|---|
| Peak concurrent viewers | viewers | Expected peak simultaneous audience. |
| Average stream bitrate | Mbps | Delivered bitrate per viewer. |
| Usable egress per server | Gbps | Sustained usable network throughput. |
| Traffic reserve | % | Headroom for peaks, overhead, and failover. |