Bandwidth pooling: one balance or several separate purchases
Bandwidth pooling says where the traffic you bought can be spent. An account-wide pool serves every user, project or proxy type from one balance; a per-plan or per-user allowance cannot be moved. The difference decides whether you can make one larger purchase at a lower rate or must keep several small balances, each with its own minimum and its own leftovers. The box below shows what the plans we track say today.
Where purchased traffic can be spent, on the 164 plans sold by the GB, checked up to Nov 17, 2026:
- 28 share one balance across the account, at 8 providers.
- 28 keep each plan's traffic to that plan, at 2 providers.
- 1 splits the traffic between sub-users you set, at 1 provider.
- 107 do not say.
Term · The comparison uses prices checked up to Nov 17, 2026; every figure in the text keeps the date it was checked.
On this page
What a shared balance saves
With one balance, a quiet project’s traffic is used by a busy one instead of expiring. Several separate balances each need their own package, usually at a higher rate per GB, and each can end the month with traffic left over. Some providers go further and let one balance pay for residential and mobile traffic alike.
Sub-users
Many providers let you create sub-users with their own login. On some, you set each sub-user’s share of the traffic; on others, they all draw on the account’s one balance. Check which before you give a team or a customer its own access.
When a plan does not say
Most plans do not say whether their traffic is pooled. Until the provider confirms it, treat each plan’s traffic as usable only by that plan when you work out how much to buy.
Price it for your amount
Checkout totals, every billing type competing. Change the amount to recalculate.
Geonode
$34.65Residential monthly subscription · Monthly
Checked Nov 17, 2026 · $0.69 per GB used
Buy at Geonode →GB and IP packages use separate amounts and billing units.