Proxy pool sizing
How Many Proxies Do I Need for Multiple Accounts?
A stable sizing method for account workflows, browser profiles and long-running sessions.
Practical estimate
For multiple accounts, the safest starting point is one stable proxy per important account or browser profile. Shared pools may work for low-value tests, but identity-sensitive accounts should not constantly change IP.
Workload
Pool
Reserve
BuyProxies guide
A good proxy count is not the biggest count. It is the smallest pool that keeps sessions stable, avoids repeated failures and leaves enough reserve for retries.
Simple formula
Starting pool = active sessions ÷ safe sessions per proxy × location multiplier × 1.25 reserve.
Count active accounts first, then decide whether any low-risk accounts can share a proxy. Add reserve for account replacement, location splits and failed IPs.
Example pool sizes
| Workload | Starting point | Why |
|---|---|---|
| 5 important accounts | 5-7 proxies | One per account plus reserve. |
| 25 browser profiles | 25-35 proxies | Stable assignment keeps troubleshooting clean. |
| Mixed low/high value accounts | One per high-value account; limited sharing for low-risk tests | Avoid treating all accounts equally if risk differs. |
When to add more proxies
Add more proxies only when the current pool is healthy but capacity is the bottleneck. If many requests fail because credentials are wrong, the country is wrong or the target is blocking the workflow, a bigger pool just spreads the same mistake over more IPs. First fix connection quality, request pacing and session rules, then increase capacity.
A useful rule is to scale in visible steps. Increase the pool, run the same workload, compare error rate and keep the change only if useful results increase without a matching increase in blocks, timeouts or support work. For location-sensitive workflows, treat every country as its own pool instead of averaging all proxies together.
How to size the pool
- Group accounts by importance and location.
- Assign one proxy to each important account.
- Keep the same proxy through the session lifecycle.
- Use reserve proxies for replacements, not constant rotation.
- Track account, proxy, browser profile and cookie state together.
A simple calculation example
Suppose the workload needs 30 active sessions and you are comfortable with 2 active sessions per proxy. The base pool is 15 proxies. If the job runs in two countries, split that into two location pools instead of one mixed pool. Then add reserve capacity for retries, maintenance and unexpected target friction. With a 25% reserve, that 15-proxy base becomes about 19 proxies before you round up for location coverage.
This calculation is not meant to be perfect. It gives you a safe starting number that can be measured. After the first run, compare successful results, retries, timeouts and manual fixes. If success rate is high but the queue is too slow, add proxies. If error rate is high, fix the workflow before buying more capacity.
Sizing mistakes
- Sending many accounts through one proxy.
- Rotating identity mid-session.
- Changing proxy, cookies and fingerprint at the same time.
- Ignoring country consistency between account and proxy.
FAQ
Can multiple accounts share one proxy?
They can, but it increases correlation and troubleshooting risk.
Should accounts use rotating proxies?
Usually no. Stable sessions are safer for account workflows.
How much reserve do I need?
Keep at least 10-25% reserve depending on how costly account disruption is.