Skip to content
Merged
Show file tree
Hide file tree
Changes from 2 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: 2 additions & 2 deletions auth/configuration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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).
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deep IP-stability content duplicated across auth and proxy pages

Low Severity

The per-session-vs-cross-session IP stability explanation is now reproduced in depth in both auth/configuration.mdx and proxies/overview.mdx (and echoed in the ISP/datacenter pages). This same PR correctly applies the brief-summary-plus-link pattern in proxies/isp.mdx and proxies/datacenter.mdx, but auth/configuration.mdx instead expands the material inline (step-up challenges, health checks, reauth) without linking to the canonical proxy overview. The auth-specific implications are valuable, but the core factual content about session-scoped IP stability is duplicated rather than briefly summarized with a link-out.

Additional Locations (1)
Fix in Cursor Fix in Web

Triggered by learned rule: Single source of truth — no deep content duplication across pages

Reviewed by Cursor Bugbot for commit b4abc50. Configure here.


Create a proxy first, then attach it to the connection:

Expand Down
4 changes: 3 additions & 1 deletion proxies/datacenter.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Comment thread
cursor[bot] marked this conversation as resolved.
Outdated

## Configuration

Expand Down
4 changes: 3 additions & 1 deletion proxies/isp.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
4 changes: 3 additions & 1 deletion proxies/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -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.

<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.
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.
Comment thread
cursor[bot] marked this conversation as resolved.
</Info>

## Create a proxy
Expand Down
Loading