# Traffic pool

A traffic pool is a monthly allowance attached to each dedicated address and summed across all addresses of an order: ten addresses with 100 GB each share one 1,000 GB pool, drawn on by whichever address does the work. It is a middle path between unlimited traffic and strict per-address caps, common on datacenter proxies. When the pool is exhausted, the provider either throttles, bills overage or lets you add traffic.


## How to size an order

Estimate monthly gigabytes for the job, divide by the per-address allowance, and compare with the number of addresses you need for concurrency or location spread; take the larger figure. Adding traffic to an existing pool is usually cheaper than adding addresses you do not need.


## Exhaustion policy

| Policy | Effect on your job |
| --- | --- |
| Throttle | Slower, but keeps running |
| Overage billing | Runs at full speed; surprise on the invoice |
| Hard stop | Fails until the next cycle |


## How it works at ProxShift

ProxShift datacenter addresses bring 100 GB a month each into the order's pool, reset on the order date; when it is exhausted, speed is reduced until the next cycle or until traffic is added, and nothing is billed on top.

Source: https://proxshift.com/glossary/traffic-pool