{"version":"2.1.275","anchor":"new-credentialauth-error-reason-ip-restricted","canonical_anchor":"new-ip-allowlist-reason-surfaces-in-model-catalog-fetch-fail","heading":"New ip_restricted error reason for IP-allowlist rejections","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/new-credentialauth-error-reason-ip-restricted","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### New ip_restricted error reason for IP-allowlist rejections\n\nRequests blocked by an org's IP allowlist now surface a distinct ip_restricted error instead of a generic failure\n\n**What**\n\nA new error reason, `ip_restricted`, was added alongside the existing `not_permitted` and `lane_unavailable` reasons in the map from internal error reasons to a public credential-scope error code. It now also appears specifically when a model catalog fetch fails because an organization's IP allowlist rejected the request (HTTP 403 with code `ip_not_in_allowed_range`), with its own log message and telemetry `off_reason`, distinguishing it from the prior two failure reasons.\n\n**Why**\n\nThis lets users and logs distinguish being blocked by an organization's IP allowlist from other credential or availability failures, making it clearer what needs to be fixed.\n\n- Area: Auth\n- Names: `ip_restricted`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}