Networking
When bandwidth pooling makes sense
How shared contracted capacity helps multi-server streaming fleets when traffic moves between nodes.
Pooling solves uneven demand
A multi-server fleet rarely uses every node at the same time. One region may spike while another is quiet; one channel may surge while a VOD node idles.
A pool lets the commercial capacity model follow the fleet instead of trapping unused capacity on the wrong server.
Physical limits still matter
A bandwidth pool does not change each server's physical port. A 10 Gbps server cannot push 40 Gbps just because the total pool is larger.
Treat pooling as fleet capacity planning and billing, not a replacement for correct per-node sizing.
Confirm the terms before launch
Alerting thresholds, upgrade paths, overage handling, eligible servers, and measurement windows should be confirmed before relying on a pool for production traffic.
The public page describes the model; the written quote should define the commercial rules.
Related next steps