From 8ada16be223c151bf17d2581c6b783532ff19923 Mon Sep 17 00:00:00 2001 From: masnwilliams <43387599+masnwilliams@users.noreply.github.com> Date: Fri, 15 May 2026 17:53:11 +0000 Subject: [PATCH 1/2] clarify managed proxy IP stability is per-session, not across sessions MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Managed ISP/datacenter proxies are stable within a session but do not guarantee the same egress IP across sessions. For destinations that need a single static IP across every session — IP allowlists, managed-auth connections whose health checks and reauths must look like the same client — point a custom (BYO) proxy at infrastructure you control. --- auth/configuration.mdx | 4 ++-- proxies/datacenter.mdx | 4 +++- proxies/isp.mdx | 4 +++- proxies/overview.mdx | 4 +++- 4 files changed, 11 insertions(+), 5 deletions(-) diff --git a/auth/configuration.mdx b/auth/configuration.mdx index 229dc13..e02d694 100644 --- a/auth/configuration.mdx +++ b/auth/configuration.mdx @@ -66,9 +66,9 @@ Pin the auth flow to a specific [proxy](/proxies/overview) so logins, health che How stable the exit IP is depends on the proxy type: -- **[ISP](/proxies/isp)** and **[datacenter](/proxies/datacenter)** proxies provide a static exit IP that stays consistent across all connections. +- **[ISP](/proxies/isp)** and **[datacenter](/proxies/datacenter)** proxies provide a stable exit IP within a single session, but Kernel does not guarantee the same IP across sessions. Sites with adaptive auth that trigger a step-up challenge (one-time code, device verification) when the client IP changes may flag the IP shift between the initial login and a subsequent health check or reauth. - **[Residential](/proxies/residential)** proxies rotate IPs per connection — use them when you need legitimacy from a real ISP pool but can tolerate IP changes. -- **[Custom (BYO)](/proxies/custom)** proxies route through whatever you point them at, so this is the right pick if you need a truly static IP under your own control (e.g. an allowlisted egress your security team owns). +- **[Custom (BYO)](/proxies/custom)** proxies route through whatever you point them at, so this is the right pick if you need a truly static IP that persists across the initial login and every subsequent health check and reauth (e.g. an allowlisted egress your security team owns). Create a proxy first, then attach it to the connection: diff --git a/proxies/datacenter.mdx b/proxies/datacenter.mdx index ec7249b..c08292b 100644 --- a/proxies/datacenter.mdx +++ b/proxies/datacenter.mdx @@ -6,7 +6,9 @@ Datacenter proxies use IP addresses assigned from datacenter servers to route yo ## IP Rotation Behavior -Datacenter proxies provide a **static exit IP** — the same IP address is used for all connections throughout the lifetime of the proxy. Every tab, request, and reconnection within a browser session exits through the same IP. +Datacenter proxies provide a **stable exit IP within a single browser session** — every tab, request, and reconnection inside that session exits through the same IP, and it does not rotate mid-session (unlike residential). + +Across separate sessions, Kernel does not guarantee the same exit IP from a managed datacenter proxy. If a destination site requires the exact same IP across every session — for example, an IP allowlist, or a [managed auth](/auth/overview) connection whose health checks and reauths must look like the same client — use a [custom (BYO) proxy](/proxies/custom) pointed at infrastructure you control. ## Configuration diff --git a/proxies/isp.mdx b/proxies/isp.mdx index 7b9393f..c06abc4 100644 --- a/proxies/isp.mdx +++ b/proxies/isp.mdx @@ -6,7 +6,9 @@ ISP (Internet Service Provider) proxies combine the speed of datacenter proxies ## IP Rotation Behavior -ISP proxies provide a **static exit IP** — the same IP address is used for all connections throughout the lifetime of the proxy. Every tab, request, and reconnection within a browser session exits through the same IP. This makes ISP proxies ideal for session-based workflows, login flows, and any use case where a consistent IP is important. +ISP proxies provide a **stable exit IP within a single browser session** — every tab, request, and reconnection inside that session exits through the same IP, and it does not rotate mid-session (unlike residential). + +Across separate sessions, Kernel does not guarantee the same exit IP from a managed ISP proxy. If a destination site requires the exact same IP across every session — for example, an IP allowlist, or a [managed auth](/auth/overview) connection whose health checks and reauths must look like the same client — use a [custom (BYO) proxy](/proxies/custom) pointed at infrastructure you control. ## Configuration diff --git a/proxies/overview.mdx b/proxies/overview.mdx index 5299d5f..52a4dee 100644 --- a/proxies/overview.mdx +++ b/proxies/overview.mdx @@ -16,7 +16,9 @@ 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. -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. +Datacenter and ISP proxies provide a **stable exit IP within a single browser session** — the IP does not rotate mid-session. Across separate sessions, however, Kernel does not guarantee the same exit IP. If you need a truly static IP that persists across every session (for example, an IP allowlist or a [managed auth](/auth/overview) connection whose health checks must egress from a single IP), use a [custom (BYO) proxy](/proxies/custom) pointed at infrastructure you control. + +Residential proxies use **rotating exit IPs** that may change per connection — see [Residential Proxies](/proxies/residential#ip-rotation-behavior) for details. ## Create a proxy From b4abc504385ed80ebb3ab19cca4ee21c0482e603 Mon Sep 17 00:00:00 2001 From: masnwilliams <43387599+masnwilliams@users.noreply.github.com> Date: Fri, 15 May 2026 18:47:23 +0000 Subject: [PATCH 2/2] collapse cross-session IP caveat to a link to overview per-proxy pages now state only the per-session stability fact and link to proxies/overview for the cross-session caveat, so the detailed explanation lives in one place. --- proxies/datacenter.mdx | 2 +- proxies/isp.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/proxies/datacenter.mdx b/proxies/datacenter.mdx index c08292b..21a9a96 100644 --- a/proxies/datacenter.mdx +++ b/proxies/datacenter.mdx @@ -8,7 +8,7 @@ Datacenter proxies use IP addresses assigned from datacenter servers to route yo Datacenter proxies provide a **stable exit IP within a single browser session** — every tab, request, and reconnection inside that session exits through the same IP, and it does not rotate mid-session (unlike residential). -Across separate sessions, Kernel does not guarantee the same exit IP from a managed datacenter proxy. If a destination site requires the exact same IP across every session — for example, an IP allowlist, or a [managed auth](/auth/overview) connection whose health checks and reauths must look like the same client — use a [custom (BYO) proxy](/proxies/custom) pointed at infrastructure you control. +For cross-session IP stability (e.g. IP allowlists or [managed auth](/auth/overview) health checks), see [IP rotation behavior across proxy types](/proxies/overview). ## Configuration diff --git a/proxies/isp.mdx b/proxies/isp.mdx index c06abc4..94bc2f5 100644 --- a/proxies/isp.mdx +++ b/proxies/isp.mdx @@ -8,7 +8,7 @@ ISP (Internet Service Provider) proxies combine the speed of datacenter proxies ISP proxies provide a **stable exit IP within a single browser session** — every tab, request, and reconnection inside that session exits through the same IP, and it does not rotate mid-session (unlike residential). -Across separate sessions, Kernel does not guarantee the same exit IP from a managed ISP proxy. If a destination site requires the exact same IP across every session — for example, an IP allowlist, or a [managed auth](/auth/overview) connection whose health checks and reauths must look like the same client — use a [custom (BYO) proxy](/proxies/custom) pointed at infrastructure you control. +For cross-session IP stability (e.g. IP allowlists or [managed auth](/auth/overview) health checks), see [IP rotation behavior across proxy types](/proxies/overview). ## Configuration