Residential proxies by ISP, state, city and ZIP

Why target by ISP instead of by country?

Because many things on the web depend on the network, not only on the place. A broadband provider's site greets its own customers differently from visitors on a rival network. Ad campaigns can target one ISP's subscribers. CDNs and security systems may treat cable, fiber and fixed wireless traffic differently. A bug may only appear for customers of one provider.

Country-level IPs land on whatever network happens to be online. ASN targeting lets you choose: Comcast against AT&T in Atlanta, Spectrum against Google Fiber in Kansas City, Verizon Fios against Optimum in New York. The ISP pages list the right AS numbers, and the city pages show which providers the FCC reports in each city.

What does the username look like?

Everything goes in the username, in this order: USERNAME-country-{cc}-state-{state}-city-{city}-zip-{zip}-asn-{asn}-session-{id}-ttl-{minutes}. Only the country is required; leave out any segment you do not need.

• USERNAME-country-us: any US home IP.
• USERNAME-country-us-asn-20115: Charter Spectrum's main network.
• USERNAME-country-us-state-fl-asn-33363: Spectrum's former Bright House network in Florida.
• USERNAME-country-us-state-wa-city-seattle-asn-209: CenturyLink or Quantum Fiber in Seattle.
• USERNAME-country-us-zip-60614: any home in ZIP 60614 (Lincoln Park, Chicago).
• USERNAME-country-us-asn-7018-session-qa7-ttl-30: one AT&T IP kept for up to 30 minutes.

The combining guide explains which filters to drop first when a request finds no IP.

# 1) exit IP through the proxy (AT&T, AS7018, Atlanta)
IP=$(curl -s -x http://gw.broadbandproxies.com:7777 \
  -U "USERNAME-country-us-state-ga-city-atlanta-asn-7018:PASSWORD" \
  "https://api.ipify.org")
echo "$IP"

# 2) which network announces it (RIPEstat, called directly)
curl -s "https://stat.ripe.net/data/prefix-overview/data.json?resource=$IP"

Rotating or sticky: which session should I use?

Rotating mode suits checks where each request stands alone, such as one product page per IP. Each new connection gets an IP from the pool, usually a different one; to get a new IP on every request, send one request per connection (turn off keep-alive).

Sticky mode suits anything that needs the same IP across several steps, such as loading a page and its follow-up requests, or a short manual session in a browser. Add -session-<id>-ttl-<minutes>: sticky sessions last up to 30 minutes (the IP can change earlier, for example if the home device goes offline). A home device can go offline, so plan for a new session ID if the IP drops.

Where do the IPs come from?

We resell residential and mobile IPs from established upstream partner networks. Our upstream provider confirms that device owners opt in and can opt out, and that its supply does not come from seized or disrupted networks such as NetNut or IPIDEA. Targeting an ASN selects the network of the home device that relays your request; it does not mean the ISP supplies, knows about or endorses the IP. That is also why the pool for each ISP rises and falls through the day: ASN availability varies by network, city and time of day; the checkout shows what is online, and no IP count per ISP is published. More on the sourcing page.