Anthropic Claude

Mar 7, 16:58 UTC
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, 13:58 UTC
Investigating - We are currently investigating this issue.

Mar 6, 17:16 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, 16:23 UTC
Resolved - This incident has been resolved.

Mar 6, 16:01 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Mar 6, 15:34 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 4, 17:01 UTC
Resolved - Errors have returned to the baseline as of 8:08 PT / 16:08 UTC.

Mar 4, 16:13 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Mar 4, 15:58 UTC
Investigating - The earlier issues with Haiku 4.5 have reappeared.

Mar 4, 15:57 UTC
Resolved - This incident has been resolved.

Mar 4, 14:14 UTC
Investigating - We are currently investigating this issue.

Mar 4, 14:55 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:47 UTC
Investigating - We are currently investigating this issue.

Mar 4, 08:32 UTC
Resolved - This incident has been resolved.

Mar 4, 01:29 UTC
Monitoring - We have applied a fix for usage reporting and are monitoring the recovery

Mar 4, 00:58 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:08 UTC
Identified - The team has identified the issues affecting admin API and cost reporting and are working on a fix

Mar 3, 18:03 UTC
Update - The team is investigating ongoing impact to admin API and usage reporting in the console

Mar 3, 17:29 UTC
Update - …

Mar 3, 16:38 UTC
Resolved - This incident has been resolved.

Mar 3, 15:40 UTC
Investigating - We are currently investigating this issue.

Mar 3, 15:39 UTC
Resolved - This incident has been resolved.

Mar 3, 14:51 UTC
Investigating - We are currently investigating this issue.

Mar 3, 14:29 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:11 UTC
Update - A fix has been implemented and we are monitoring the results.

Mar 3, 14:03 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Mar 3, 12:59 UTC
Update - We are continuing to work on a fix for this issue.

Mar 3, 12:00 UTC
Identified - The issue is reoccurring, a fix is being implemented.

Mar 3, 10:27 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Mar 3, 08:31 UTC
Identified - …

Mar 3, 10:18 UTC
Resolved - This incident has been resolved.

Mar 3, 09:36 UTC
Update - We are continuing to monitor for any further issues.

Mar 3, 08:39 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

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
Update - We are continuing to investigate this issue.

Mar 3, 03:15 UTC
Investigating - We are currently investigating this issue.

Mar 2, 21:16 UTC
Resolved - This incident has been resolved.

Mar 2, 18:54 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Mar 2, 18:18 UTC
Investigating - We are seeing a repeat of this issue, we are currently investigating.

Mar 2, 18:07 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Mar 2, 17:56 UTC
Investigating - We are currently investigating this issue.

Mar 2, 17:55 UTC
Resolved - This incident has been resolved.

Mar 2, 17:24 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Mar 2, 17:15 UTC
Identified - The issue has been identified and a fix is being implemented.

Mar 2, 17:09 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Mar 2, 16:50 UTC
Investigating - We are currently investigating this issue.

Mar 2, 17:23 UTC
Resolved - This incident has been resolved.

Mar 2, 17:08 UTC
Investigating - We are currently investigating this issue.

Mar 2, 15:50 UTC
Resolved - This incident has been resolved.

Mar 2, 15:49 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Mar 2, 14:42 UTC
Identified - The issue has been identified and a fix is being implemented.

Mar 2, 14:35 UTC
Update - We are continuing to investigate this issue.

Mar 2, 14:35 UTC
Investigating - We are currently investigating this issue.

Mar 2, 15:47 UTC
Resolved - This incident has been resolved.

Mar 2, 15:25 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Mar 2, 14:05 UTC
Update - We are continuing to work on a fix for this issue.

Mar 2, 13:37 UTC
Update - We have discovered that some API methods are not working and we are investigating.

Mar 2, 13:22 UTC
Identified - The issue has been identified and a fix is being implemented.

Mar 2, 12:21 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 …

Feb 28, 18:34 UTC
Resolved - Between 9:50 PT / 17:50 UTC and 10:12 PT / 18:12 UTC we had a high rate of errors on Claude Opus 4.6. This has now ended

Feb 28, 18:09 UTC
Investigating - We are currently investigating this issue.

