ProxyNomad / Proxies / Residential
Residential proxies
Exits on real household connections, in the neighborhoods your targets serve. Rotating by default, sticky when you need one identity for a while, targeted by country, city or ASN.
$4.00/GB
Volume tiers to $2.20/GB. Metered on delivered traffic only. Purchased traffic does not expire.
What it is
An address that belongs somewhere.
A residential exit is a real consumer connection: an address a target sees as a household on a local ISP, because that is what it is. Sites that fingerprint and block datacenter ranges treat these requests the way they treat their own users, which is the entire point.
Our residential supply comes from consumer devices whose owners have opted in to share bandwidth through partner applications and are compensated for it. We do not name partners, and we hold the whole chain to the same rules: what may run through these addresses is written in our acceptable use policy, and we vet every customer against it before credentials go out. A clean pool stays clean by refusing traffic, not by apologizing for it.
- Protocols
- HTTP CONNECT on port 7000, SOCKS5 on 7001
- Rotation
- New exit per request by default
- Sticky
- Same exit up to 30 minutes via
sessionparameter - Targeting
- Country, city, ASN, combinable
- Auth
- Username and password, or IP allowlist
- Concurrency
- No hard cap, fair use
- TLS
- End to end. We tunnel, we do not inspect.
Fit
When residential is the right call, and when it is not.
Use it for
- Marketplaces, retail and travel sites that block datacenter ranges
- SERP and rank tracking where results must come from a real city
- Price intelligence, seeing what a local shopper sees
- Ad verification against geo-targeted campaigns
- Any target where your datacenter success rate has fallen below what you can retry away
Do not use it for
- Unprotected sites and open APIs: datacenter does the same job at $0.60/GB
- Long-lived logins that must keep one address for weeks: that is ISP
- Mobile-only apps and the hardest anti-bot stacks: that is mobile
Paying residential rates for a job that does not need them is the most common mistake in this market. We will point it out.
Sessions & targeting
Routing lives in the username.
Append segments to your username and the gateway does the rest. country-br pins the country. city-sao_paulo pins the city. asn-26599 pins the network. Add session-<any id you invent> and the exit holds for up to 30 minutes; if the device behind it goes offline, you get a replacement from the same targeting scope and the session id keeps working.
A 502 from the gateway means we had no healthy exit for your targeting at that moment. It is not billed, and if you see it more than rarely on a broad target, that is a bug on our side: tell us.
# same exit for the whole crawl session S="session-checkout_7f2" curl -x "http://USER-country-br-city-sao_paulo-$S:PASS@gate.proxynomad.com:7000" \ https://ifconfig.me # run it twice: same IP both times
Pricing
Residential tiers
Price breaks apply to the size of a single purchase. Traffic does not expire while your account is open.
Above a terabyte a month, talk to us and bring your target list: the price depends on what the traffic looks like, and we would rather quote it honestly than pad a rate card.
Questions
Asked by people who have been burned before.
How clean are the IPs, really?
Clean is a process, not a property. Exits are checked against public blocklists and reputation feeds on admission, monitored while they serve, and dropped when they degrade. Customer vetting keeps the abusive traffic out that burns pools in the first place. We will not quote you a percentage because a pool percentage is unverifiable from the outside; run a trial against your actual target and measure your success rate. That number is the real answer.
What exactly is billed, and what is not?
You pay for bytes delivered through the gateway, both directions, measured at the gateway. A request that fails inside our network, a 502 because no exit matched, a tunnel that never established, costs nothing. A response from the target is delivered traffic even when it is a 403: we moved the bytes, and pretending otherwise would just be hidden in the rate. That is the boundary. Every provider has the same one; we state it.
What happens when a target blocks an exit?
You will see whatever the target serves, a 403, a CAPTCHA, an empty 200, and your next request rotates to a different exit automatically unless you asked for a sticky session. We do not silently retry for you; scraper logic differs too much for that to be safe. If a specific target starts failing across many exits at once, that is exactly the moment to write to us. Tuning against a named target is normal support here, not a professional services invoice.
Do you cap concurrency or requests per second?
No hard caps. Hundreds of concurrent connections are routine. If you plan to run tens of thousands of concurrent sessions or point sustained load at a small city pool, tell us in advance and we will make sure the pool depth is there before you start, instead of you finding out mid-job.
Can I authenticate by IP instead of credentials?
Yes. Allowlist your server IPs from the dashboard and skip proxy auth entirely. Targeting then moves into an X-Nomad-Route header, documented in the quickstart.
Test it against the target that hurts.
Not a demo site. Bring the one that blocks you today, and measure.