Skip to content

Correct ISP and datacenter IP stability in managed auth proxy docs - #668

Draft
courtney918 wants to merge 1 commit into
mainfrom
hypeship/fix-auth-proxy-ip-stability
Draft

courtney918 wants to merge 1 commit into
mainfrom
hypeship/fix-auth-proxy-ip-stability

Conversation

@courtney918

Copy link
Copy Markdown
Contributor

Summary

The Custom Proxy section of auth/configuration.mdx said ISP and datacenter proxies give a stable exit IP within a single session but no guarantee across sessions. That contradicts the proxy docs and the implementation:

  • ISP: each ISP proxy is pinned to one endpoint when created, so its exit IP persists across sessions (proxies/isp.mdx). The login, health checks and reauths all use the same IP.
  • Datacenter: exit IPs rotate per request, even within a session (proxies/datacenter.mdx).

Changes:

  • Split the combined ISP/datacenter bullet into two accurate bullets. The ISP bullet notes that each ISP proxy has its own IP, so users should reuse one proxy.
  • Reword the custom proxy bullet so it no longer implies custom is the only static-IP option. It's now positioned as the choice when you need to control the egress IP yourself.

Docs-only change; not previewed locally.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

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

Project Status Preview Updated
Kernel 🟢 Ready View Preview Oct 5, 2026, 6:23 PM

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

This branch was successfully deployed

1 active deployment
staging — cba831df Deployed Oct 5, 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.

1 participant