Is Claude down right now?
Claude Status currently reports the selected Claude components as operational.
Uptime over the past 90 days, as published by the provider.
View official history ↗- Scope
- Claude API, Claude Code, Console, and claude.ai components
- Source updated
- Checked by Qodex
This page reads Claude’s official component status on the server. It can confirm a provider incident, but it cannot confirm that your prompt, API contract, tool call, or Claude Code workflow still succeeds.
Qodex does not operate Claude. Source: Claude Status.
Claude is operational. Is your workflow?
An official status page answers whether the provider sees a broad service problem. It does not execute the request, repository, or browser journey your product depends on.
Authentication
Replay the request with the same key, organization, and project headers your application sends.
Model access
Confirm the configured model exists, is enabled for the account, and has not changed its identifier.
Response contract
Validate status code, streaming events, JSON shape, tool calls, and timeout behavior against your integration.
User flow
Run the browser or API journey that consumes the model response, including retries and error states.
Official components and incidents
Scope matters. The rows below come from Claude Status and are filtered to Claude API and Claude Code. They are evidence from the provider, not synthetic Qodex probes.
No matching incident is active in the Claude source data returned for this render.
Troubleshoot Claude without guessing
Start with the provider state, then move inward through your account, request, application, and final user journey.
| Signal | What to verify |
|---|---|
| Authentication | Replay the request with the same key, organization, and project headers your application sends. |
| Model access | Confirm the configured model exists, is enabled for the account, and has not changed its identifier. |
| Response contract | Validate status code, streaming events, JSON shape, tool calls, and timeout behavior against your integration. |
| User flow | Run the browser or API journey that consumes the model response, including retries and error states. |
Claude status FAQ
Is Claude down right now?
The status above is rendered from Claude Status and scoped to Claude API, Claude Code, Console, and claude.ai components. If the official source is unavailable, Qodex reports the status as unavailable instead of guessing.
Why can Claude be operational while my integration is failing?
Provider dashboards report aggregate platform health. Your account, credentials, model access, region, request contract, SDK, repository, browser session, or downstream application flow can still fail independently.
Does Qodex monitor or operate Claude?
No. Claude is operated by its provider. Qodex renders the provider’s public status data here and helps engineering teams test the API and UI workflows that depend on it.
What should I test after the provider status is green?
Replay the real request and user journey with the same environment, credentials, payload, and assertions used in production. Check the response contract and the final user-visible result, not only connectivity.
Provider green is the start of diagnosis.
Qodex tests the API and UI path your team actually ships, then keeps the evidence with the failure.