A proxy pool is the set of exit IP addresses or proxy endpoints available for a service to assign to client connections. Rotation and session systems select exits from this set according to availability and the client’s requested constraints.

Pool size describes how many exits are available, but size alone says little about usefulness. A workable pool also needs exits that are online, responsive, correctly classified, and available in the locations a request needs. Thousands of unreachable or repeatedly blocked addresses do not provide the same value as a smaller set of healthy exits. Distribution matters too because many addresses from one network range can share the same reputation or block boundary.

Residential pools naturally experience churn. Household devices disconnect, internet addresses change, and participants stop or start sharing bandwidth. A provider must remove unavailable exits and update selection as the active set changes. Clients should still expect occasional connection failures and use bounded retries rather than assuming every chosen exit will remain reachable.

A rotating proxy draws new assignments from the pool. A sticky session asks the selection system to retain one exit for related work, subject to availability. How residential proxies work explains where the pool fits in the connection path.

Related terms: exit node and rotating proxy.

Browse all glossary terms

Use residential proxies with your own workflow.