Is the Anthropic API reachable right now?
A live probe of api.anthropic.com from NetOkay’s edge, a test from your own browser, and how to tell a Claude API incident from an idle timeout on your own path.
In short: The card below shows the latest probe of api.anthropic.com from
eight Cloudflare regions: one GET for /v1/models with a placeholder
x-api-key. Anthropic answers in its own JSON: 401
authentication_error from most Cloudflare locations, or a 403 within
milliseconds from locations in regions Anthropic does not serve. Either is Anthropic
answering, not an outage. Then test from this browser: if NetOkay reaches the host and
your stream still dies, check your network’s idle handling.
Last updated
Live probe · api.anthropic.com
Where is api.anthropic.com reachable from?
Loading the latest observation of api.anthropic.com… Test from this browser →
From this browser
—Not run. One request from your browser, sent only when you ask.
What this proves, and what it does not
Loading…
Anthropic specifics
- API host
-
api.anthropic.com, HTTPS on port 443. Messages live at/v1/messages(POST only);/v1/modelsis the read-only list this probe asks for. - Streaming
-
Messages stream as server-sent events with named event types:
message_start,content_block_start,content_block_delta,content_block_stop,message_delta,message_stop. Anthropic also sends periodicpingevents, so a healthy stream is rarely silent for long. - Thinking pauses
-
With extended thinking enabled,
thinking_deltaevents can arrive slowly and the final text block can come after a long gap. A client that only counts text deltas as progress may treat that gap as a hang. - Official status
- status.anthropic.com (it redirects to status.claude.com) lists API and console incidents.
- Support ticket header
-
Quote the
request-idresponse header; error bodies repeat it asrequest_id. The Python and TypeScript SDKs expose it as_request_id. - Client defaults
-
The Python SDK waits up to 10 minutes per request with a 5-second connect timeout and
retries twice; the TypeScript SDK also uses 10 minutes, stretched up to 60 for large
non-streaming
max_tokens. A 30-second idle cut on your path happens long before either.
What Anthropic status codes mean
| Code | Sent by | Meaning |
|---|---|---|
| 403 | API application |
Policy refusal in Anthropic’s own JSON (permission_error): a region
Anthropic does not serve, or a key without permission. Answered within milliseconds
at the front door, so it proves reachability, not that your request would succeed.
|
| 401 | API application |
authentication_error: the key is missing or invalid. The API
application produced this answer.
|
| 429 | API application | Rate limit on requests or tokens; the body names the limit. |
| 529 | API application |
Overloaded, which is Anthropic‑specific: retry with backoff. Streamed requests can
also deliver an error event mid‑stream.
|
| Every row is an HTTP answer: the host was reached and the request was refused or served. None of them means api.anthropic.com is unreachable. | ||
Reachable here but failing for you?
-
Run the 30‑second idle stream from the network where your app fails. Anthropic’s
pingevents usually keep a stream alive, so a stream that still dies points at a proxy that buffers or drops them. Run the idle stream → -
Read the idle result. Closed during the silence points at an idle limit under 30 seconds
on your path; start and done arriving together points at buffering that also delays
ping. Fixes in the streaming guide → - Compare environments if this browser passes but a container, server or agent fails, then run the CLI from the failing environment against api.anthropic.com. Compare environments →
Anthropic API status FAQ
Is a 401 from the probe a problem?
No. The probe sends a placeholder x-api-key that belongs to no account, so
Anthropic answering 401 authentication_error is the expected result: the API
itself refused the token. A 403 in Anthropic’s own JSON within milliseconds is a policy
refusal, usually because the Cloudflare location that served you sits in a region
Anthropic does not serve; a generic “Edge refused” block proves only DNS, TLS and the
front door.
Claude streams fine for short answers but breaks on long ones. Why?
Long answers and extended thinking make the stream last longer, so any idle or total‑duration limit on your path becomes visible. Run the homepage idle stream check; a failure there points at your proxy or gateway, not at Anthropic.
What does 529 mean?
Anthropic returns 529 when the API is temporarily overloaded. It is an HTTP response, so connectivity is fine; back off and retry rather than debugging your network.