Residential Proxy

A residential proxy uses IP addresses that are provided by an Internet Service Provider (ISP) to a real household. When you use a residential proxy, your web traffic appears to come from a real person's home internet connection, making it extremely difficult for websites to detect or block.

Residential proxies are typically rotating by default, meaning you get a different IP from the pool on every request (or after a configurable period).

Common use cases:
- Web scraping at scale
- Ad verification
- Price monitoring
- Market research
- Social media management

Pros vs cons:
Extremely high trust level
Access to any geography (190+ countries)
Slower than ISP/datacenter proxies
Usually priced per GB of bandwidth

How it works

A residential proxy network is a pool of consumer devices (home routers, mobile phones, opted-in SDK installs) that relay traffic on behalf of the provider's customers. When your request enters the gateway, the provider's router picks a peer device matching your filters (country, city, ASN, sticky-session id) and tunnels the request through it. The target site sees the peer's home IP and routes the response back through the same tunnel.

Because the IP belongs to a real residential connection, anti-bot stacks rate it as a legitimate user and rarely challenge it on reputation alone. The trade-off is bandwidth: every byte travels through a consumer link, so providers charge per GB rather than per IP. Murphy runs 25M+ residential IPs across 190+ countries, with rotation on every request by default and sticky sessions up to 30 minutes when you need to hold the same IP for a multi-step flow.