Residential Proxies
Residential exits are real devices on real home connections. Every targeting option and every protocol we support works here, and nowhere else.
| Entry points | us-east.gw and ap-southeast.gw |
| Ports | 8000 HTTP and HTTPS · 1080 SOCKS5 |
| 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, HTTPS and SOCKS5 on the standard entry points. SOCKS5 UDP, HTTP/3 and STUN need a UDP-capable entry point. See Protocols.
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 the slowest of the three products. If the target does not require a home connection, Rotating ISP is faster and cheaper.
Was this page helpful?
Thanks. That helps us fix it.