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
- 48 incidents reported over the last 90 days.
- Last reported incident was 7 days ago.
- All 6 monitored components are currently operational.
- Most frequently affected: claude.ai, Claude Cowork, and Claude Code.
[ 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
Past Incidents
Elevated errors affecting the Google Calendar connector
Oct 28, 2026 · Resolved Oct 28, 2026
The issue affecting the Google Calendar connector on claude.ai, Claude Code, and Claude Cowork has been resolved. Impact occurred from 04:07 PT / 11:07 UTC on October 26 to 11:52 PT / 18:52 UTC on October 28.
We are seeing recovery for errors affecting the Google Calendar connector, and error rates have returned to normal levels. We are continuing to monitor with our upstream provider.
We are continuing to investigate elevated errors affecting the Google Calendar connector, and are working with our upstream provider. We will provide another update as soon as we have more information.
We are investigating elevated errors affecting the Google Calendar connector. Some requests to list or search calendar events have been failing since October 26. We will provide an update as soon as possible.
Elevated errors affecting the Gmail connector
Oct 28, 2026 · Resolved Oct 28, 2026
The issue affecting the Gmail connector on claude.ai, Claude Code, and Claude Cowork has been resolved. Impact occurred from 16:00 PT / 23:00 UTC on October 27 to 22:29 PT on October 27 / 05:29 UTC on October 28.
We are investigating elevated errors when searching and reading email with the Gmail connector. This issue does not affect other connectors.
We are investigating elevated errors when searching and reading email with the Gmail connector. This issue does not affect other connectors. We will provide an update as soon as possible.
Elevated errors for Claude Sonnet 5.5
Oct 27, 2026 · Resolved Oct 27, 2026
The issue affecting claude.ai, the Claude API, Claude Code, and Claude Cowork has been resolved. Impact occurred from 07:42 PT / 14:42 UTC to 08:17 PT / 15:17 UTC.
We are investigating elevated errors on requests to Claude Sonnet 5.5. We will provide an update as soon as possible.
Elevated errors for Claude Sonnet 5.5
Oct 27, 2026 · Resolved Oct 27, 2026
The issue affecting Claude services has been resolved.
A fix has been deployed for the issue affecting Claude services and we are monitoring for recovery.
We are investigating elevated errors on requests to Claude Sonnet 5.5. We will provide an update as soon as possible.
Elevated errors for Claude Fable 5.1
Oct 25, 2026 · Resolved Oct 25, 2026
The issue affecting Claude services has been resolved. Impact occurred from 01:08 PT / 08:08 UTC to 01:29 PT / 08:29 UTC.
A fix has been deployed for the issue affecting Claude services and we are monitoring for recovery.
We have identified the cause of elevated errors on requests to Claude Fable 5.1 and are working on a fix. We will provide an update as soon as possible.
We are investigating elevated errors on requests to Claude Fable 5.1. We will provide an update as soon as possible.
Elevated errors for Claude Sonnet 5.5 and other models
Oct 25, 2026 · Resolved Oct 25, 2026
The issue affecting Claude services has been resolved. Impact occurred from 23:05 PT on October 24 / 06:05 UTC on October 25 to 23:35 PT on October 24 / 06:35 UTC on October 25.
A fix has been deployed for the issue affecting Claude services and we are monitoring for recovery.
We have identified the cause of elevated errors on requests to Claude Sonnet 5.5 and are working on a fix. We will provide an update as soon as possible.
We are investigating elevated errors on requests to Claude Mythos 5.1, Claude Fable 5.1, Claude Opus 5.5, Claude Sonnet 5.5, and Claude Haiku 5.5. We will provide an update as soon as possible.
Elevated errors for Claude Fable 5 and Claude Fable 5.1
Oct 24, 2026 · Resolved Oct 24, 2026
The issue affecting Claude services has been resolved. Impact occurred from 22:00 PT on October 23 / 05:00 UTC on October 24 to 22:35 PT on October 23 / 05:35 UTC on October 24.
A fix has been deployed for the issue affecting Claude services and we are monitoring for recovery.
We have identified the cause of elevated errors on requests to other Claude models and are working on a fix. We will provide an update as soon as possible.
We have identified the cause of elevated errors on requests to other Claude models and are working on a fix. We will provide an update as soon as possible.
We are investigating elevated errors on requests to other Claude models. We will provide an update as soon as possible.
Elevated errors for Claude Opus 5.5
Oct 24, 2026 · Resolved Oct 24, 2026
The issue affecting Claude Opus 5.5 has been resolved. Impact occurred from 17:23 PT on October 23 / 00:23 UTC on October 24 to 17:34 PT on October 23 / 00:34 UTC on October 24.
We are investigating elevated errors on requests to Claude Opus 5.5. We will provide an update as soon as possible.
Elevated errors for Claude Fable 5.1, Sonnet 5.5, and Haiku 5.5
Oct 23, 2026 · Resolved Oct 24, 2026
The issue affecting Claude models has been resolved. Impact occurred from 16:28 PT / 23:28 UTC on October 23 to 16:59 PT / 23:59 UTC on October 23.
We are seeing success rates return to normal for all affected models, and are continuing to monitor to ensure no further issues.
We have identified the cause of elevated errors on requests to Claude Fable 5.1, Sonnet 5.5, and Haiku 5.5, as well as fast mode requests to Opus 5.5 and are working on a fix. We will provide an update as soon as possible.
We are investigating elevated errors on requests to Claude Fable 5.1. We will provide an update as soon as possible.
Elevated errors affecting Connectors
Oct 22, 2026 · Resolved Oct 22, 2026
The issue affecting claude.ai and Claude Cowork has been resolved.
A fix has been deployed for the issue affecting claude.ai and Claude Cowork and we are monitoring for recovery.
We are investigating elevated errors affecting connectors. We will provide an update as soon as possible.
Degraded performance for Claude Fable 5
Oct 21, 2026 · Resolved Oct 21, 2026
The issue affecting other Claude models has been resolved.
We are investigating elevated errors on requests to Claude Fable 5. We will provide an update as soon as possible.
Elevated errors on platform.claude.com
Oct 7, 2026 · Resolved Oct 13, 2026
This issue has been resolved.
We've mitigated the errors loading usage data on platform.claude.com and in the Admin API usage report. While we work on a full fix, the most recent ~30 minutes of usage may take longer to appear on the platform.claude.com. API requests are not affected, and we will provide additional updates here.
We've identified the cause of errors loading usage data. The Admin API usage report has recovered, and fixes for the platform.claude.com Usage and Rate limits pages are in progress. The most recent 30 minutes of usage may be delayed. Core functionality is not affected.
We are continuing to work on elevated errors affecting usage data on the platform.claude.com Usage and Rate limits pages and the Admin API usage report. A mitigation for the Usage page and the Admin API usage report is rolling out; once it is in place, the most recent usage may take about 30 minutes to appear there. Core functionality is not affected.
We are investigating elevated errors affecting usage data on the platform.claude.com Usage page and the Admin API usage report. Core functionality is not affected. We will provide an update as soon as possible.
Issue with spend limits
Oct 7, 2026 · Resolved Oct 7, 2026
We have identified an issue which resulted in some organizations to be incorrectly paused for having reached their spend limit, resulting in refused requests on the Claude API, Claude.ai, Claude Code, Claude Security, and Claude Cowork. This is now resolved.
Elevated errors loading usage data on platform.claude.com
Oct 7, 2026 · Resolved Oct 7, 2026
This incident has been resolved. From 17:00 PT on October 6 / 00:00 UTC on October 7 to 18:40 PT on October 6 / 01:40 UTC on October 7, many requests to load usage data on the platform.claude.com Usage page and the Admin API usage report returned errors.
We are investigating elevated errors loading usage data on the platform.claude.com Usage page and the Admin API usage report endpoint since 5 PM PT. Messages API requests are not affected. We will provide an update as soon as possible.
Elevated errors for Claude Opus 5.5
Oct 6, 2026 · Resolved Oct 6, 2026
The issue affecting Claude Opus 5.5 has been resolved.
We have identified the cause of elevated errors on requests to Claude Opus 5.5 and are working on a fix. We will provide an update as soon as possible.
We are investigating elevated errors on requests to Claude Opus 5.5. We will provide an update as soon as possible.
Elevated errors for Claude Mythos 5.1 and Claude Fable 5.1
Oct 5, 2026 · Resolved Oct 5, 2026
The issue affecting Claude Mythos 5.1 and Claude Fable 5.1 has been resolved. Impact occurred from 05:40 PT / 12:40 UTC to 06:10 PT / 13:10 UTC.
We are investigating elevated errors on requests to Claude Mythos 5.1 and Claude Fable 5.1. We will provide an update as soon as possible.
Delayed credits on the Claude Platform
Oct 1, 2026 · Resolved Oct 1, 2026
This issue has been resolved.
We have resolved the issue causing delays in credits being applied after purchase. We are monitoring closely to ensure no further issues.
We are investigating delays in credit purchases being reflected in account balances, resulting in some requests failing for insufficient credit balance. We will provide an additional update as soon as possible.
Elevated errors on claude.ai, Claude Code, Claude Cowork and the Claude API
Sep 29, 2026 · Resolved Sep 29, 2026
The issue affecting Claude.ai, the Claude desktop and mobile apps, Claude Code, Claude Cowork, and the Claude API has been resolved, and services have been operating normally since recovery. Impact occurred from 07:00 PT / 14:00 UTC to 07:59 PT / 14:59 UTC.
All services have been operating normally since 14:59 UTC. We are continuing to monitor.
Most services have recovered as of 14:59 UTC. Signing in, starting new chats, voice conversations, Claude Code and Cowork sessions, purchases and file uploads are working again. Some messages sent between 14:00 and 14:59 UTC may not have been saved. We are monitoring closely and will post another update within 30 minutes.
The errors that began at 14:00 UTC were mitigated at 14:36 UTC, and existing conversations are mostly working again. A second issue is preventing many users from signing in (single sign-on and Sign in with Apple are unavailable), starting new chats, voice conversations and Claude Code or Cowork sessions, making purchases, and uploading files. If you're signed in, please don't sign out. We're working on a fix and will post another update within 30 minutes.
We have applied a mitigation and error rates have dropped substantially. Some sign-in attempts, account actions and Claude Code and Cowork sessions are still failing. We are continuing to work on a full fix.
+ 3 more updates
Elevated errors for multiple models
Sep 22, 2026 · Resolved Sep 22, 2026
This issue has been resolved. Impact occurred from 5:50pm PT / 00:50 UTC to 7:10pm PT / 02:10 UTC.
We have seen success rates return to normal across affected models, and are monitoring closely to ensure no further issues.
We are continuing to work to resolve errors affecting some models. At this time, requests to Claude Fable 5 and 5.1 and Mythos 5 and 5.1 have returned to normal success rates. We are working to resolve remaining errors affecting Claude Opus 5, and will provide an additional update shortly.
We have identified the cause of elevated errors on requests to Claude Mythos 5.1, Claude Fable 5.1, and Claude Opus 5 and are working on a fix. We will provide an update as soon as possible.
We are investigating elevated errors on requests to Claude Mythos 5.1, Claude Fable 5.1, and Claude Opus 5. We will provide an update as soon as possible.
Issues with Google Play subscriptions
Sep 16, 2026 · Resolved Sep 16, 2026
This issue has been resolved.
We are aware of an issue affecting users interacting with subscriptions via Google Play, such as when creating a new subscription on Android devices. Google has confirmed an issue with Google Play, and we are awaiting their further updates.
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.ai, Claude Cowork, and Claude Code. 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 22 models across 1 mode (22 chat)