What are residential proxies and how do they work
Residential proxies exit through consumer ISP addresses. This explains pools, sticky sessions, what sites see, and what to ask a provider before you buy.
What are residential proxies and how do they work
A residential proxy is an HTTP or SOCKS endpoint whose exit IP belongs to a consumer internet provider. Your request leaves the public internet as if it came from a household connection. That is the whole product. Marketing names do not change the ASN.
People buy this origin when a site already treats hosting ranges as automation. The extra cost buys a different label, not magic. If you are choosing between this origin and a server IP, read residential vs datacenter first.
01How a residential IP gets assigned
A consumer ISP announces a range of addresses for homes and small offices. A proxy provider needs a legal way to send customer traffic out of some of those addresses. Common stories are a peer app that users opt into, or a partnership with the ISP itself.
You connect to the provider’s gateway with a username, a password, and sometimes a session parameter. The gateway picks an exit IP from the pool that matches your filters. The destination site sees that exit IP. It does not see your real address if the proxy is working.
The provider does not move a physical household for you. It routes through capacity it already has in that ISP range. City targeting is only real when that routing can select a subnet in that city. A label without routing is a filter that lies.
02Pools, rotation, and sticky sessions
Most residential products are shared pools. Many customers can exit through the same range over a day. That is how a vendor offers many countries without giving you a dedicated circuit in each one.
Rotation means the exit IP changes. It may change every request. It may change on a timer. Sticky mode asks the gateway to keep the same IP for a window so a login or a cart can finish. The window is a setting. It is not a property of the ISP.
If your client holds cookies across requests, you probably want sticky. If each URL is independent, rotating is simpler. Details live in sticky vs rotating proxies.
Metered billing is the usual residential price model because the provider pays for peer or carrier capacity by traffic. A headless browser with images on will burn data faster than a text crawler. Measure that before you compare two quotes.
03What a site actually sees
The site sees an IP, an ASN, and whatever headers your client sends. A residential ASN looks like a household ISP. That helps on hosts that score hosting networks. It does not hide a bad TLS fingerprint. It does not hide a script that hits every URL in a millisecond.
Geo databases will place the IP in a country, and sometimes in a city. Those databases disagree. Always check the live exit. Open My IP through the proxy and read country plus ASN. If you need a clean reputation for mail or sign-ups, also run IP blacklist.
A residential IP can still be on a blocklist. Pools are shared. Someone else may have used the address. That is why a small test beat a large prepaid plan.
04What to ask before you buy
Ask how the pool is sourced. Peer consent and ISP contracts are the two answers that make sense. If the vendor will not say, look elsewhere.
Ask which filters change routing. Country is the baseline. State, city, and ASN targeting are extras. If the docs cannot explain how a city is selected, do not pay for city.
Ask what sticky hold actually means. Some products keep the same /32. Some only keep the same subnet. Login walls care about that difference.
Ask which protocol the gateway speaks. HTTP CONNECT is enough for many scrapers. SOCKS5 is what some browsers and apps expect. Confirm with the proxy checker.
The catalog cards below are residential-origin services from this site. Read each card for session behavior and countries. Then test.
Bright Data is a large proxy network for data collection: residential, mobile, ISP and datacenter IPs in about 195 countries. Residential traffic can be paid as you go with no subscription, and datacenter and ISP addresses come in packs from 10 IPs. Residential and mobile access requires identity verification.
Residential proxies are a tool for jobs that need a household ASN. They are the wrong tool for open crawls that already work on datacenter proxies. Buy the origin the target requires. Keep the rest of the client honest with rate limits and the site’s published crawl rules.
Related articles
AI proxy vs LLM gateway: what is the difference?
Tell network forwarding, an API gateway, and model routing apart so you pick the layer that matches the job.
Gemini network proxy: configure and diagnose a client connection
Route google-genai through an HTTP CONNECT proxy, keep TLS on, and tell a dead hop from an API refusal without treating a tunnel as Google access.
curl proxy setup: authentication, HTTPS CONNECT and reliable checks
Set an explicit curl proxy, keep -U apart from -u, send HTTPS through CONNECT without -k, and read exit codes against the route you actually used.
