Key error diagnosis

Anthropic | IP restricted

Anthropic returning 403 / IP restricted should not be judged from the message alone. Cross-check key shape, Base URL, balance, model permission, region/IP, and visible model list.

Provider

Anthropic

global provider route

Error type

IP restricted

medium

Status code

403

ip-restricted

Sample models

Claude 3.5 Haiku · Claude 3.7 Sonnet · Claude 3.7 Sonnet (thinking)

Error route summary

Error type

ip-restricted

medium

Provider

Anthropic

Status code

403

Read-only check. Detection data burns after 5 minutes.

What this error usually means

Anthropic returning 403 / IP restricted should not be judged from the message alone. Cross-check key shape, Base URL, balance, model permission, region/IP, and visible model list.

Provider: Anthropic
Error type: IP restricted
Status code: 403

How to prove it during checking

Read-only check. Detection data burns after 5 minutes.

Run read-only identity first: confirm whether the key really belongs to Anthropic, not just a compatible protocol.
Then list models or run a lightweight probe: check whether models like Claude 3.5 Haiku · Claude 3.7 Sonnet · Claude 3.7 Sonnet (thinking) are visible and return stable evidence.
Finally record 403, error body, latency, egress IP, and reproducibility to separate balance, permission, route, or upstream issues.

Next action

IP restricted should not only show failed. The console should return the next move: refill balance, change Base URL, switch model, add permission, change egress IP, hold listing, or monitor.

Read-only check. Detection data burns after 5 minutes.
global provider route
Claude 3.5 Haiku · Claude 3.7 Sonnet · Claude 3.7 Sonnet (thinking)

Open key checker

Read-only check. Detection data burns after 5 minutes.

Open providers

Anthropic

Open models

Claude 3.5 Haiku · Claude 3.7 Sonnet · Claude 3.7 Sonnet (thinking)