All Systems Operational

claude.ai Operational
90 days ago
99.38 % uptime
Today
platform.claude.com (formerly console.anthropic.com) Operational
90 days ago
99.57 % uptime
Today
Claude API (api.anthropic.com) Operational
90 days ago
99.4 % uptime
Today
Claude Code Operational
90 days ago
99.65 % uptime
Today
Claude for Government Operational
90 days ago
99.86 % 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.
Mar 16, 2026
Resolved - This incident has been resolved.
Mar 16, 12:36 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 16, 12:27 UTC
Investigating - We are currently investigating this issue.
Mar 16, 12:01 UTC
Mar 15, 2026

No incidents reported.

Mar 14, 2026

No incidents reported.

Mar 13, 2026
Resolved - This incident has been resolved.
Mar 13, 21:27 UTC
Investigating - We are currently investigating this issue.
Mar 13, 18:37 UTC
Mar 12, 2026
Resolved - This incident has been resolved.
Mar 12, 18:00 UTC
Identified - A repeat of an earlier issue today started at 9:27 PT / 16:27 UTC.
Mar 12, 16:34 UTC
Resolved - This incident has been resolved.
Mar 12, 16:28 UTC
Monitoring - We recently had an incident on Sonnet 4.6 between 8:30 PT / 15:30 UTC and 8:44 PT / 15:44 UTC where users would have seen a higher error rate across Claude Code, Claude API, and Claude.ai.

Separately, we also had at around 8:27 PT an incident relate to Claude.ai that lasted a minute.

Mar 12, 16:07 UTC
Resolved - This incident has been resolved.
Mar 12, 15:48 UTC
Investigating - We are currently investigating this issue.
Mar 12, 15:42 UTC
Mar 11, 2026
Postmortem - Read details
Mar 11, 17:56 UTC
Resolved - The incident is now resolved. To recap we had an incident starting at 07:17 PT / 14:17 UTC and the errors returned to baseline at 10:11 PT / 17:11 UTC.
Mar 11, 17:28 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 11, 17:22 UTC
Update - We are continuing to work on a fix for this issue.
Mar 11, 17:22 UTC
Identified - The issue has been identified and a fix is being implemented.
Mar 11, 17:19 UTC
Update - We're currently investigating issues with Claude Code and Claude.ai. Some users may be unable to log in, and others may experience slower than usual performance. The Claude API is not affected.
Mar 11, 15:44 UTC
Update - We are continuing to investigate this issue.
Mar 11, 15:27 UTC
Update - This is affecting the login/logout actions in Claude Code as well.
Mar 11, 14:47 UTC
Investigating - We are currently investigating this issue.
Mar 11, 14:44 UTC
Mar 10, 2026
Resolved - This incident has been resolved.
Mar 10, 16:52 UTC
Monitoring - Root cause: Users with scheduled tasks in Claude Cowork or Claude Code who are in a timezone that observed daylight saving time last night were affected by an infinite loop. When the app tried to locate tasks scheduled during the “skipped” hour, it couldn’t resolve them and got stuck.

Fix: Update to version 1.1.5749 via https://claude.com/download. If you’re unable to update right away, temporarily switching to a timezone that doesn’t observe daylight saving time will also resolve the issue.

We’re working on a backend fix as well. We know disruptions to Claude affect your work, and we apologize for the trouble.

Mar 8, 19:42 UTC
Update - Root cause: Users with scheduled tasks in Claude Cowork or Claude Code who are in a timezone that observed daylight saving time last night were affected by an infinite loop. When the app tried to locate tasks scheduled during the “skipped” hour, it couldn’t resolve them and got stuck.
Mar 8, 19:42 UTC
Identified - The issue has been identified and a fix is being implemented.
Mar 8, 18:27 UTC
Investigating - We have identified the issue and are working on a mitigation. Currently, scheduled tasks are disabled for cowork and claude code desktop.
Mar 8, 17:57 UTC
Mar 9, 2026

No incidents reported.

Mar 8, 2026
Resolved - Filesystem extension has been restored to allowlists
Mar 8, 15:49 UTC
Identified - The issue has been identified and a fix has been implemented. Users may need to re-add the Filesystem connector to their organization allowlist in order to reactivate it.
Mar 6, 17:16 UTC
Mar 7, 2026
Resolved - Today between 5:35 PT / 13:35 UTC and 6:44 PT / 14:44 UTC Haiku 4.5 had an elevated error rate. We are now at the baseline error rate.
Mar 7, 16:58 UTC
Investigating - We are currently investigating this issue.
Mar 7, 13:58 UTC
Mar 6, 2026
Resolved - This incident has been resolved.
Mar 6, 16:23 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 6, 16:01 UTC
Investigating - Some API requests to api.anthropic.com are experiencing connection timeouts due to network degradation at an upstream peering point. Requests that successfully connect are unaffected. We are working with our upstream providers to resolve the issue.
Mar 6, 15:34 UTC
Mar 5, 2026

