Anthropic Status

Resolved: This incident has been resolved.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

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

Resolved: This incident has been resolved.

Investigating: We are currently investigating this issue.

Resolved: As of 01:30 PT / 09:30 UTC the error rates have returned to baseline

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.

Resolved: As of 03:26 PT / 11:26 UTC the error rate has now reduced to the baseline.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: As of 23:27 PT / 7:27 UTC the errors are back to the baseline.

Investigating: We are currently investigating this issue.

Resolved: As of 5:10 PT / 13:10 UTC errors are back to baseline.

Investigating: Previously this incident named Sonnet 4.5 as the affected model. This is a mistake and the model affected is Sonnet 4.6. Sorry.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

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.

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.

Identified: We continue to work on getting a fix deployed as quickly as possible.

Identified: We are currently working on deploying a fix to the Claude Desktop app.

Monitoring: A fix has been deployed and we're monitoring error rates.

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.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently investigating this issue.

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.

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

Identified: 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

Identified: 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

Identified: 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

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

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: Some new logins to the Claude Desktop app were not working.

Resolved: This incident has been resolved.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Investigating: We are currently investigating this issue.

Resolved: As of 01:30 PT / 09:30 UTC the error rates have returned to baseline

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: As of 5:10 PT / 13:10 UTC errors are back to baseline.

Investigating: Previously this incident named Sonnet 4.5 as the affected model. This is a mistake and the model affected is Sonnet 4.6. Sorry.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently investigating this issue.

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.

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

Identified: 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

Identified: 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

Identified: 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

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

Resolved: This incident has been resolved.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

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

Resolved: This incident has been resolved.

Investigating: We are currently investigating this issue.

Resolved: As of 01:30 PT / 09:30 UTC the error rates have returned to baseline

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.

Resolved: As of 03:26 PT / 11:26 UTC the error rate has now reduced to the baseline.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: As of 23:27 PT / 7:27 UTC the errors are back to the baseline.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Investigating: We are continuing to investigate this issue.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently investigating this issue.

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.

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

Identified: 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

Identified: 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

Identified: 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

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

Resolved: This incident has been resolved.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Investigating: We are currently investigating this issue.

Resolved: As of 01:30 PT / 09:30 UTC the error rates have returned to baseline

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.

Resolved: As of 03:26 PT / 11:26 UTC the error rate has now reduced to the baseline.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: As of 23:27 PT / 7:27 UTC the errors are back to the baseline.

Investigating: We are currently investigating this issue.

Resolved: As of 5:10 PT / 13:10 UTC errors are back to baseline.

Investigating: Previously this incident named Sonnet 4.5 as the affected model. This is a mistake and the model affected is Sonnet 4.6. Sorry.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently investigating this issue.

Resolved: We've confirmed this issue is resolved in Claude Code v2.1.61. Run claude update for the latest.

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.

Identified: We are continuing to work on deploying a hotfix for this issue.

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.

Resolved: This incident has been resolved.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Investigating: We are currently investigating this issue.

Resolved: As of 01:30 PT / 09:30 UTC the error rates have returned to baseline

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: The issue has been identified and a fix is being implemented.

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are currently investigating this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved.

Investigating: We are currently investigating this issue.