Is Claude Down?
Anthropic · API & platform status
Claude 4, Claude 3.5, Claude API, Claude Code, and all Anthropic platform services.
Official status data last reflected here:
[ STATUS AT A GLANCE ]
System Components
Current status of individual Anthropic services
Anthropic down? Route around it.
When Anthropic has issues, Bifrost automatically routes your requests to a healthy alternative provider. Zero code changes. 99.999% effective uptime.
About Anthropic
What Anthropic does, where the data on this page comes from, and recent reliability
[ ABOUT ANTHROPIC ]
About Anthropic
Anthropic provides Claude, Claude API, Claude Code, and Claude Sonnet. Anthropic outages often matter most to engineering, agent, and internal tooling use cases where Claude is deeply embedded into day-to-day developer workflows.
This page pulls data from Anthropic's official status page to show current service health, any active incidents, and a history of recent issues, all in one view.
[ DATA SOURCES ]
Full incident history available
Anthropic publishes detailed component status, a full incident archive, and scheduled maintenance data through their official status page.
- Data pulled from Anthropic's official status page (status.claude.com)
- Refreshed every 60 seconds
- Covers Claude, Claude API, Claude Code, Claude Sonnet, and Claude Opus
- Includes full incident archive and scheduled maintenance history
[ RELIABILITY ]
Recent reliability
- 50 incidents reported over the last 90 days.
- The most recent incident was reported today.
- All 6 monitored components are currently operational.
- Most frequently affected: Claude Code, claude.ai, and Claude API (api.anthropic.com).
[ COMMON USE CASES ]
How teams use Anthropic
Anthropic outages often matter most to engineering, agent, and internal tooling use cases where Claude is deeply embedded into day-to-day developer workflows.
Incidents & Maintenance
Active incidents, scheduled maintenance, and incident history for Anthropic
Active Incidents (1)
We’ve suspended access to Claude Mythos 5 and Claude Fable 5
Jun 13, 2026
Learn more here: https://anthropic.com/news/fable-mythos-access
Past Incidents
Elevated errors across many models
Jun 22, 2026 · Resolved Jun 22, 2026
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
Elevated errors for Claude Opus 4.8
Jun 22, 2026 · Resolved Jun 22, 2026
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are continuing to investigate this issue.
We are currently investigating this issue.
Elevated Error Rates for Opus 4.8, Opus 4.7, Opus 4.6, Sonnet 4.6, and Haiku 4.5
Jun 22, 2026 · Resolved Jun 22, 2026
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
Opus 4.7 has recovered
Haiku 4.5 has recovered
Opus 4.8 has recovered.
+ 3 more updates
Opus 4.8 errors
Jun 20, 2026 · Resolved Jun 20, 2026
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are continuing to investigate this issue.
We are currently investigating this issue.
Elevated error rates on the Claude API
Jun 19, 2026 · Resolved Jun 19, 2026
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
Elevated errors for Claude Opus 4.8
Jun 19, 2026 · Resolved Jun 19, 2026
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
Service disruption on Claude services
Jun 18, 2026 · Resolved Jun 18, 2026
The issue affecting Claude services has been resolved. Impact occurred from 06:55 to 07:40 UTC.
We have identified the cause of the issue affecting Claude.ai and are working on a fix. We will provide an update as soon as possible.
Elevated errors for Claude Opus 4.8
Jun 17, 2026 · Resolved Jun 17, 2026
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
Elevated errors for Claude Opus 4.8
Jun 17, 2026 · Resolved Jun 17, 2026
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
Elevated errors for Claude Opus 4.8
Jun 17, 2026 · Resolved Jun 17, 2026
This incident has been resolved. Requests to Claude Opus 4.8 received elevated errors between 9:59pm PT / 04:59 UTC and 10:41pm PT / 05:41 UTC.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
Elevated errors on Claude Sonnet 4.6 and Opus 4.8
Jun 17, 2026 · Resolved Jun 17, 2026
This incident has been resolved.
At this time, success rates for Claude Sonnet 4.6 have recovered and we are working to resolve an issue resulting in elevated errors on Opus 4.8. We will provide additional updates as soon as possible.
We are currently investigating this issue.
Elevated errors for Claude Opus 4.8
Jun 16, 2026 · Resolved Jun 16, 2026
This issue has been resolved. We saw elevated errors on requests to Claude Opus 4.8 between 1:45pm PT / 20:45 UTC and 1:58pm PT / 20:58 UTC.
We have resolved the issue resulting in elevated errors on requests to Claude Opus 4.8, and are currently monitoring closely to prevent any further issues.
We are investigating elevated errors on requests to Claude Opus 4.8. We will provide an update as soon as possible.
Opus 4.8 errors
Jun 16, 2026 · Resolved Jun 16, 2026
This incident has been resolved.
Opus 4.8 error rates were elevated from 12:41 PDT to approximately 12:53 PDT. The team is monitoring.
Elevated errors across many models
Jun 16, 2026 · Resolved Jun 16, 2026
The incident has now been resolved. We had two phases: * between 10:23 PT / 17:23 UTC to 11:00 PT / 18:00 UTC -- all Sonnet and Opus models were affected, reaching an error rate of around 10% * after 11:00 PT / 18:00 UTC and until 12:20 PT / 19:20 UTC -- Opus 4.8 had an average error rate of 10% The incident is now resolved.
A fix has been implemented and we are monitoring the results.
We are continuing to work on a fix for this issue.
We are continuing to work to resolve an elevated rate of errors on requests to Claude Opus 4.8, and will provide an additional update as soon as possible.
We are still seeing errors on Opus 4.8 and Haiku 4.5.
+ 2 more updates
Elevated errors on Claude Opus 4.8
Jun 15, 2026 · Resolved Jun 15, 2026
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
Elevated errors on Claude Opus 4.8
Jun 13, 2026 · Resolved Jun 13, 2026
This incident has been resolved.
We are currently investigating this issue.
Elevated errors across models
Jun 11, 2026 · Resolved Jun 11, 2026
The issue affecting various models has been resolved. Impact occurred from 09:42am PT / 16:42 UTC to 10:03am PT / 17:03 UTC.
A fix has been implemented and we are monitoring the results.
We are currently investigating this issue.
Elevated errors on Claude Opus 4.6
Jun 11, 2026 · Resolved Jun 11, 2026
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are currently investigating this issue.
Elevated errors on Claude Haiku 4.5
Jun 10, 2026 · Resolved Jun 10, 2026
This incident has been resolved.
We are continuing to monitor Claude Haiku 4.5 towards full recovery, and at this point have seen success rates recover to close to normal operating levels. We are working to ensure there are no further issues.
A fix has been implemented and we are monitoring the results.
We are continuing to work on a fix for this issue.
The issue has been identified and a fix is being implemented.
+ 1 more updates
Elevated errors on Claude Opus 4.6
Jun 9, 2026 · Resolved Jun 9, 2026
From 1:20pm PT / 20:20 UTC through 2:05pm PT / 21:05 PT, we saw elevated errors on requests to Claude Opus 4.6. This issue has been resolved.
We are currently investigating this issue.
Frequently Asked Questions
Is Claude down right now?
Check the status indicator at the top of this page. It pulls directly from Anthropic's official status page. If Anthropic is experiencing any issues, you'll see it reflected here. This real-time monitoring helps teams quickly identify whether performance problems are caused by Anthropic infrastructure or their own systems.
What does this Anthropic status page track?
This page tracks Claude, Claude API, Claude Code, Claude Sonnet, and Claude Opus using data from Anthropic's official status page. You can see current component health, active incidents, and a history of past issues. This visibility is crucial for teams building resilient AI applications that need to route around provider outages.
How often is Anthropic status updated here?
We check Anthropic's status page every 60 seconds to ensure you get near real-time status updates. How quickly issues show up here depends on how fast Anthropic updates their own official status. For production systems that need instant failover, Bifrost can automatically detect and route around degraded providers.
Why monitor Anthropic status?
Anthropic outages often matter most to engineering, agent, and internal tooling use cases where Claude is deeply embedded into day-to-day developer workflows. Real-time status monitoring enables proactive incident response and helps teams decide when to route traffic to alternative providers for maximum uptime.
What should I do when Claude or Anthropic has an outage?
When Anthropic experiences an outage, the best practice is automatic failover to alternative AI providers. Bifrost is an open-source AI gateway that automatically detects Anthropic degradation and routes LLM traffic to healthy alternatives like OpenAI (GPT-4), Google Gemini, Cohere, keeping your application running with zero manual intervention. This intelligent routing ensures your users never experience downtime from a single provider's issues.
How can I prevent Anthropic downtime from affecting my application?
Production AI applications should never depend on a single provider. Bifrost AI Gateway provides automatic multi-provider failover, intelligent load balancing, and health-based routing. When Anthropic degrades, Bifrost instantly routes requests to operational alternatives while maintaining API compatibility. This architecture approach is used by teams running mission-critical AI features.
What are common causes of Anthropic outages and degraded performance?
Based on incident history, Anthropic issues most frequently affect Claude Code, claude.ai, and Claude API (api.anthropic.com). Common causes include infrastructure scaling issues, regional cloud provider problems, API gateway overload, and deployment errors. Teams using Bifrost can configure automatic routing rules based on component-level status to minimize impact.
Alternative Providers for Automatic Failover
When Anthropic experiences issues, Bifrost AI Gateway can automatically route your LLM traffic to these alternatives
💡 Build resilient AI apps: Configure Bifrost to automatically detect Anthropic outages and route requests to healthy alternatives. This multi-provider approach ensures your application maintains uptime even when individual providers experience issues. Learn more about Bifrost AI Gateway
Anthropic Models & Pricing
Anthropic offers 18 models across 1 mode (18 chat)