{"version":"2.1.318","anchor":"hosted-egress-proxy-startup-probe-reason-removed","canonical_anchor":"hosted-egress-proxy-startup-probe-reason-removed","heading":"The hosted proxy no longer reports being unreachable at startup as a failure reason","tier":"internal","area":"Internals","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/hosted-egress-proxy-startup-probe-reason-removed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### The hosted proxy no longer reports being unreachable at startup as a failure reason\n\nClaude Code dropped the failure reason it gave when the hosted egress proxy could not be reached at startup\n\n**What**\n\nIn hosted environments, Claude Code can send its outgoing network traffic through an egress proxy, which is a relay that all outbound connections pass through. Claude Code keeps a list of reasons it can give when that proxy fails. One of them said the hosted egress proxy was unreachable at startup, and that reason has been removed from the list.\n\nOther reasons, such as a control character found in the host name of a connection request, are still on the list.\n\n**Why**\n\nThe check at startup that produced this reason was dropped, so a proxy failure will no longer be blamed on the proxy being unreachable at startup.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}