Managing the Geyser of IPs

Buying a proxy pool is easy; operating it is a discipline. Most providers give you a gateway URL you can plug into requests, then all of the pool complexity is hidden behind that single endpoint. Understanding how that gateway works—and how to steer which IP you get—separates scrapers that survive months from scrapers that get banned in a day.

Backconnect Gateways

A backconnect gateway is a load balancer in front of the pool. Your HTTP request hits the gateway, and the gateway forwards it through a specific exit IP chosen by its rotation logic.

  • Rotating (Every Request): The gateway gives you a fresh exit IP per request. Perfect for wholesale page downloads, but useless when you need a login session.
  • Sticky (Timed): The gateway keeps you on the same exit IP for a configurable window (typically 5–30 minutes). Within that window every request shares cookies, TLS session, and reputation continuity.
  • Sticky (Bounded): The gateway holds the IP until it has served N requests or until the target site bans it, then rotates. This is the classic "sneaker bot" mode.

The choice of rotation mode must match the shape of your job. A job that hits 10,000 distinct product pages with no cookies has no reason to be sticky. A job that signs in, adds items to a cart, checks out, and repeats absolutely must be sticky—otherwise a mid-session IP swap looks like account hijacking to the WAF.

Session Continuity Is Data

Think of a session as a bundle of correlated signals: IP, TLS parameters, cookies, fingerprint, and visit history. WAFs model sessions the same way you do. If your cookies say "same user", your fingerprint says "same device", but your IP suddenly jumps from California to Germany, the correlation breaks. Staying sticky on one IP for the entire logical workflow keeps all those signals mutually consistent.

Geo-Alignment

Residential providers let you filter exits by country, region, and sometimes city. Always align geography with the content you are fetching: a scraping job reading localized Japanese retail sites from a US residential IP will trigger anomaly signals that a local Japanese IP would never see. When a site legitimately uses geo-gating, a mislocated IP is a guaranteed red flag.

Pool Health and Recycling

Provider pools recycle. When a homeowner unplugs the router, that IP vanishes from the pool and reappears elsewhere. Your code must treat rotating exits as the norm: never hardcode an IP, always expect connect timeouts, and structure retries so that a dead exit simply means "try the next IP". Also monitor your own ban rate per pool segment. If 10% of one provider's subnets return 403s while another provider stays clean, rebalance your traffic toward the clean pool.

Pricing Models

  • By GB: residential and mobile proxies bill on bandwidth. High-throughput HTML scraping becomes expensive fast.
  • By IP count: datacenter proxies bill per IP slot. Ideal for many long-lived socks.
  • By concurrent session: some providers bill by simultaneous gateway sessions, which fits headless-browser workloads better than raw bandwidth.

Choose the billing model that matches your traffic profile. Paying per gigabyte for a text-only scrape wastes money; renting 10,000 IPs to run 50 slow browsers wastes money the other way.