Residential proxies

A residential proxy sends your request through an IP address that an ISP assigned to a home connection. Target sites see an ordinary consumer network in the location you picked.

When they are the right tool

Use them when the answer depends on who is asking and from where: localized search results, regional prices, ads shown only in one market, or sites that respond differently to data center ranges. For testing your own service from a fixed address, a residential proxy is usually more than you need.

Rotating IPs

By default the IP changes on every request. That suits work where requests do not depend on each other, such as checking many separate pages.

Sticky sessions

To keep one IP, add a session to the proxy username: a six-character ID that you choose, plus a duration in minutes. The same session ID keeps the same IP, and a new ID gets a new one. Home connections can go offline, so a long job should be ready for the IP to change. How to choose between the two.

Location targeting

Without any options, each request gets a random IP worldwide. You can pick one or several countries, or within a single country a state and city or an ISP. State and city codes are listed per country in the dashboard. See available locations.

Protocols

Connect over HTTP on port 8080, which also carries HTTPS sites through a tunnel, or over SOCKS5 on port 1080. Both use the same credentials. The developer guide has working examples.

Billing and control

You pay for gigabytes, not IPs or time. The dashboard shows used and remaining traffic and hourly usage, and lets you reset the proxy password or pause a plan. See current prices.

What we do not claim

We do not publish pool sizes or success rates: they depend on the target and the location, and we have no measurement that would be honest for your job. Test with a small pack before you commit to a large one.