No incidents reported.

Mar 4, 2026
Resolved - Errors have returned to the baseline as of 8:08 PT / 16:08 UTC.
Mar 4, 17:01 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 4, 16:13 UTC
Investigating - The earlier issues with Haiku 4.5 have reappeared.
Mar 4, 15:58 UTC
Resolved - This incident has been resolved.
Mar 4, 15:57 UTC
Investigating - We are currently investigating this issue.
Mar 4, 14:14 UTC
Resolved - The incident for Haiku 4.5 has been between 6:45 PT / 14:45 UTC and 6:50 PT / 14:50 UTC.
Mar 4, 14:55 UTC
Investigating - We are currently investigating this issue.
Mar 4, 14:47 UTC
Resolved - This incident has been resolved.
Mar 4, 08:32 UTC
Monitoring - We have applied a fix for usage reporting and are monitoring the recovery
Mar 4, 01:29 UTC
Update - A fix has been applied and the admin API is operational.

We are continuing to investigate issues with usage reporting via Console and admin API

Mar 4, 00:58 UTC
Identified - The team has identified the issues affecting admin API and cost reporting and are working on a fix
Mar 4, 00:08 UTC
Update - The team is investigating ongoing impact to admin API and usage reporting in the console
Mar 3, 18:03 UTC
Update - The team has applied a fix for the admin API. Console and admin API endpoints

The team is still investigating an ongoing issue with usage reporting in the console and admin API

Mar 3, 17:29 UTC
Investigating - The team is currently investigating an issue affecting the admin API and some reporting screens in the Console
Mar 3, 16:49 UTC
Mar 3, 2026
Resolved - This incident has been resolved.
Mar 3, 16:38 UTC
Investigating - We are currently investigating this issue.
Mar 3, 15:40 UTC
Resolved - This incident has been resolved.
Mar 3, 15:39 UTC
Investigating - We are currently investigating this issue.
Mar 3, 14:51 UTC
Resolved - This incident has been resolved.
Mar 3, 14:29 UTC
Update - We are continuing to monitor for any further issues.
Mar 3, 14:29 UTC
Update - A fix has been implemented and we are monitoring the results.
Mar 3, 14:11 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 3, 14:03 UTC
Update - We are continuing to work on a fix for this issue.
Mar 3, 12:59 UTC
Identified - The issue is reoccurring, a fix is being implemented.
Mar 3, 12:00 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 3, 10:27 UTC
Identified - The issue has been identified and a fix is being implemented.
Mar 3, 08:31 UTC
Investigating - We are currently investigating this issue.
Mar 3, 06:59 UTC
Resolved - This incident has been resolved.
Mar 3, 10:18 UTC
Update - We are continuing to monitor for any further issues.
Mar 3, 09:36 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 3, 08:39 UTC
Update - We are continuing to investigate this issue.
Mar 3, 04:43 UTC
Update - We are continuing to investigate this issue.
Mar 3, 04:41 UTC
Update - We are continuing to investigate this issue.
Mar 3, 04:39 UTC
Investigating - We are currently investigating this issue.
Mar 3, 03:15 UTC
Mar 2, 2026
Resolved - This incident has been resolved.
Mar 2, 21:16 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 2, 18:54 UTC
Investigating - We are seeing a repeat of this issue, we are currently investigating.
Mar 2, 18:18 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 2, 18:07 UTC
Investigating - We are currently investigating this issue.
Mar 2, 17:56 UTC
Resolved - This incident has been resolved.
Mar 2, 17:55 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 2, 17:24 UTC
Identified - The issue has been identified and a fix is being implemented.
Mar 2, 17:15 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 2, 17:09 UTC
Investigating - We are currently investigating this issue.
Mar 2, 16:50 UTC
Resolved - This incident has been resolved.
Mar 2, 17:23 UTC
Investigating - We are currently investigating this issue.
Mar 2, 17:08 UTC
Resolved - This incident has been resolved.
Mar 2, 15:50 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 2, 15:49 UTC
Identified - The issue has been identified and a fix is being implemented.
Mar 2, 14:42 UTC
Update - We are continuing to investigate this issue.
Mar 2, 14:35 UTC
Investigating - We are currently investigating this issue.
Mar 2, 14:35 UTC
Resolved - This incident has been resolved.
Mar 2, 15:47 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Mar 2, 15:25 UTC
Update - We are continuing to work on a fix for this issue.
Mar 2, 14:05 UTC
Update - We have discovered that some API methods are not working and we are investigating.
Mar 2, 13:37 UTC
Identified - The issue has been identified and a fix is being implemented.
Mar 2, 13:22 UTC
Update - We have identified that the Claude API is working as intended. The issues we are seeing are related to Claude.ai and with the login/logout paths.
Mar 2, 12:21 UTC
Update - We are continuing to investigate this issue.
Mar 2, 12:06 UTC
Investigating - We are currently investigating this issue.
Mar 2, 11:49 UTC