Claude
Live official status, components, and recent incidents.
Check ClaudeAI Status Watch
A lightweight status hub for AI tools and model providers. The MVP tracks Claude live first, then expands to OpenAI, Gemini, DeepSeek, and other providers.
Current answerClaude is currently operational according to the official Claude status page.
Likely impactClaude is live; OpenAI, Gemini, and DeepSeek are planned
Next checkUse the Claude pages for live checks while provider expansion is validated.
Provider Coverage
Claude is live in this MVP. Other providers stay marked as planned until their data is wired cleanly.
OpenAI
Planned for the next batch after Claude pages are indexed.
PlannedGemini
Planned after core Claude status and error pages are validated.
PlannedDeepSeek
Candidate provider for later AI status comparison pages.
PlannedLive Claude Components
Component-level status helps separate a Claude.ai outage from API, Console, Claude Code, or account-specific issues.
| 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. |
Latest Claude Incidents
Recent official incidents can explain intermittent errors even after the current status has recovered.
Elevated errors on Claude Opus 4.7
claude.ai, Claude API (api.anthropic.com), Claude Code, Claude Cowork
Elevated errors for Claude Sonnet 4.6 and Haiku 4.5
claude.ai, Claude Console (platform.claude.com), Claude API (api.anthropic.com), Claude Code, Claude Cowork
Elevated Error Rate for Vaults and Credentials
Claude Console (platform.claude.com)
Claude Code on the Web Partial Outage
Claude Code
Elevated errors on Claude Opus 4.1
claude.ai, Claude Console (platform.claude.com), Claude API (api.anthropic.com), Claude Code
Elevated errors on Claude Opus 4.7
claude.ai, Claude API (api.anthropic.com), Claude Code, Claude Cowork
Elevated Errors on File Operations
claude.ai, Claude API (api.anthropic.com)
Elevated errors on Claude Sonnet 4.6
claude.ai, Claude Console (platform.claude.com), Claude API (api.anthropic.com), Claude Code, Claude Cowork
Elevated errors across Claude Models
claude.ai, Claude Console (platform.claude.com), Claude API (api.anthropic.com), Claude Code, Claude Cowork, Claude for Government
How to use this AI status hub
Use provider-specific pages for exact answers. A broad AI status page should route people to the right tool, not blur all providers into one vague dashboard.
- Use Claude Down when the Claude web app or desktop app fails.
- Use Anthropic Status for API, Console, and developer-facing issues.
- Use Claude Code Status for CLI, IDE, and coding agent workflows.
- Use error pages when you search a specific message such as unable to connect to Anthropic services.
- Treat planned providers as navigation placeholders until live data sources are connected.
FAQ
Does this page track all AI providers live?
Not yet. The MVP tracks Claude live first. Other providers are intentionally marked as planned to avoid a thin or misleading dashboard.
How should I check if an AI service is down?
Start with the provider-specific page, then compare official component status, recent incidents, your account or API logs, and whether other users report the same symptom.
Why start with Claude instead of every AI service?
Claude has validated search demand, official component data, frequent incidents, and clear long-tail pages such as Claude Code status and connection error checks.
Is this an official AI provider status page?
No. AI Status Watch is an independent tracker that links to official sources and adds troubleshooting context for searchers and developers.
Will OpenAI or Gemini be added?
Yes, after the Claude pages validate indexing and search impressions. Provider expansion should follow evidence, not page count.
Why are some providers marked planned?
Planned providers are kept visible as navigation targets, but they should not be presented as live until clean data sources and useful troubleshooting pages are ready.