Residential Proxies
Residential exits are real devices on real home connections. Every targeting option and every protocol we support works here, and port 1080 protocols need approval. Rotating ISP, Rotating DC and Scale Residential support only part of that.
This page describes Premium Residential. Scale Residential is a product of its own with no targeting. Premium domains are included in both. See Scale and Premium.
| Entry points | us-east.gw and ap-southeast.gw |
| Ports | 8000 HTTP and HTTPS · 1080 SOCKS5, on approval |
| Billing | By bandwidth |
| Rotation | New exit on every request by default |
Connecting
Section titled “Connecting”What you can target
Section titled “What you can target”Everything. Country, state, city, ZIP code, ASN, device OS and IP version.
curl -x USERNAME:PASSWORD-country-US-region-texas-city-dallas@us-east.gw.rayobyte.com:8000 \ https://checkip.amazonaws.comCombine as many as you like, in any order. See How targeting works.
Protocols
Section titled “Protocols”HTTP and HTTPS work on port 8000 from the start. SOCKS5, SOCKS5 UDP, HTTP/3 and
STUN run on port 1080, which we approve per account.
What to expect
Section titled “What to expect”These are consumer devices, not servers. A device can drop off mid-request, so a single attempt can fail on a request that would succeed on retry. Build retries in from the start. Errors & retries covers the codes and what each one means.
Residential is also slower than Rotating ISP and Rotating DC. If the target does not require a home connection, Rotating ISP is faster.
Was this page helpful?
Thanks. That helps us fix it.