Claude Code
Operational
13:29:43 UTC
What are developers seeing?
Anonymous developer reports, aggregated over roughly 15 minutes. They are not official status.
No public incident
Official ↗Claude Code is operational.
Operational
13:29:43 UTC
What are developers seeing?
Anonymous developer reports, aggregated over roughly 15 minutes. They are not official status.
No public incident
Official ↗RELIABILITY
See how stable this tool has been in recent availability records.
Availability
100.00%
Outages
0
Outage time
0m
Availability
100.00%
Outages
0
Outage time
0m
Use your browser to test public entry points. No account details or content are sent.
This tests public reachability from your current network, not login, quota, or private APIs.
These tools currently show as operational. Confirm they fit your workflow before switching.
Get an alert after an official status change.
Get an alert after an official status change.
Paste this Markdown into a README or internal wiki.
[](https://devdown.dev/status/claude-code)Run this command to view current status.
curl -s https://devdown.dev/cliThis tool's status record
Only official snapshots saved by this site are counted. Uncollected periods stay blank.
Availability check
Resolved official incidents
Claude Code · Resolved · Official component match
Claude Code · Resolved · Official component match
Claude Code · Resolved · Official component match
Or is it your account/network?
Official status only answers whether the service is failing. These checks keep quota and local issues separate.
Read this card's component lights and official incident. If amber or red, follow the incident and wait for recovery.
If status is green but requests fail, check Usage, HTTP 429 rate limits, and HTTP 529 capacity.
HTTP 429 · HTTP 529Sign in again, then check system time, network, regional restrictions, organization policy, and IDE extension version.
View incident detailsRead the component lights: Claude Code, API, claude.ai, Cowork. Data from Anthropic official status.
No. 529 is capacity. The official page often stays green. Wait or switch models, then rule out quota.
The same JSON, aggregated every 60 seconds. A failed pull is unknown plus last success time.
DATA SOURCE
Status comes from official vendor pages and public-page availability observations, refreshed automatically.
Status records and official incidents are updated to help you understand service stability.
Source health · This refresh Request self-heal · 18:15:21 UTC