Claude Code had 114 outages in the last 2 years totaling 26h 22m of downtime — averaging 4.7 incidents per month.
There were 114 Claude Code outages since March 18, 2026 totaling 26h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.
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 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 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.
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.
We are currently investigating this issue.
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 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 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.
We are currently investigating this issue. Our team is actively working to identify the root cause.
From 23:59–00:30 UTC, users experienced elevated errors when trying to authenticate across various Claude surfaces including Claude.ai and Claude Code. This issue has been resolved, and we are monitoring closely to ensure no further issues.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.