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: 2 additions & 2 deletions auth/configuration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -729,9 +729,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)** proxies provide a static exit IP that persists across sessions, so the initial login, health checks, and reauths all exit through the same IP. The IP only changes in rare ISP-initiated replacement events or a temporary [failover to a backup endpoint](/proxies/isp#backup-endpoint-failover).
- **[ISP](/proxies/isp)** proxies normally use the same primary IP for login, health checks, and reauthentication. A connection can use a different IP during [backup endpoint failover](/proxies/isp#backup-endpoint-failover).
- **[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 pick one if the static IP must be infrastructure you control (e.g. an allowlisted egress your security team owns).
- **[Custom (BYO)](/proxies/custom)** proxies route through your own proxy server. If the site enforces an IP allowlist, use a custom proxy with known egress IPs and allowlist each one.

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

Expand Down
10 changes: 5 additions & 5 deletions proxies/isp.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -6,13 +6,13 @@ ISP (Internet Service Provider) proxies are hosted on datacenter infrastructure

## IP rotation behavior

ISP proxies provide a **static exit IP that persists across sessions** — every tab, request, reconnection, and future browser session attached to this proxy exits through the same IP. The IP only changes in rare ISP-initiated replacement events.
ISP proxies normally use the same **primary exit IP across browser sessions**. A connection can use a different IP during [backup endpoint failover](#backup-endpoint-failover) without changing the primary.

This makes ISP proxies suitable for use cases that require a stable IP, such as IP allowlists or [managed auth](/auth/managed-auth) health checks. For comparison with other proxy types, see [IP rotation behavior across proxy types](/proxies/overview).
This makes ISP proxies suitable for use cases that benefit from a stable IP, such as [managed auth](/auth/managed-auth) health checks. For comparison with other proxy types, see [IP rotation behavior across proxy types](/proxies/overview).

### Backup endpoint failover

For some organizations, Kernel attaches a backup ISP endpoint from a different provider to each ISP proxy. If the primary endpoint refuses connections, traffic temporarily exits through the backup endpoint's IP and returns to the primary IP once it's reachable again. If you allowlist the proxy's IP, sites might see the backup IP during a primary outage.
Kernel tries to attach a backup from a second provider to shared US ISP proxies. For a proxy drawn from a reserved allocation, the allocation must include IPs from both providers in that country. If Kernel can't find a healthy backup at creation, the proxy starts with only its primary. Kernel can add the backup later when you attach the proxy to a browser. Until then, there's no failover.

## Configuration

Expand Down Expand Up @@ -103,7 +103,7 @@ func main() {

If your workload targets `.gov`, use a [residential proxy](/proxies/residential#gov-support) with no targeting, country-only targeting, or US state targeting. Kernel's default egress reaches `.gov` directly, so running without a proxy also works.

ISP proxies don't route `.gov` automatically today. Kernel attaches the provider that handles `.gov` to residential proxies only, so a `.gov` request from an ISP proxy falls back to the default provider, which carries some `.gov` destinations and returns a `502` on the rest.
Only residential proxies have special routing for `.gov`. ISP proxies use their usual endpoints, including a [backup](#backup-endpoint-failover) if one is available. If those endpoints can't reach the destination, you may see a `502`.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

ISP .gov copy drops required wording

Medium Severity

The ISP .gov support limitation no longer says there is no auto-route today, and it no longer states that ISP endpoints carry some .gov hosts while others return a 502. That contract is required so readers do not treat the gap as permanent or as a total block.

Fix in Cursor Fix in Web

Triggered by learned rule: Eligible residential proxies auto-route .gov; don't restore always-blocked gov

Reviewed by Cursor Bugbot for commit 8b18a63. Configure here.


## Bypass hosts

Expand Down Expand Up @@ -176,7 +176,7 @@ See the [overview](/proxies/overview#bypass-hosts) for full bypass host rules an

## Getting the static IP address

Because an ISP proxy has a static exit IP, you can read that IP once and reuse it — for example, to add it to an IP allowlist. The IP is returned as `ip_address` in the response when you [create a proxy](https://kernel.sh/docs/api-reference/proxies/create-a-proxy) and when you [get a proxy by ID](https://kernel.sh/docs/api-reference/proxies/get-proxy-by-id).
To log the configured primary IP, read `ip_address` when you [create a proxy](https://kernel.sh/docs/api-reference/proxies/create-a-proxy) or [get a proxy by ID](https://kernel.sh/docs/api-reference/proxies/get-proxy-by-id). This field still reports the primary during [failover](#backup-endpoint-failover). To verify which IP a specific request used, check the destination's access logs.

<CodeGroup>
```typescript Typescript/Javascript
Expand Down
6 changes: 4 additions & 2 deletions proxies/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ Kernel-provided proxies are unmetered and not billed, subject to the fair use ru
</Note>

<Info>
ISP proxies provide a **static exit IP that persists across sessions** — every browser session attached to the proxy exits through the same IP, and it only changes in rare ISP-initiated replacement events or a temporary [failover to a backup endpoint](/proxies/isp#backup-endpoint-failover). This makes them suitable for IP allowlists or [managed auth](/auth/managed-auth) health checks that must egress from a single IP.
ISP proxies normally reuse the same **primary exit IP** across browser sessions, which is useful for [managed auth](/auth/managed-auth) health checks. A connection can use a different IP during [backup endpoint failover](/proxies/isp#backup-endpoint-failover). If every request to a site must come from an allowlisted IP, use a [custom proxy](/proxies/custom) with known egress IPs instead.

Residential and mobile proxy exit IPs may change per connection — see [Residential routing and IP behavior](/proxies/residential#routing-and-ip-behavior) and [Mobile Proxies](/proxies/mobile) for details.
</Info>
Expand Down Expand Up @@ -244,7 +244,9 @@ client.Proxies.Check(ctx, proxy.ID, kernel.ProxyCheckParams{
</CodeGroup>

<Info>
For ISP proxies the exit IP is stable, so a successful check against a `url` reliably indicates that subsequent sessions will reach the same target from the same IP. For residential and mobile proxies the exit node changes between requests, so the check validates credentials and connectivity but not site-specific reachability. When `url` is provided, the result does not update the proxy's stored health status.
For ISP proxies, a successful check against `url` means the **primary endpoint** reached that URL at the time of the check. It doesn't test the [backup endpoint](/proxies/isp#backup-endpoint-failover) or tell you which IP a later browser connection will use. If the primary check fails, a browser may still reach the URL through a healthy backup.

For residential and mobile proxies, the exit IP can change between connections, so a successful check doesn't guarantee a later connection will reach the same site. When you provide `url`, the result doesn't update the proxy's stored health status.
</Info>

## Bypass hosts
Expand Down
Loading