Feb 28, 15:50 UTC
Resolved - This incident has been resolved.

Feb 28, 13:07 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 28, 12:57 UTC
Investigating - We are currently investigating this issue.

Feb 27, 19:43 UTC
Resolved - This incident has been resolved.

Feb 27, 19:32 UTC
Investigating - We are currently investigating this issue.

Feb 27, 17:21 UTC
Resolved - This incident has been resolved.

Feb 27, 17:21 UTC
Update - We are continuing to monitor for any further issues.

Feb 27, 14:00 UTC
Monitoring - Some new logins to the Claude Desktop app were not working.

Feb 27, 17:17 UTC
Resolved - This incident has been resolved.

Feb 27, 13:41 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 27, 13:14 UTC
Investigating - We are currently investigating this issue.

Feb 27, 14:23 UTC
Resolved - This incident has been resolved. Impact: Feb 26 ~02:00 to Feb 27 06:20 UTC. Usage report API endpoints and analytics dashboards experienced errors and missing data due to an internal data service issue. All endpoints have been restored and historical data is now displaying correctly. We apologize for any inconvenience caused.

Feb 27, 03:04 UTC
Monitoring - Usage reporting has been restored across products, but is not returning data for usage that occurred after 2026-02-25 at around 18:40 UTC.

The team is able restore this data and is currently working on a fix

Feb 26, 22:10 UTC
Update - We …

Feb 27, 13:12 UTC
Resolved - This incident has been resolved.

Feb 27, 12:59 UTC
Investigating - We are currently investigating this issue.

Feb 26, 23:07 UTC
Resolved - We've confirmed this issue is resolved in Claude Code v2.1.61. Run `claude update` for the latest.

Feb 26, 22:43 UTC
Monitoring - We have deployed a fix to this issue in version 2.1.61. Run `claude update` to get the latest version.

We are monitoring for config corruption rates in this version since it is a nondeterministic, environment-dependent failure.

Feb 26, 21:06 UTC
Update - We are continuing to work on deploying a hotfix for this issue.

Feb 26, 19:57 UTC
Identified - We have identified a bug where Windows users are experiencing significant write contention for the .claude.json global config file, …

Feb 25, 23:54 UTC
Resolved - If Claude fails to launch on your computer, please download the latest version from download the latest version on https://claude.com/download. We have now fixed the underlying issue.

Feb 25, 17:58 UTC
Monitoring - We have released a version that fixes the issue. Please download the latest version of Claude on https://claude.com/download to update to at least v1.1.4328.

Feb 25, 17:30 UTC
Update - We continue to work on getting a fix deployed as quickly as possible.

Feb 25, 16:31 UTC
Identified - We are currently working on deploying a fix to the Claude Desktop app.

Feb 25, 16:23 UTC
Monitoring - A fix …

Feb 25, 19:37 UTC
Resolved - This incident has been resolved.

Feb 25, 19:33 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 25, 19:15 UTC
Investigating - We are currently investigating this issue.

Feb 25, 17:46 UTC
Resolved - This incident has been resolved.

Feb 25, 17:21 UTC
Update - We are continuing to investigate this issue.

Feb 25, 17:21 UTC
Update - We are continuing to investigate this issue.

Feb 25, 17:15 UTC
Investigating - We are currently investigating this issue.

Feb 25, 16:22 UTC
Resolved - This incident has been resolved.

Feb 25, 15:42 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 25, 15:02 UTC
Update - We are continuing to investigate this issue.

Feb 25, 13:58 UTC
Investigating - We are currently investigating this issue.

Feb 24, 13:26 UTC
Resolved - As of 5:10 PT / 13:10 UTC errors are back to baseline.

Feb 24, 13:00 UTC
Update - Previously this incident named Sonnet 4.5 as the affected model. This is a mistake and the model affected is Sonnet 4.6. Sorry.

Feb 24, 12:22 UTC
Investigating - We are currently investigating this issue.

Feb 24, 11:51 UTC
Resolved - This incident has been resolved.

Feb 22, 22:45 UTC
Identified - The issue has been identified and a fix is being implemented.

Feb 18, 00:30 UTC
Update - We are continuing to investigate this issue.

