The Wayback Machine - https://web.archive.org/web/20260201131553/https://status.claude.com/

All Systems Operational

claude.ai Operational
90 days ago
99.43 % uptime
Today
platform.claude.com (formerly console.anthropic.com) Operational
90 days ago
99.85 % uptime
Today
Claude API (api.anthropic.com) Operational
90 days ago
99.68 % uptime
Today
Claude Code Operational
90 days ago
99.66 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Feb 1, 2026
Resolved - As of 2026-02-01 03:55 PT / 11:55 UTC the errors are back to the baseline.
Feb 1, 12:34 UTC
Update - Start of errors 2026-02-01 03:36 PT / 11:36 UTC.
Feb 1, 11:48 UTC
Investigating - We are currently investigating this issue.
Feb 1, 11:47 UTC
Resolved - The errors have returned to baseline as of 2026-02-01 02:51 / 10:51 UTC.
Feb 1, 11:42 UTC
Update - We are continuing to investigate this issue.
Feb 1, 10:54 UTC
Investigating - We are investigating an issue with Opus 4.5 that started at 2026-02-01 02:41 PT / 10:41 UTC.
Feb 1, 10:54 UTC
Jan 31, 2026
Resolved - This incident has been resolved. Update Claude Code to 2.1.29.
Jan 31, 21:06 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 31, 20:41 UTC
Identified - We have identified the problem and are working on a fix. More details can be found in Github issue #22042.
Jan 31, 20:18 UTC
Jan 30, 2026

No incidents reported.

Jan 29, 2026
Resolved - During the outage, all of the following were delayed:
- customer balances
- billing for standard API usage
- issuing credit auto-recharge invoices
- access shutoff/restore for $0 in credits, and for reaching spend limits

The outage has now been resolved. There is no longer a system delay for any of the above.

Jan 29, 20:39 UTC
Identified - Some customers are experiencing delays in having their successful credit purchases applied and in triggering credit auto-reloads. We have identified the issue and are working to resolve.
Jan 29, 19:51 UTC
Investigating - We are currently investigating this issue.
Jan 29, 19:10 UTC
Jan 28, 2026
Resolved - As of 06:12 PT / 14:12 UTC, we have mitigated the issue.
Jan 28, 14:14 UTC
Update - This is a repeat of the incident earlier in the day. Errors have restarted from 05:41 PT / 13:41 UTC.
Jan 28, 13:52 UTC
Investigating - We are currently investigating this issue.
Jan 28, 13:52 UTC
Resolved - As of 03:50 PT / 11:50 UTC we have fully recovered.
Jan 28, 12:30 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 28, 11:47 UTC
Investigating - We are currently investigating this issue.
Jan 28, 11:30 UTC
Resolved - This incident has been resolved.
Jan 28, 10:36 UTC
Investigating - We are currently investigating this issue.
Jan 28, 10:13 UTC
Jan 27, 2026
Resolved - This incident is resolved.
Jan 27, 23:07 UTC
Monitoring - A fix has been applied. Request latencies are returning to normal. We will continue to monitor system health
Jan 27, 22:55 UTC
Investigating - We are currently investigating degraded performance on platform.claude.com.
Jan 27, 22:28 UTC
Resolved - This incident has been resolved.
Jan 27, 14:56 UTC
Investigating - We are currently investigating this issue.
Jan 27, 14:23 UTC
Jan 26, 2026
Resolved - This incident has been resolved.
Jan 26, 14:32 UTC
Update - We are continuing to monitor for any further issues.
Jan 26, 04:53 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 25, 09:57 UTC
Investigating - We are currently investigating this issue.
Jan 25, 08:05 UTC
Jan 25, 2026
Jan 24, 2026

No incidents reported.

Jan 23, 2026
Resolved - This issue is resolved for new requests. However, for responses from one platform received between 2026-01-23 00:00 UTC - 2026-01-23 08:00 UTC that are subsequently included in requests sent to a different platform, there may still be errors.
Jan 23, 07:47 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 23, 07:32 UTC
Update - We are continuing to work on a fix for this issue.
Jan 23, 06:24 UTC
Update - A mitigation is to _not_ mix Claude API traffic between Bedrock, Vertex, and api.anthropic.com. Each platform is fully operational independently.
Jan 23, 05:22 UTC
Update - We are continuing to work on a fix for this issue.
Jan 23, 05:12 UTC
Update - We are continuing to work on a fix for this issue.
Jan 23, 05:10 UTC
Identified - The issue has been identified and fix is being implemented.
Jan 23, 05:09 UTC
Jan 22, 2026
Resolved - This incident has been resolved.
Jan 22, 22:26 UTC
Update - We are continuing to monitor for any further issues.
Jan 22, 22:23 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 22, 22:22 UTC
Investigating - We are currently investigating this issue.
Jan 22, 22:19 UTC
Resolved - This incident has been resolved.
Jan 22, 16:49 UTC
Update - We are continuing to monitor for any further issues.
Jan 22, 16:49 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 22, 16:36 UTC
Identified - The issue has been identified and a fix is being implemented.
Jan 22, 16:29 UTC
Investigating - We are currently investigating an issue affecting Claude Code authentication. Users may encounter errors when attempting to sign in or authenticate their Claude Code sessions.
Jan 22, 16:22 UTC
Resolved - This incident has been resolved.
Jan 22, 16:49 UTC
Update - We are continuing to investigate this issue.
Jan 22, 16:10 UTC
Investigating - We are currently investigating this issue.
Jan 22, 16:06 UTC
Jan 21, 2026
Postmortem - Read details
Jan 21, 15:58 UTC
Resolved - This incident has been resolved.
Jan 21, 15:32 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 21, 15:28 UTC
Identified - The issue has been identified and a fix is being implemented.
Jan 21, 15:01 UTC
Investigating - We are currently investigating this issue.
Jan 21, 14:44 UTC
Jan 20, 2026
Postmortem - Read details
Jan 20, 18:00 UTC
Resolved - This incident has been resolved.
Jan 20, 17:34 UTC
Identified - The issue has been identified and a fix is being implemented.
Jan 20, 17:20 UTC
Investigating - We are currently investigating this issue.
Jan 20, 16:41 UTC
Jan 19, 2026

No incidents reported.

Jan 18, 2026

No incidents reported.