Operations

What is Proxy Pool?

A proxy pool is the set of IP addresses a provider can route your traffic through. Its usefulness comes from composition as much as from size: how many distinct subnets and autonomous systems it spans, how many countries it reaches, how heavily each address is reused, and how clean those addresses look to the sites you target.

Advertised pool sizes mean little on their own. A provider counting every address seen over the past year reports a number far above what is online at this moment, and none of it says how many addresses are reachable in the one country you need. The figure worth having is the count of distinct IPs you receive for your target geography across a fixed sampling window. A few thousand requests with the exit address logged answers that question in an afternoon.

Diversity beats raw count. Two thousand addresses spread across many /24 blocks and several carriers behave very differently from twenty thousand sitting in a handful of hosting ranges, because defenders block by subnet and by ASN as readily as by single address. Mobile pools invert the usual arithmetic. A carrier NAT gateway can put thousands of genuine subscribers behind one public address, so the pool is small in IP count while each address carries traffic no site can afford to ban outright.

How the provider hands addresses out is part of the pool. Round-robin, random selection and least-recently-used produce different reuse patterns, and reuse is what burns an address on a hard target. Ask whether an IP you are given can go to another customer at the same moment, and how long a released address rests before it comes back into circulation. Ask too whether addresses that have collected blocks get quarantined. Providers that recycle aggressively look larger on the pricing page and perform worse in production.

Test the pool against your own targets, because reputation is per-site. An address that a search engine treats as ordinary consumer traffic can be flagged by a sneaker retailer and ignored by a small e-commerce store. Sample a few hundred exits against the endpoint you care about, recording the success rate along with the type of block you get. Repeat the sample monthly. Pools drift as providers add ranges and lose devices, and an abuse report against one range can change your results without any change on your side.

Where you meet it

Pool size is the first number a salesperson quotes and close to the last one that predicts your results. The question reaches you when a job that ran clean at low volume starts collecting blocks as you scale, because you have worked through the distinct addresses available in that country and are now looping over the same ones. Logging exit IPs per request shows you where the ceiling sits before your success rate does.

Common questions

How big does a proxy pool need to be?

It depends on how many requests one address can make before your target reacts. A tolerant site may accept hundreds of requests from one IP, so a few hundred addresses cover a large crawl. A hard target might block after a handful, and then you need either far more addresses or better ones. Measure against the site you are scraping.

Why do mobile proxy pools contain fewer IP addresses?

Carriers place many subscribers behind each public address through CGNAT, so a mobile pool holding a few thousand addresses stands in for a very large number of real users. Sites cannot block those addresses without also blocking paying customers, which is why a small mobile pool often outperforms a much larger datacenter one.

How do I check the real size of a proxy pool?

Run several thousand requests through the gateway with rotation enabled, targeting the geography you care about, and log the exit IP every time. Count distinct addresses and distinct /24 blocks. If the curve flattens early, you are recycling a small set regardless of the number printed on the pricing page.

Related terms

Rotating Proxy
A rotating proxy changes the exit IP address it presents to the target, either on every request or on a timer, without the client changing its configuration. Your code keeps pointing at one host and port; the provider swaps the address behind it, spreading traffic across a pool of many IPs.
IP Rotation
IP rotation is the practice of changing the outbound address a client uses, on every request, on a timer, or on demand. It spreads traffic so no single address builds up enough volume to be rate limited or banned, and it is the defining behaviour of rotating and backconnect proxy services.
Session
In proxy usage, a session is a span of requests that all exit through the same IP address. It begins when you open a connection or claim a session identifier, and it ends when that identifier's timer expires or the network reassigns the address underneath you. Session control is what separates rotating traffic from a continuous identity.
Sticky Session
A sticky session is a proxy configuration that pins your traffic to one exit IP for a fixed window instead of rotating on every request. You request it through a session identifier in the username or through a dedicated port, and the gateway routes each matching request back to the same node until the timer runs out.
Geotargeting
Geotargeting is choosing which country, region, city or carrier your proxy traffic exits from, so a site sees a visitor located where you want. You select it through parameters in the proxy username, a country-specific hostname, or a dedicated port, and the site reads that exit IP against whichever geolocation database it uses.
Geo-Restriction
Geo-restriction is a service limiting access or content by the visitor's apparent location. The site maps the client IP to a country through a geolocation database, then blocks the request or quietly swaps in a regional catalogue with local pricing. Content licensing, sanctions rules, tax registration and commercial strategy are the usual reasons.
Concurrent Connections
Concurrent connections are the number of proxy connections open at the same moment, counted across your workers rather than over a period. It is a capacity limit, separate from requests per second and from bandwidth. Ten connections can carry thousands of requests an hour when each is short, or almost none when each holds a slow page open.
Backconnect Proxy
A backconnect proxy is a single hostname and port that fronts a pool of many IP addresses. The client keeps one connection string while the provider's gateway assigns a different exit IP per request, per session or on a timer. Rotation and pool health checks happen upstream, where the client cannot see them.

Real 4G/5G mobile and residential IPs

PROXIES.SX runs carrier IPs in 100+ countries with HTTP and SOCKS5 on every endpoint. $4/GB down to $2.40/GB at volume, free endpoints and rotation, and your GB never expire.

View pricing Browse the glossary