Last updated: November 13, 2026, at 14:36 UTC. A widespread Claude outage is causing elevated errors across Claude.ai, the Claude API and Claude Code, according to Anthropic. The company says recovery is underway, but several products and connectors remain degraded. Users may encounter failed requests, unavailable conversations, login errors or tools that do not return expected results.
The disruption is not a single, fully resolved event. Anthropic reported authentication problems earlier in the day, marked that incident resolved at 11:58 UTC, and subsequently reported a separate service disruption affecting core Claude products. A Microsoft 365 connector problem that began on November 12 is also ongoing and has a different cause.
Is Claude Down Right Now? What Is Claude’s Current Status?
Yes, some Claude services are experiencing problems. Anthropic’s latest update at 14:36 UTC said elevated errors had affected Claude.ai, the API and Claude Code. Claude.ai and API availability were recovering, but that language indicates partial restoration rather than a complete resolution.
Mobile applications were affected in the same way as Claude.ai. That means changing from the website to the iOS or Android app may not help when the underlying Claude service is degraded.
Anthropic also reported continuing problems with a group of connected features, including Docs and Sheets connectors, Claude in Meetings, Managed Agents, Claude Security and connector use inside Claude Code. Users relying on those tools may continue to see failures even if ordinary chats begin working again.
The situation is changing, so the official Anthropic status page should be treated as the primary source for the latest Claude service status. An incident should not be considered fully resolved until Anthropic explicitly says so.
Which Claude Services Are Experiencing Problems?
The current Anthropic outage does not affect every component equally. At the time of the check, the status information could be summarized as follows:
- Claude.ai: Affected by elevated errors, with recovery underway.
- Claude mobile apps: Affected in the same way as Claude.ai.
- Claude API: Affected, although Anthropic reported that it was recovering.
- Claude Code: Affected by the broader incident; connector use remained degraded.
- Docs and Sheets connectors: Still degraded in Anthropic’s latest update.
- Claude in Meetings: Still degraded.
- Managed Agents and Claude Security: Still degraded.
- Microsoft 365 integrations: Experiencing a separate upstream Microsoft-related incident affecting mail, calendar and search functions.
- Claude Console: Listed as operational at the time of the check.
- Cloud-platform integrations: Several were listed as operational, although users should verify the component they use.
This component-level distinction matters. One user may be able to open the Claude Console while another cannot complete a request on Claude.ai. Likewise, a basic conversation may work while a prompt requiring Google Docs, Microsoft mail or another connector fails.
People searching for a Claude Cowork outage should also avoid assuming that every Claude product shares the same status. Check the relevant component and incident notes, especially when the workflow depends on connectors or managed tools.
Is Claude Code Down?
Claude Code is included in Anthropic’s report of elevated errors, so developers may see slow responses, failed operations or intermittent availability. The company specifically said connector use in Claude Code remained degraded at 14:36 UTC.
A Claude Code outage can therefore appear in more than one form. The core assistant may fail to answer, or Claude Code may respond while a connected service does not. If a task depends on external documents, repositories or enterprise data, isolate that dependency before concluding that the entire command-line tool is unavailable.
Avoid repeatedly launching the same agentic task during an incident. Duplicate submissions can create uncertainty about which operation succeeded and may consume resources once service returns.
Is the Claude API Working?
The Claude API was recovering as of the latest official update, but it was not yet appropriate to describe the incident as fully resolved. API customers may still experience elevated error rates, timeouts or intermittent request failures.
Developers should check the Claude API status before changing production code or rotating credentials. If Anthropic is reporting an active incident, an authentication or server error may be service-side rather than evidence of an application defect.
Use controlled retries with exponential backoff and observe normal rate-limit guidance. Do not send rapid, repeated requests, because doing so can amplify load and make application logs harder to interpret. For important workflows, preserve failed job details so they can be retried safely after recovery.
Why Is Claude Not Letting Users Log In?
Claude login problems were reported earlier on November 13. Anthropic opened an authentication incident at 09:58 UTC and marked that incident resolved at 11:58 UTC. That event should be distinguished from the later disruption affecting Claude.ai, the API and Claude Code.
This distinction explains why some users may have regained account access and then encountered a different error while submitting a prompt. An earlier Claude authentication error can be resolved even while a subsequent platform incident causes failed conversations or API calls.
If the official status page says authentication is operational, users can try signing out and back in, opening a private browser window, disabling an interfering extension or clearing site data. Before resetting a password, confirm that the problem is limited to the account rather than part of an active Anthropic outage. Enterprise users should also check whether their identity provider or single sign-on configuration is operating normally.
Is the Microsoft 365 Outage Affecting Claude?
Yes, but it is a separate incident from the November 13 core-service disruption. Anthropic reported a Microsoft 365 connector incident beginning November 12. It affects mail, calendar and search integrations, as well as Claude for Outlook.
Anthropic attributed that incident to an upstream Microsoft service problem. As a result, Claude may be available for ordinary chats while requests involving Microsoft 365 data fail, return incomplete results or cannot connect. Repeatedly reauthorizing the connector is unlikely to solve an upstream outage and could create unnecessary account confusion.
The Microsoft 365 issue should also not be conflated with problems involving Docs and Sheets, which Anthropic listed among the degraded features in the later Claude incident. Although both involve connectors, they have different dependencies and incident timelines.
Timeline of the November 13 Claude Outage
- 09:58 UTC: Anthropic reported authentication problems affecting access to Claude.
- 11:58 UTC: The earlier authentication incident was marked resolved.
- Later on November 13: Anthropic reported elevated errors affecting Claude.ai, the Claude API and Claude Code as a separate disruption.
- 14:36 UTC: Anthropic said Claude.ai and the API were recovering. Several connectors and related products remained degraded.
The Microsoft 365 connector incident predates this timeline, having begun on November 12. Keeping these events separate provides a more accurate explanation than describing every error as one uninterrupted outage.
How to Check Anthropic’s Official Status Page
The official status page is the best place to determine whether Claude AI is not working globally or whether the issue is local. Review both the overall component list and the incident updates, because the top-level display may not explain which feature is degraded.
- Check active incidents: Look for the newest timestamp and wording such as investigating, identified, monitoring, recovering or resolved.
- Find your component: Separate Claude.ai, the Claude API, Claude Code, authentication and connectors rather than treating Claude as one service.
- Match the error to the incident: A login loop suggests authentication, while an API timeout or failed connector points to a different layer.
- Wait briefly and retry once: Recovery can be gradual. Avoid submitting the same prompt or operation many times.
- Test local causes when systems are operational: Try another network or browser, disable extensions, inspect firewall settings and confirm that system time is correct.
Third-party reports such as Downdetector Claude submissions can reveal that many users are seeing trouble, but they do not replace Anthropic’s diagnosis. User-reporting sites may combine login, API, billing and connector complaints into one spike.
What Users and Developers Should Do Now
For routine work, save prompts and unfinished content outside Claude until service is stable. If a request fails, wait several minutes before trying again rather than repeatedly pressing submit. When a response is business-critical, verify that it completed fully before relying on it.
Developers should monitor error codes, pause nonessential batch jobs and retain idempotency safeguards where applicable. Do not make major configuration changes solely because of errors during a confirmed Claude outage. Once Anthropic reports resolution, test with a small request before restoring normal traffic.
There is no confirmed evidence in Anthropic’s updates that the disruption was caused by a cyberattack. The responsible approach is to describe the observed service failures and official recovery statements without assigning an unverified cause.
Frequently Asked Questions
Is Claude down for everyone?
Not necessarily. Claude.ai, the API and Claude Code experienced elevated errors, but availability may vary by region, account and feature. Claude Console and several cloud-platform integrations were listed as operational at the time checked.
Has Anthropic fully resolved the Claude outage?
No full resolution had been announced as of 14:36 UTC. Anthropic said Claude.ai and the API were recovering, while multiple connectors and related products remained degraded. Recovery does not mean every component is restored.
Why does Claude work until I use a connector?
The core model interaction and the connected data source are separate dependencies. Claude may answer a normal prompt while Docs, Sheets, Microsoft 365 or another connector remains degraded.
Should I reset my password if Claude will not let me log in?
First check the authentication component on the status page. If Anthropic reports an active login incident, wait before changing credentials. If authentication is operational, then test browser, network and identity-provider issues.
Where can I find independent coverage?
In addition to Anthropic’s updates, readers can review the Associated Press report for broader coverage. Official incident notices remain the authority for current component status.
Update note: This report reflects information available at 14:36 UTC on November 13, 2026, and should be updated when Anthropic changes the incident status.
