Community pulse · 24 hours
1report100% were negative. Reports may describe errors, slowness, outages, or response quality.
Add your Claude report →Live Claude API status
Official status for api.anthropic.com, compared with fresh community reports from people using Claude.
Community pulse · 24 hours
1report100% were negative. Reports may describe errors, slowness, outages, or response quality.
Add your Claude report →Official incidents
No unresolved official incidents are listed.
Official status can lag brief, regional, or account-specific problems, so compare both signals.
Browse community status history →Fast diagnosis
Service status and request errors are different. Start with the HTTP code before assuming an outage.
| Code | Meaning | First response |
|---|---|---|
| 400 | Invalid request | Validate the request body, model name, and parameters. |
| 401 | Authentication error | Check that the API key is present and valid. |
| 403 | Permission error | Confirm the key and workspace can access the requested resource. |
| 429 | Rate limit | Back off, reduce concurrency, and inspect your account limits. |
| 500 | API error | Retry safely with exponential backoff and check live status. |
| 529 | Overloaded | Retry with exponential backoff and jitter; avoid synchronized bursts. |
Claude API status FAQ
The live card above comes from Anthropic's official Claude API component. Compare it with the community pulse: a burst of recent negative reports can reveal a developing or localized issue.
Anthropic is temporarily overloaded. Use exponential backoff with jitter and make retries idempotent where possible.
Malformed requests, invalid keys, missing permissions, and account rate limits do not require a service-wide incident. The error code table above separates those cases from likely server-side failures.
claudedumb.com is an independent community tracker and is not affiliated with Anthropic. Community reports are voluntary submissions, not unique users or verified incidents.