Subscribe to UpdatesSubscribe
Get email notifications whenever Claude creates, updates or resolves an incident.
Get text message notifications whenever Claude creates or resolves an incident.
Get incident updates and maintenance status messages in Slack.
Subscribe via Slack
By subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get incident updates and maintenance status messages in Microsoft Teams channel.
By subscribing you acknowledge our Privacy Policy. In addition, you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy.
Get webhook notifications whenever Claude creates an incident, updates an incident, resolves an incident or changes a component status.
Visit our support site.
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 06, 2026 - 17:16 UTC
Mar 06, 2026 - 17:16 UTC
Uptime over the past 90 days. View historical uptime.
claude.ai
Operational
90 days ago
99.35
% uptime
Today
platform.claude.com (formerly console.anthropic.com)
Operational
90 days ago
99.5
% uptime
Today
Claude API (api.anthropic.com)
Operational
90 days ago
99.4
% uptime
Today
Claude Code
Operational
90 days ago
99.64
% uptime
Today
Claude for Government
Operational
90 days ago
99.79
% 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.
Related
No incidents or maintenance related to this downtime.
Past Incidents
Mar 7, 2026
No incidents reported today.
Mar 6, 2026
Resolved -
This incident has been resolved.
Mar 6, 16:23 UTC
Mar 6, 16:23 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Mar 6, 16:01 UTC
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 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
Mar 4, 17:01 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Mar 4, 16:13 UTC
Mar 4, 16:13 UTC
Investigating -
The earlier issues with Haiku 4.5 have reappeared.
Mar 4, 15:58 UTC
Mar 4, 15:58 UTC
Resolved -
This incident has been resolved.
Mar 4, 15:57 UTC
Mar 4, 15:57 UTC
Investigating -
We are currently investigating this issue.
Mar 4, 14:14 UTC
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
Mar 4, 14:55 UTC
Investigating -
We are currently investigating this issue.
Mar 4, 14:47 UTC
Mar 4, 14:47 UTC
Resolved -
This incident has been resolved.
Mar 4, 08:32 UTC
Mar 4, 08:32 UTC
Monitoring -
We have applied a fix for usage reporting and are monitoring the recovery
Mar 4, 01:29 UTC
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
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
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
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
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, 16:49 UTC
Mar 3, 2026
Resolved -
This incident has been resolved.
Mar 3, 16:38 UTC
Mar 3, 16:38 UTC
Investigating -
We are currently investigating this issue.
Mar 3, 15:40 UTC
Mar 3, 15:40 UTC
Resolved -
This incident has been resolved.
Mar 3, 15:39 UTC
Mar 3, 15:39 UTC
Investigating -
We are currently investigating this issue.
Mar 3, 14:51 UTC
Mar 3, 14:51 UTC
Resolved -
This incident has been resolved.
Mar 3, 14:29 UTC
Mar 3, 14:29 UTC
Update -
We are continuing to monitor for any further issues.
Mar 3, 14:29 UTC
Mar 3, 14:29 UTC
Update -
A fix has been implemented and we are monitoring the results.
Mar 3, 14:11 UTC
Mar 3, 14:11 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Mar 3, 14:03 UTC
Mar 3, 14:03 UTC
Update -
We are continuing to work on a fix for this issue.
Mar 3, 12:59 UTC
Mar 3, 12:59 UTC
Identified -
The issue is reoccurring, a fix is being implemented.
Mar 3, 12:00 UTC
Mar 3, 12:00 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Mar 3, 10:27 UTC
Mar 3, 10:27 UTC
Identified -
The issue has been identified and a fix is being implemented.
Mar 3, 08:31 UTC
Mar 3, 08:31 UTC
Investigating -
We are currently investigating this issue.
Mar 3, 06:59 UTC
Mar 3, 06:59 UTC
Resolved -
This incident has been resolved.
Mar 3, 10:18 UTC
Mar 3, 10:18 UTC
Update -
We are continuing to monitor for any further issues.
Mar 3, 09:36 UTC
Mar 3, 09:36 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Mar 3, 08:39 UTC
Mar 3, 08:39 UTC
Update -
We are continuing to investigate this issue.
Mar 3, 04:43 UTC
Mar 3, 04:43 UTC
Update -
We are continuing to investigate this issue.
Mar 3, 04:41 UTC
Mar 3, 04:41 UTC
Update -
We are continuing to investigate this issue.
Mar 3, 04:39 UTC
Mar 3, 04:39 UTC
Investigating -
We are currently investigating this issue.
Mar 3, 03:15 UTC
Mar 3, 03:15 UTC
Mar 2, 2026
Resolved -
This incident has been resolved.
Mar 2, 21:16 UTC
Mar 2, 21:16 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Mar 2, 18:54 UTC
Mar 2, 18:54 UTC
Investigating -
We are seeing a repeat of this issue, we are currently investigating.
Mar 2, 18:18 UTC
Mar 2, 18:18 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Mar 2, 18:07 UTC
Mar 2, 18:07 UTC
Investigating -
We are currently investigating this issue.
Mar 2, 17:56 UTC
Mar 2, 17:56 UTC
Resolved -
This incident has been resolved.
Mar 2, 17:55 UTC
Mar 2, 17:55 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Mar 2, 17:24 UTC
Mar 2, 17:24 UTC
Identified -
The issue has been identified and a fix is being implemented.
Mar 2, 17:15 UTC
Mar 2, 17:15 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Mar 2, 17:09 UTC
Mar 2, 17:09 UTC
Investigating -
We are currently investigating this issue.
Mar 2, 16:50 UTC
Mar 2, 16:50 UTC
Resolved -
This incident has been resolved.
Mar 2, 17:23 UTC
Mar 2, 17:23 UTC
Investigating -
We are currently investigating this issue.
Mar 2, 17:08 UTC
Mar 2, 17:08 UTC
Resolved -
This incident has been resolved.
Mar 2, 15:50 UTC
Mar 2, 15:50 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Mar 2, 15:49 UTC
Mar 2, 15:49 UTC
Identified -
The issue has been identified and a fix is being implemented.
Mar 2, 14:42 UTC
Mar 2, 14:42 UTC
Update -
We are continuing to investigate this issue.
Mar 2, 14:35 UTC
Mar 2, 14:35 UTC
Investigating -
We are currently investigating this issue.
Mar 2, 14:35 UTC
Mar 2, 14:35 UTC
Resolved -
This incident has been resolved.
Mar 2, 15:47 UTC
Mar 2, 15:47 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Mar 2, 15:25 UTC
Mar 2, 15:25 UTC
Update -
We are continuing to work on a fix for this issue.
Mar 2, 14:05 UTC
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
Mar 2, 13:37 UTC
Identified -
The issue has been identified and a fix is being implemented.
Mar 2, 13:22 UTC
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
Mar 2, 12:21 UTC
Update -
We are continuing to investigate this issue.
Mar 2, 12:06 UTC
Mar 2, 12:06 UTC
Investigating -
We are currently investigating this issue.
Mar 2, 11:49 UTC
Mar 2, 11:49 UTC
Mar 1, 2026
No incidents reported.
Feb 28, 2026
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:34 UTC
Feb 28, 18:34 UTC
Investigating -
We are currently investigating this issue.
Feb 28, 18:09 UTC
Feb 28, 18:09 UTC
Resolved -
This incident has been resolved.
Feb 28, 15:50 UTC
Feb 28, 15:50 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Feb 28, 13:07 UTC
Feb 28, 13:07 UTC
Investigating -
We are currently investigating this issue.
Feb 28, 12:57 UTC
Feb 28, 12:57 UTC
Feb 27, 2026
Resolved -
This incident has been resolved.
Feb 27, 19:43 UTC
Feb 27, 19:43 UTC
Investigating -
We are currently investigating this issue.
Feb 27, 19:32 UTC
Feb 27, 19:32 UTC
Resolved -
This incident has been resolved.
Feb 27, 17:21 UTC
Feb 27, 17:21 UTC
Update -
We are continuing to monitor for any further issues.
Feb 27, 17:21 UTC
Feb 27, 17:21 UTC
Monitoring -
Some new logins to the Claude Desktop app were not working.
Feb 27, 14:00 UTC
Feb 27, 14:00 UTC
Resolved -
This incident has been resolved.
Feb 27, 17:17 UTC
Feb 27, 17:17 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Feb 27, 13:41 UTC
Feb 27, 13:41 UTC
Investigating -
We are currently investigating this issue.
Feb 27, 13:14 UTC
Feb 27, 13:14 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, 14:23 UTC
Feb 27, 14:23 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 27, 03:04 UTC
The team is able restore this data and is currently working on a fix
Feb 27, 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, 22:10 UTC
The issue has been identified and the team is working on a fix
Feb 26, 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, 18:52 UTC
The team is still working on fixes for other endpoints and services
Feb 26, 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, 17:24 UTC
The issue has been identified and the team is working on a fix
Feb 26, 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, 15:56 UTC
The issue has been identified and the team is working on a fix
Feb 26, 15:56 UTC
Resolved -
This incident has been resolved.
Feb 27, 13:12 UTC
Feb 27, 13:12 UTC
Investigating -
We are currently investigating this issue.
Feb 27, 12:59 UTC
Feb 27, 12:59 UTC
Feb 26, 2026
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
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
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
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
Feb 26, 19:57 UTC
Feb 25, 2026
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
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
Feb 25, 17:58 UTC
Update -
We continue to work on getting a fix deployed as quickly as possible.
Feb 25, 17:30 UTC
Feb 25, 17:30 UTC
Identified -
We are currently working on deploying a fix to the Claude Desktop app.
Feb 25, 16:31 UTC
Feb 25, 16:31 UTC
Monitoring -
A fix has been deployed and we're monitoring error rates.
Feb 25, 16:23 UTC
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
Feb 25, 16:23 UTC
Resolved -
This incident has been resolved.
Feb 25, 19:37 UTC
Feb 25, 19:37 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Feb 25, 19:33 UTC
Feb 25, 19:33 UTC
Investigating -
We are currently investigating this issue.
Feb 25, 19:15 UTC
Feb 25, 19:15 UTC
Resolved -
This incident has been resolved.
Feb 25, 17:46 UTC
Feb 25, 17:46 UTC
Update -
We are continuing to investigate this issue.
Feb 25, 17:21 UTC
Feb 25, 17:21 UTC
Update -
We are continuing to investigate this issue.
Feb 25, 17:21 UTC
Feb 25, 17:21 UTC
Investigating -
We are currently investigating this issue.
Feb 25, 17:15 UTC
Feb 25, 17:15 UTC
Resolved -
This incident has been resolved.
Feb 25, 16:22 UTC
Feb 25, 16:22 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Feb 25, 15:42 UTC
Feb 25, 15:42 UTC
Update -
We are continuing to investigate this issue.
Feb 25, 15:02 UTC
Feb 25, 15:02 UTC
Investigating -
We are currently investigating this issue.
Feb 25, 13:58 UTC
Feb 25, 13:58 UTC
Feb 24, 2026
Resolved -
As of 5:10 PT / 13:10 UTC errors are back to baseline.
Feb 24, 13:26 UTC
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
Feb 24, 13:00 UTC
Investigating -
We are currently investigating this issue.
Feb 24, 12:22 UTC
Feb 24, 12:22 UTC
Resolved -
This incident has been resolved.
Feb 24, 11:51 UTC
Feb 24, 11:51 UTC
Identified -
The issue has been identified and a fix is being implemented.
Feb 22, 22:45 UTC
Feb 22, 22:45 UTC
Update -
We are continuing to investigate this issue.
Feb 18, 00:30 UTC
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
Feb 17, 20:15 UTC
Resolved -
As of 23:27 PT / 7:27 UTC the errors are back to the baseline.
Feb 24, 07:41 UTC
Feb 24, 07:41 UTC
Investigating -
We are currently investigating this issue.
Feb 24, 07:22 UTC
Feb 24, 07:22 UTC
Feb 23, 2026
Resolved -
This incident has been resolved.
Feb 23, 15:59 UTC
Feb 23, 15:59 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Feb 23, 14:57 UTC
Feb 23, 14:57 UTC
Identified -
The issue has been identified and a fix is being implemented.
Feb 23, 14:54 UTC
Feb 23, 14:54 UTC
Update -
We are continuing to investigate this issue.
Feb 23, 14:07 UTC
Feb 23, 14:07 UTC
Investigating -
We are currently investigating this issue.
Feb 23, 14:06 UTC
Feb 23, 14:06 UTC
Resolved -
As of 03:26 PT / 11:26 UTC the error rate has now reduced to the baseline.
Feb 23, 11:36 UTC
Feb 23, 11:36 UTC
Identified -
The issue has been identified and a fix is being implemented.
Feb 23, 11:29 UTC
Feb 23, 11:29 UTC
Investigating -
We are currently investigating this issue.
Feb 23, 11:21 UTC
Feb 23, 11:21 UTC
Resolved -
As of 01:30 PT / 09:30 UTC the error rates have returned to baseline
Feb 23, 09:58 UTC
Feb 23, 09:58 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
Feb 23, 09:39 UTC
Feb 23, 09:39 UTC
Identified -
The issue has been identified and a fix is being implemented.
Feb 23, 08:13 UTC
Feb 23, 08:13 UTC
Investigating -
We are currently investigating this issue.
Feb 23, 08:00 UTC
Feb 23, 08:00 UTC
Feb 22, 2026
Feb 21, 2026
Resolved -
This incident has been resolved.
Feb 21, 23:11 UTC
Feb 21, 23:11 UTC
Investigating -
We are currently investigating this issue.
Feb 21, 22:16 UTC
Feb 21, 22:16 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
Feb 21, 05:00 UTC