docs: document residential proxy IP rotation behavior

Customers are confused when they see different IPs across browser tabs
with residential proxies. Add a warning callout, an "IP Rotation Behavior"
section explaining per-connection rotation, and a comparison table
(residential vs ISP) so users can pick the right proxy type.
Also add an Info callout to the proxies overview page.

Made-with: Cursor

Author: ulziibay-kernel

proxies/overview.mdx

@@ -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:

proxies/residential.mdx

@@ -4,6 +4,27 @@ title: "Residential Proxies"
 
 Residential proxies route traffic through real residential IP addresses. They support advanced targeting options including city, state, and operating system.
 
+<Warning>
+Residential proxies use **rotating exit IPs** — each new connection may route through a different residential IP address within your targeted region. 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.
+</Warning>
+
+## 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.
+
+| Feature | Residential | ISP |
+| --- | --- | --- |
+| IP stability | Rotating — changes per connection | Static — consistent across all connections |
+| IP authenticity | Real consumer devices | ISP-assigned IPs hosted in data centers |
+| Best for | Web scraping, data collection, avoiding rate limits | Session-based workflows, account management, login flows |
+| Geo-targeting | Country, state, city, ZIP, ASN | Country |
+
 ## Configuration
 
 Create a residential proxy with a target country: