Claude Status
Current Claude.ai, API, Console, Claude Code, and component health.
Check whether Claude is down, slow, returning API errors, or failing in Claude Code. Compare live Claude status, 529 overloaded errors, timeouts, and recent Anthropic incidents from one independent hub.
Pick the right check
Most searches for Claude status are really asking one of four questions. Use the closest match first instead of treating every symptom as a full outage.
Current Claude.ai, API, Console, Claude Code, and component health.
Slow replies, Claude Code lag, usage limits, long context, or green status but poor performance.
429 rate limits, 529 overloaded, timeouts, 500/503 errors, and request-log triage.
CLI lag, MCP tools, long context, terminal issues, and coding-agent slowdowns.
Common symptoms
These pages answer the problems official status pages usually cannot: green status but slow behavior, API overload errors, and Claude Code workflows that feel worse than usual.
Official Claude status is operational, but Claude.ai, API, or Claude Code still feels degraded.
Claude API requests time out, stream stalls, or Claude Code hangs during long runs.
Claude Code is super slow, too slow, stuck in tools, or carrying too much context.
Claude Code or Anthropic API returns 529 overloaded, retry loops, or temporary server-side overload.
Fable 5, Mythos 5, model picker, or model access errors affect one Claude model or account path.
Full outage checks when Claude.ai, Claude API, or Claude Code is unavailable.
Use component-level status to tell whether the issue affects Claude.ai, Claude API, Claude Code, Console, or a narrower Anthropic service.
| Component | Status | What it affects |
|---|---|---|
| claude.ai | operational | Web app, chat UI, and login experience. |
| Claude Console (platform.claude.com) | operational | Developer console and platform settings. |
| Claude API (api.anthropic.com) | operational | API requests to api.anthropic.com. |
| Claude Code | operational | Coding agent, CLI, and IDE-related workflows. |
| Claude Cowork | operational | Team collaboration features. |
| Claude for Government | operational | Government environment. |
Recent official incidents can explain slow replies, API errors, connection problems, or Claude Code interruptions after the current status has recovered.
No component listed
claude.ai, Claude Console (platform.claude.com), Claude API (api.anthropic.com), Claude Code, Claude Cowork
claude.ai, Claude Console (platform.claude.com), Claude API (api.anthropic.com), Claude Code, Claude Cowork
claude.ai, Claude Console (platform.claude.com), Claude API (api.anthropic.com), Claude Code, Claude Cowork
claude.ai, Claude API (api.anthropic.com), Claude Code, Claude Cowork
claude.ai, Claude API (api.anthropic.com), Claude Code, Claude Cowork
claude.ai, Claude API (api.anthropic.com), Claude Code, Claude Cowork
claude.ai, Claude Console (platform.claude.com), Claude API (api.anthropic.com), Claude Code, Claude Cowork
claude.ai, Claude Console (platform.claude.com), Claude API (api.anthropic.com), Claude Code, Claude Cowork
Start broad, then move to the page that matches the exact symptom.
Start with Claude Status for the current official component state. Then use Claude Slow for latency, Claude API Status for 429, 529, timeout, and 5xx errors, or Claude Code Status for CLI and IDE workflows.
No. AI Status Watch is independent. It summarizes official Claude status data and adds troubleshooting context, but the official source remains status.claude.com.
A green status page can still leave model-specific latency, account limits, long prompts, Claude Code context, local network issues, or API overload symptoms. Use the slow and API pages to narrow the cause.
Use Claude API Status for 429 rate limits, 529 overloaded responses, timeouts, 500/503 errors, model-specific failures, request logs, and recent Claude API incidents.
Check Claude Code Status first, then compare Claude API Status, recent incidents, 529 overloaded errors, login state, IDE extension state, and local network access.