Skip to content

Document backup endpoint failover for US ISP proxies - #766

Merged
yummybomb merged 1 commit into
mainfrom
hypeship/isp-backup-ip-docs
Nov 20, 2026
Merged

yummybomb merged 1 commit into
mainfrom
hypeship/isp-backup-ip-docs

Conversation

@yummybomb

@yummybomb yummybomb commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Summary

A shared US ISP proxy can have a second exit IP, but creating the proxy doesn't guarantee a healthy backup. The ISP guide explains which proxies qualify and when Kernel can attach a backup after creation.

  • Distinguish the primary ip_address returned by the API from the IP a destination sees. Recommend a custom proxy with known egress IPs for strict allowlists, including managed auth.
  • Clarify that proxies.check tests only the primary endpoint, not the backup or the route a later browser connection will use.

The routing change is already deployed. This PR changes documentation only.

Validation

  • mint validate and mint broken-links passed.
  • Confirmed the updated ISP, proxy overview, and managed auth pages render in the local preview.

Note

Low Risk
Documentation-only updates to proxy and auth guides; no code or runtime behavior changes.

Overview
Updates proxy and managed-auth docs to match deployed US ISP backup endpoint failover behavior, replacing language that treated ISP exit IPs as strictly static.

ISP proxy guide now describes a primary exit IP that can shift during failover, when Kernel attaches a backup (shared US ISP vs reserved dual-provider allocations, possibly only after a browser attach), and that ip_address always reflects the primary—not the IP a destination saw. .gov routing is clarified as residential-only.

Proxies overview and auth connection configuration steer strict IP allowlists toward custom proxies, and note that proxies.check with url validates only the primary endpoint (a failing check doesn't rule out backup reachability).

Reviewed by Cursor Bugbot for commit 86b693e. Bugbot is set up for automated code reviews on this repo. Configure here.

@mintlify

mintlify Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated
Kernel 🟢 Ready View Preview Nov 20, 2026, 4:52 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.

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

Comment thread proxies/isp.mdx
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.

@hiroTamada hiroTamada left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

lgtm — checked the backup eligibility, ip_address, and proxies.check claims against the api/egress code and they line up.

@yummybomb
yummybomb merged commit 8201ffc into main Nov 20, 2026
3 checks passed
@yummybomb
yummybomb deleted the hypeship/isp-backup-ip-docs branch November 20, 2026 17:00

This branch was successfully deployed

1 active deployment
staging — 86b693e7 Deployed Nov 20, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants