Start Free TrialLog In

Glossary

What Is an IP Pool?

An IP pool is the collection of IP addresses a proxy provider can assign as exit IPs for customer traffic, typically spanning many subnets, ASNs, and geographies.

Understand what makes a proxy pool useful (size, diversity, freshness, geo coverage), why pool quality beats pool size beyond a threshold, and how to evaluate one.

Explained

An IP pool is the underlying inventory of IP addresses a proxy gateway can route customer traffic through. When you connect to a rotating proxy and the gateway picks an exit IP, it picks from this pool. Pool quality is the single biggest variable that determines whether your scraping or verification workload succeeds.

Three dimensions matter when evaluating an IP pool: size (raw count of available IPs), diversity (number of distinct subnets and ASNs covered), and geo coverage (how many countries / cities / ISPs are represented). A pool with 10M IPs spread across 1000 subnets is usually more effective than a pool with 100M IPs concentrated in 50 subnets, because anti-bot systems track IPs at the subnet and ASN level, not just the individual IP.

Freshness also matters. Residential pools that grow through opt-in SDK partnerships continuously cycle IPs in and out as users join and leave the network. A pool that's been stagnant for months will have more IPs already flagged on common targets than a pool that refreshes weekly.

How It Works

Residential proxy providers maintain their pool by partnering with applications and SDKs that users opt into in exchange for free or premium features. When a user is online and the SDK is active, their device contributes its IP to the proxy pool for the duration. The provider's gateway treats the device as an available exit endpoint, routes a small amount of customer traffic through it, and removes it from the pool when the user goes offline.

Large providers maintain millions of devices in the active pool at any given moment, with new devices coming in and out continuously. The gateway selects exit IPs based on geo filters, IP health, and load balancing, presenting customers with a single endpoint that abstracts away all the underlying churn.

Types

Residential IP Pool

Pool of IPs assigned to real consumer devices by ISPs. Highest trust score on protected sites; the IP type used for most modern scraping and verification work.

ISP / Static Residential IP Pool

Pool of IPs registered with consumer ISPs but hosted on datacenter infrastructure. Smaller and more stable than residential proxies, used for sticky workflows.

Mobile IP Pool

Pool of IPs assigned by mobile carriers via 4G/5G. Smallest in raw count but highest trust due to CGNAT, used for the most sensitive workflows.

Datacenter IP Pool

Pool of IPs from cloud and hosting providers. Cheap and fast, but easily detected by anti-bot systems on protected targets.

Common Use Cases

Scaling rotating-proxy throughput across diverse subnets
Geo-targeted scraping with deep per-country coverage
Avoiding repeat-offender bans by drawing from a large fresh pool
Multi-account workflows with one IP per account
Long-tail city / ASN coverage for niche markets
FAQ

Frequently asked questions

Common questions about ip pool.

Shifter maintains a residential pool of over 205M IPs spread across 195+ countries with city-level granularity in major markets. The pool refreshes continuously as devices come on and off the network.

Up to a threshold, yes. Beyond that threshold, diversity matters more than raw count. A 10M-IP pool spread across 1000 subnets and 200 ASNs is more effective for evading anti-bot systems than a 100M-IP pool concentrated in 50 subnets, because most detection systems track IPs at the subnet/ASN level.

Residential providers grow the pool through opt-in SDK partnerships with apps, where users explicitly consent to share idle bandwidth and IP capacity in exchange for premium app features. ISP and mobile pools grow through commercial partnerships with ISPs and carriers.

In a healthy residential pool, the average IP cycles in and out as users come online or change networks. The 'freshness' you see on a per-request basis depends on how recently each IP was assigned to its current device by the ISP. Major providers see high churn, which keeps the pool fresh.

Most rotating proxy providers don't expose the full pool list because the underlying device pool is constantly churning. You can verify an exit IP per request by inspecting the response or using an IP-echo endpoint.

Rotate to a fresh IP. The size and diversity of the underlying pool determine how often you'll hit a clean IP on the next try. Larger, more diverse pools mean fewer rotations to find a working IP. Shifter's pool is sized so this is rarely a meaningful constraint.