Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions proxies/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,10 @@ Kernel supports four types of proxies:

Datacenter has the fastest speed, while residential is least detectable. ISP is a balance between the two options, with less-flexible geotargeting. Kernel recommends to use the first option in the list that works for your use case.

<Info>
Datacenter and ISP proxies provide a **stable exit IP** that stays consistent across all connections. Residential proxies use **rotating exit IPs** that may change per connection — see [Residential Proxies](/proxies/residential#ip-rotation-behavior) for details.
</Info>

## Create a proxy

Create a proxy configuration from the types above that can be reused across browser sessions:
Expand Down
14 changes: 14 additions & 0 deletions proxies/residential.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,20 @@ title: "Residential Proxies"

Residential proxies route traffic through real residential IP addresses. They support advanced targeting options including city, state, and operating system.

<Info>
Residential proxies use **rotating exit IPs** — each new connection may route through a different residential IP address within your targeted region. This is because residential traffic is routed through real consumer devices that may go offline at any time, so the network assigns a new available exit node per connection. This means different browser tabs or requests to different websites within the same session can show different public IPs. If you need a consistent IP address across all connections, use an [ISP proxy](/proxies/isp) instead.
</Info>

## IP Rotation Behavior

Residential proxies assign a new exit IP for each new TCP connection. In practice:

- **Same website across tabs**: Tabs connecting to the same domain typically share a TCP connection (via HTTP connection pooling), so they usually see the same IP.
- **Different websites across tabs**: Tabs connecting to different domains open separate connections, so they will likely exit through different residential IPs.
- **Reconnections**: If a connection is closed and re-established (e.g., after a timeout or page idle), the new connection may get a different exit IP.

This behavior is inherent to residential proxy networks, where traffic is routed through real consumer devices that come online and offline dynamically.

## Configuration

Create a residential proxy with a target country:
Expand Down
Loading