Proxy Pool
A collection of proxy IP addresses managed by a provider, from which IPs are assigned to users for each request or session.
A proxy pool is the full set of IP addresses a proxy provider manages and makes available. When you send a request through a rotating proxy, the provider's gateway picks an IP from this pool and routes your traffic through it.
Pool size directly affects detection avoidance. A pool of 10,000 IPs cycling through requests at high volume will repeat the same IPs frequently - increasing the chance of hitting an already-flagged address. A pool of 50 million IPs rarely repeats.
Pool quality matters as much as size. A large pool where 30% of IPs are already banned on major sites is less useful than a smaller pool with clean, well-maintained IPs. Providers with strict fair usage policies and regular pool cleaning maintain better IP reputation.
Shared vs. dedicated pools: in a shared pool, multiple customers use the same IP addresses. An IP one customer burned may affect your requests. Dedicated pools assign IPs exclusively to you - cleaner but more expensive.
Geographic distribution within the pool determines targeting options. A pool with 50 million IPs concentrated in the US provides less flexibility for European targeting than a more geographically distributed pool of the same size.
A pool is a set of exits and the rules around it
A proxy pool is the collection of addresses available to you, plus whatever logic decides which one serves the next request. In a gateway product the pool belongs to the provider and the logic is theirs. In a list product the pool is the addresses you bought and the logic is yours to write.
Pool quality is not the same as pool size. What matters is how many addresses are usable for your specific target and geography at the moment you need them. A pool of eighty million addresses is irrelevant if only a handful are online in the city you asked for.
Pools also have composition. A mix of residential, ISP and datacenter addresses behaves differently against a single target than any of them alone, which is why mature setups route by target rather than sending everything through one pool.
Your pool with us
Residential is our pool, static products are yours. Most setups end up using both:
Two kinds of pool
Provider pool proxy.sotaproxy.com:10000, exits chosen per connection
targeting by suffix, no management on your side
Your pool ISP, datacenter and IPv6 addresses you own
you decide rotation, resting and retirement- Route by target, not by habit. Public pages on datacenter, protected pages on residential, accounts on ISP or mobile.
- Track which address served which request. Without that record you cannot tell a bad address from a bad target.
- Give addresses in your own pool a rest between passes rather than cycling them at maximum speed.
- For city-level work, expect availability to move. A 400 means the pool for that city is empty right now, not that the city is unsupported.
Pool myths
Bigger is not better
Coverage where you need it beats a headline number. Ask about your countries, not about the total.
A pool is not a guarantee of uniqueness
Residential exits are shared with other customers over time, just not simultaneously within your session.
Pool size does not fix rate limits
The target counts per address. A larger pool helps only if you actually spread across it.
One pool rarely fits every target
Sites differ in what they filter. Mixed routing beats a single expensive pool.
Related terms
See this in practice
Ready to use proxy pool?
SotaProxy gives you access to rotating residential, mobile, datacenter, and ISP proxies. No minimum commitment.
Get started