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 27, 2026 - 03:04 UTC
Update - We are responding to an outage in usage reporting across products and APIs.
The issue has been identified and the team is working on a fix
Feb 26, 2026 - 22:10 UTC
Update - A fix has been deployed for the /v1/organizations/usage_report/messages admin API endpoint.
The team is still working on fixes for other endpoints and services
Feb 26, 2026 - 18:52 UTC
Update - We are responding to an outage in usage reporting across products and APIs.
The issue has been identified and the team is working on a fix
Feb 26, 2026 - 17:24 UTC
Identified - We are responding to an outage in usage reporting via the Console and the admin API's /v1/organizations/usage_report endpoints.
The issue has been identified and the team is working on a fix
Feb 26, 2026 - 15:56 UTC
Resolved -
We've confirmed this issue is resolved in Claude Code v2.1.61. Run `claude update` for the latest.
Feb 26, 23:07 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, 22:43 UTC
Update -
We are continuing to work on deploying a hotfix for this issue.
Feb 26, 21:06 UTC
Identified -
We have identified a bug where Windows users are experiencing significant write contention for the .claude.json global config file, starting with Claude Code 2.1.59. We are working on a hotfix.
Feb 26, 19:57 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, 23:54 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:58 UTC
Update -
We continue to work on getting a fix deployed as quickly as possible.
Feb 25, 17:30 UTC
Identified -
We are currently working on deploying a fix to the Claude Desktop app.
Feb 25, 16:31 UTC
Monitoring -
A fix has been deployed and we're monitoring error rates.
Feb 25, 16:23 UTC
Investigating -
We have identified an issue leading to the Claude Desktop app failing to start for a subset of Windows users and macOS users on older macOS releases. We are working on rolling out a fix.
Feb 25, 16:23 UTC
Resolved -
As of 5:10 PT / 13:10 UTC errors are back to baseline.
Feb 24, 13:26 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, 13:00 UTC
Investigating -
We are currently investigating this issue.
Feb 24, 12:22 UTC
Resolved -
This incident has been resolved.
Feb 24, 11:51 UTC
Identified -
The issue has been identified and a fix is being implemented.
Feb 22, 22:45 UTC
Update -
We are continuing to investigate this issue.
Feb 18, 00:30 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 17, 20:15 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 21, 05:00 UTC
Resolved -
This incident has been resolved.
Feb 17, 20:04 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, 15:26 UTC
Resolved -
We have deployed a fix for Code Execution tool on the API.
Feb 14, 16:39 UTC
Update -
We are continuing to monitor for any further issues.
Feb 14, 16:38 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:27 UTC
Investigating -
We're currently investigating an issue where API requests using the Code Execution Tool are erroring for users.
Feb 14, 16:13 UTC
