Repository navigation
Document backup endpoint failover for US ISP proxies - #766
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ 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.
| 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`. |
There was a problem hiding this comment.
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.
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.
c023e6b to
86b693e
Compare
hiroTamada
left a comment
There was a problem hiding this comment.
lgtm — checked the backup eligibility, ip_address, and proxies.check claims against the api/egress code and they line up.


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.
ip_addressreturned by the API from the IP a destination sees. Recommend a custom proxy with known egress IPs for strict allowlists, including managed auth.proxies.checktests 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 validateandmint broken-linkspassed.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_addressalways reflects the primary—not the IP a destination saw..govrouting is clarified as residential-only.Proxies overview and auth connection configuration steer strict IP allowlists toward custom proxies, and note that
proxies.checkwithurlvalidates 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.