Feb 17, 20:15 UTC
Investigating - We are seeing periods of high error rates in a skills-related service used by claude.ai, Claude Desktop app, and our API.

Feb 24, 07:41 UTC
Resolved - As of 23:27 PT / 7:27 UTC the errors are back to the baseline.

Feb 24, 07:22 UTC
Investigating - We are currently investigating this issue.

Feb 23, 15:59 UTC
Resolved - This incident has been resolved.

Feb 23, 14:57 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 23, 14:54 UTC
Identified - The issue has been identified and a fix is being implemented.

Feb 23, 14:07 UTC
Update - We are continuing to investigate this issue.

Feb 23, 14:06 UTC
Investigating - We are currently investigating this issue.

Feb 23, 11:36 UTC
Resolved - As of 03:26 PT / 11:26 UTC the error rate has now reduced to the baseline.

Feb 23, 11:29 UTC
Identified - The issue has been identified and a fix is being implemented.

Feb 23, 11:21 UTC
Investigating - We are currently investigating this issue.

Feb 23, 09:58 UTC
Resolved - As of 01:30 PT / 09:30 UTC the error rates have returned to baseline

Feb 23, 09:39 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 23, 08:13 UTC
Identified - The issue has been identified and a fix is being implemented.

Feb 23, 08:00 UTC
Investigating - We are currently investigating this issue.

Feb 21, 23:11 UTC
Resolved - This incident has been resolved.

Feb 21, 22:16 UTC
Investigating - We are currently investigating this issue.

Feb 21, 05:00 UTC
Resolved - Some Windows users on v1.1.3918 of Desktop saw a "Virtualization is not enabled" message and were not able to use Cowork. Resolved in v1.1.3963

Feb 20, 20:17 UTC
Resolved - This incident has been resolved.

Feb 20, 20:10 UTC
Identified - The issue has been identified and a fix is being implemented.

Feb 20, 19:42 UTC
Investigating - We are currently investigating this issue.

Feb 20, 15:37 UTC
Resolved - This incident has been resolved.

Feb 20, 15:21 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 20, 14:47 UTC
Identified - The issue has been identified and a fix is being implemented.

Feb 20, 14:37 UTC
Investigating - We are currently investigating this issue.

Feb 19, 16:03 UTC
Resolved - This incident has been resolved.

Feb 19, 15:36 UTC
Update - We are continuing to investigate this issue.

Feb 19, 15:30 UTC
Investigating - We are currently investigating this issue.

Feb 18, 18:28 UTC
Resolved - This incident has been resolved.

Feb 18, 15:59 UTC
Update - We are continuing to monitor for any further issues.

Feb 18, 15:47 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 18, 15:36 UTC
Investigating - We are currently investigating this issue.

Feb 18, 15:35 UTC
Resolved - This incident has been resolved.

Feb 18, 14:22 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 18, 13:29 UTC
Identified - The issue has been identified and a fix is being implemented.

Feb 18, 13:20 UTC
Investigating - We are currently investigating this issue.

Feb 18, 12:09 UTC
Resolved - This incident has been resolved.

Feb 18, 11:56 UTC
Update - We are continuing to monitor for any further issues.

Feb 18, 11:42 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 18, 10:49 UTC
Identified - The issue has been identified and a fix is being implemented.

Feb 18, 04:07 UTC
Resolved - This incident has been resolved.

Feb 18, 03:38 UTC
Identified - The issue has been identified and a fix is being implemented.

Feb 18, 03:23 UTC
Investigating - We are currently investigating this issue.

Feb 18, 00:10 UTC
Resolved - This incident has been resolved.

Feb 17, 23:59 UTC
Update - We are continuing to monitor for any further issues.

Feb 17, 23:59 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 17, 23:56 UTC
Investigating - We are currently investigating this issue.

Feb 17, 21:05 UTC
Resolved - This incident has been resolved.

Feb 17, 20:16 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 17, 19:20 UTC
Identified - The issue has been identified and a fix is being implemented.

Feb 17, 20:04 UTC
Resolved - This incident has been resolved.

