Web scraping · Residential recommended
A crawler from one address is trivial to spot: hundreds of requests a minute from a hosting range, no browser history, the same fingerprint on every hit. Targets answer with rate limits, CAPTCHAs, empty pages or silent bans. A residential pool turns that stream into thousands of ordinary visitors from the countries you need, so the data you collect is the data a real user would see.
01 — Which network
A recommendation is only useful with its trade-offs. The cards below say what each network does well for web scraping, and where it stops being worth the money.
Rotation on every request across real households defeats rate limits and bot scores. City and ASN targeting reproduce what local users see. Per GB, never expires.
Cheapest per request for targets that do not fingerprint hosting ranges: public APIs, sitemaps, your own properties, low-protection catalogues.
Only when the crawl needs a login that must stay on one address; otherwise you pay for stability you do not use.
Overkill for most collection, but the fallback for targets that block everything else.
02 — The recipe
The settings that matter for web scraping, and a working example on the right. Replace USER and PASS with the credentials issued at signup.
import requests
proxy = "http://USER-cc-us:[email protected]:9000"
session = requests.Session()
session.proxies = {"http": proxy, "https": proxy}
for url in urls:
r = session.get(url, timeout=30) # a new US household on every request
if r.status_code in (403, 429):
r = session.get(url, timeout=30) # retry once: different exit already
parse(r.text)03 — Budget
Per-GB pricing is predictable once you know your page size. Enter your monthly volume; the average size is pre-filled with a realistic figure for this job and can be changed.
average page size (HTML only)
Residential rate ladder, identical in every country. Buying the month's traffic in one purchase reaches the tier shown; smaller top-ups are priced at their own tier. Full ladder.
04 — Best practices
The pool is rarely the problem. These four habits decide the success rate and the bill.
Scrape the German store from German households; mixed locations trigger consistency checks and skew prices.
Multi-page flows (search, then result pages) work better on one sticky exit for a few minutes than on a new IP per hop.
Block images, fonts and trackers in headless browsers: you pay per GB, and HTML is a small fraction of a page.
Rate-limit per domain, honour robots.txt where it applies, and never collect personal data you have no basis to hold.
05 — Questions
Start with datacenter if the target does not challenge you: it is the cheapest per request. The moment you see CAPTCHAs, 403s or degraded content, move that target to residential; the per-GB price buys the success rate.
HTML alone is usually 100 to 500 KB per page. Half a million pages at 350 KB is about 170 GB, which costs around $262 on the residential ladder. Headless browsers that load images can multiply that by five; block them.
Collecting publicly available data is allowed. Attacking a site, bypassing authentication, or harvesting personal data without a legal basis is not, and the acceptable use policy is enforced.
Yes, on the same account. Omit the session parameters for rotation; add -sid- and -ttl- on the requests that must share an IP.
It depends on the target far more than on the pool. Well-behaved crawlers on residential exits typically see the vast majority of requests succeed; the rest is retried on a fresh IP at no extra cost beyond the bytes.
Ready when you are
Create your account, top up $10 and try the recipe above on your real target. What you do not use stays on your balance.