Claude.ai had 52 outages in the last 2 years totaling 46h 9m of downtime — averaging 2.1 incidents per month.
There were 52 Claude.ai outages since March 18, 2026 totaling 46h 9m of downtime. Each is summarised below — incident details, duration, and resolution information.
The issue has been identified and a fix is being implemented.
Earlier today we had an outage on Opus 4.6 that started at 23:03 PT / 6:03 UTC and ended at 00:26 PT / 7:26 UTC.
We are seeing increased errors on Claude.ai, API, and Claude Code
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
The Claude API has fully recovered as of 8:01 PT / 16:01 UTC. We are currently working on mitigating the ongoing errors for Claude AI. Claude Code users who are logged in are still able to use it, but logging in is still broken.
Claude.ai and Platform are down. Login for Claude Code does not work via Claude.ai.
We have seen success rates for login to Claude.ai, including via Claude Code, stabilize and are working to fully resolve this issue. We will provide an update shortly.
This incident has been resolved.
We are investigating reports of degraded performance affecting the usage and analytics admin API endpoints. We will provide an update as soon as possible.
Root cause identified. Fixes have been merged and are progressing through our deployment pipeline. Intermittent 503 errors on usage and analytics admin API endpoints may continue until the rollout completes. We will update once the fix is live in production.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate elevated errors on Claude.ai, primarily affecting login. We will provide an update as soon as possible.
We have identified the issue affecting Claude.ai and Claude Code logins. We are working to apply a fix for this issue, and will provide an additional update as soon as possible.
We have resolved the issue resulting in elevated errors on login for Claude.ai and Claude Code betwen 15:31 to 16:19 UTC.
We are investigating reports of elevated errors on requests to Claude across all products. We will provide an update as soon as possible.
We have identified the current issue as affecting requests to models other than Claude Opus 4.6, and are working to fully resolve this issue. We will provide additional updates shortly.
The issue affecting requests to non-Opus models has been resolved.
Certain connectors are experiencing higher error rates. We are investigating the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We have identified an issue resulting in elevated errors on Claude.ai, including desktop and mobile. Users may experience errors when attempting to login, engaging with voice mode, or completing chats with Claude. We are working to resolve this issue as soon as possible.
We have applied a fix and success rates have returned to normal. We are continuing to monitor closely to ensure there are no further issues.
From 14:32–15:12 UTC, we saw elevated errors impacting various Claude services, including Claude.ai and Claude Code authentication. These errors have been resolved.
We are currently investigating an issue resulting in elevated errors on requests to Claude Sonnet 4.6. We will provide an update as soon as possible.
This incident has been resolved.
We have identified an issue which results in the Claude.ai desktop application returning an error when attempting to connect. We are working to resolve this issue as quickly as possible, and the Claude.ai website is unaffected.
This incident has been resolved.
We have identified an issue resulting in elevated errors on requests to Claude Opus 4.6, and are working to resolve this. We will provide an update as soon as possible.
This incident has been resolved.
We have identified an issue which resulted in elevated rates of timeouts when making requests to Claude Opus 4.6 and Sonnet 4.6 from 17:45 UTC on March 31 through 05:52 UTC on April 1. This issue has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have identified an issue which has resulted in some Claude.ai connectors becoming unavailable within the desktop application. We are working to restore access to these extensions, and will provide an update as soon as possible.
We have resolved an issue that resulted in the unavailability of connectors in the Claude.ai desktop application. Affected connectors were removed from organization allowlists, and can be manually re-added while we work to automatically restore impacted allowlists.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
This incident has been resolved.
Issue started at 1:33 PT / 8:53 UTC.
At baseline error rate from 2:19 PT / 9:19 UTC.
This incident has been resolved.
We've identified an issue in the latest Claude Desktop release (Claude 1.1.9310) where Dispatch sessions stop responding. Messages sent to Dispatch are received and processed, but replies do not appear in the conversation. We have identified the cause and are working on a fix. As a workaround, you can continue using standard Cowork sessions, which are unaffected.
The issue affecting Dispatch has been resolved. We fixed an underlying issue that prevent the agent from sending responses to user messages. Please update to Claude desktop app 1.1.9493. We apologize for any inconvenience caused.
We are currently investigating this issue.
We are continuing to investigate the ongoing incident.
Sonnet 4.6 is also showing elevated errors.
As of 5:00 PT / 12:00 UTC Sonnet 4.6 is now healthy. We are still working to fix Opus 4.6.
We have mitigated the main issue and the error rate for Opus 4.6 is hovering around 0.4% which is still high, but much better than the performance during the previous hours. We are waiting for a more permanent fix to land in the near future.
As of 6:40 PT / 13:40 UTC our error rate has returned to the baseline. We are still monitoring the current situation.
This incident has been mitigated as of 9:30 PT / 16:30 UTC.
On March 26–27, 2026, customers experienced elevated error rates when using Claude Opus 4.6 and Claude Sonnet 4.6. The issue was caused by a networking performance degradation within our infrastructure that disrupted communication between components of our serving stack. We resolved the incident by migrating the affected workloads to healthy infrastructure, restoring normal service by 9:30 AM PT on March 27.
We are currently investigating an issue resulting in elevated errors for some MCP calls. We will provide an update as soon as possible.
This incident has been resolved.
We are currently investigating an issue resulting in elevated errors on requests to Claude Opus 4.6 and Sonnet 4.6. We will provide an update as soon as possible.
We have identified an issue resulting in a low rate of errors on requests to Claude Opus 4.6 and Sonnet 4.6, we are continuing to work to fully resolve this issue and will provide additional updates.
This incident has been resolved.
We are currently investigating this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
We are currently seeing recovery, and our engineers are working to ensure no further recurrences. We will provide an update as soon as possible.
This incident has been resolved.
Between 9:10 PT / 16:10 UTC and 9:26 PT / 16:26 UTC users saw an elevated rate of errors on Claude.ai The Claude API was unaffected.
This incident has been resolved.
We are investigating an issue preventing logins on Claude Console (platform.claude.com)
We are investigating an issue with users authenticating to claude.ai and Claude Console (platform.claude.com)
A mitigation has been applied. Logins have returned to normal, the team is continuing to monitor the situation.
This incident has been resolved. Logins and authentication for claude.ai and platform.claude.com have returned to normal
Since approximately 20:00 UTC / 13:00 PT on Friday, March 20, Claude.ai responses may appear to "hang" for around 5 seconds after the text has finished streaming before the message completes. The Anthropic API is not affected.
The issue has been identified and a fix is being implemented.
As of 13:02 UTC / 06:02 PT this incident has been mitigated.
We are currently investigating elevated error rates affecting Claude Opus 4.6. Our team is actively working to identify the root cause.
We have identified an issue resulting in elevated errors on both Claude Opus and Sonnet 4.6, and are working to resolve this issue as quickly as possible.
We have observed success rates return to normal for Claude Opus 4.6, and are working to fully resolve elevated errors for Claude Sonnet 4.6.
This incident has been resolved.