Feb 17, 15:26 UTC
Investigating - We are currently investigating an issue with new user-created skills on Claude.ai. Our team is actively working to identify the root cause.

Feb 17, 19:02 UTC
Resolved - This incident has been resolved.

Feb 17, 18:38 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 17, 18:26 UTC
Identified - The issue has been identified and a fix is being implemented.

Feb 17, 18:01 UTC
Investigating - We are currently investigating this issue.

Feb 17, 16:39 UTC
Resolved - This incident has been resolved.

Feb 17, 16:31 UTC
Update - We are continuing to monitor for any further issues.

Feb 17, 15:39 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 17, 14:43 UTC
Update - We are continuing to work on a fix for this issue.

Feb 17, 13:45 UTC
Identified - The issue has been identified and a fix is being implemented.

Feb 17, 13:13 UTC
Investigating - We are currently investigating this issue.

Feb 16, 19:15 UTC
Resolved - This incident has been resolved.

Feb 16, 16:55 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 16, 16:36 UTC
Identified - The issue has been identified and a fix is being implemented.

Feb 16, 16:05 UTC
Investigating - We are currently investigating this issue. Our team is actively working to identify the root cause.

Feb 16, 15:06 UTC
Resolved - This incident has been resolved.

Feb 16, 14:39 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 16, 14:32 UTC
Investigating - We are currently investigating this issue.

Feb 14, 16:39 UTC
Resolved - We have deployed a fix for Code Execution tool on the API.

Feb 14, 16:38 UTC
Update - We are continuing to monitor for any further issues.

Feb 14, 16:27 UTC
Monitoring - We have identified the issue with the Code Execution tool and have rolled out a fix. We're monitoring to confirm resolution.

Feb 14, 16:13 UTC
Investigating - We're currently investigating an issue where API requests using the Code Execution Tool are erroring for users.

Feb 14, 08:44 UTC
Resolved - This incident has been resolved.

Feb 14, 08:38 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 14, 07:31 UTC
Update - We are continuing to investigate this issue.

Feb 14, 07:27 UTC
Investigating - We are currently investigating this issue.

Feb 13, 23:21 UTC
Resolved - This issue has been resolved.

Feb 13, 17:56 UTC
Investigating - We are currently investigating this issue.

Feb 13, 21:27 UTC
Resolved - This incident has been resolved.

Feb 13, 17:13 UTC
Investigating - We are currently investigating this issue.

Feb 12, 15:17 UTC
Resolved - This incident has been resolved.

Feb 12, 14:45 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 12, 14:18 UTC
Investigating - We are currently investigating this issue.

Feb 11, 15:43 UTC
Resolved - This incident has been resolved.

Feb 11, 14:52 UTC
Investigating - We are currently investigating this issue.

Feb 11, 14:55 UTC
Resolved - This incident has been resolved.

Feb 11, 13:44 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 11, 13:22 UTC
Investigating - We are currently investigating this issue. Our team is actively working to identify the root cause.

Feb 11, 08:37 UTC
Resolved - This incident has been resolved.

Feb 11, 08:31 UTC
Monitoring - A fix has been implemented and we are monitoring the results.

Feb 11, 08:21 UTC
Investigating - We are currently investigating this issue.

Feb 11, 05:41 UTC
Resolved - This incident has been resolved.

Feb 11, 02:51 UTC
Monitoring - The issue has been mitigated.

Feb 10, 22:11 UTC
Investigating - We are currently investigating the issue.

Feb 10, 16:28 UTC
Resolved - This incident has been resolved.

Feb 10, 13:20 UTC
Identified - The issue has been identified and a fix is being implemented.

Feb 10, 11:23 UTC
Investigating - Starting at about 02:05 PST Opus 4.6 Fast Mode serves a small amount of errors. We are investigating.

Feb 7, 16:31 UTC
Resolved - As of 16:27 UTC / 8:27 PT the incident has been resolved.

Feb 7, 16:08 UTC
Identified - Starting with 15:15 UTC / 7:15 PT we've seen errors on our API for several models. We have identified the issue and are rolling out a fix.

Feb 7, 15:59 UTC
Investigating - We are currently investigating this issue.

Feb 6, 19:30 UTC
Resolved - This issue has been resolved.