Was the Claude API down during the 13 November login outage?

The Claude API was not listed as affected during the morning login incident on 13 November 2026, when claude.ai showed a major outage and Claude Code and the Console showed partial outages. The API was affected in the second incident, which Anthropic opened at 13:09 UTC for elevated errors on claude.ai, the Claude API and Claude Code.

Did Claude scheduled tasks run during the outage?

Anthropic's status update at 15:33 UTC on 13 November said Claude scheduled tasks ran more than two hours late during the afternoon incident and that some were skipped. Adding new connectors was also temporarily unavailable. Users who depend on scheduled Claude runs should check which ones did not happen and start them again by hand.

What caused the 13 November Claude outage?

Anthropic has not published a root cause for either 13 November Claude incident. Its status page only says a fix was deployed at 11:05 UTC for the login problem and that error levels returned to normal at 15:33 UTC for the second incident. The separate Microsoft 365 connector failure was caused by a Microsoft 365 service incident.

Is the Claude outage related to the Microsoft 365 outage?

The Microsoft 365 connector incident was a separate Claude status entry. It ran from 16:03 UTC on 12 November to 16:40 UTC on 13 November and broke mail, calendar and search requests, plus Claude for Outlook, because of a Microsoft 365 service incident. Anthropic did not link the two 13 November Claude incidents to that Microsoft failure.

Anthropic · 2026-11-13 · major

Claude outage — login failures, then API errors hit claude.ai and Claude Code

In short

Claude had two outages on 13 November. Logins to claude.ai and Claude Code failed from 09:58 to 11:58 UTC. From 13:09 to 15:38 UTC, claude.ai, the Claude API, Claude Code and connectors returned elevated errors.

Anthropic · 2026-11-13 · 3 sources checked

Anthropic image used by Business Today in its report on the Claude login outage — Business Today

Two back-to-back Claude incidents on 13 November locked users out, then broke the API and connectors.

Quick facts

Date	13 November 2026
Login incident	09:58–11:58 UTC
Error incident	13:09–15:38 UTC
Affected	claude.ai, Claude Code, Console, API, connectors
Root cause	Not published
HN discussion	480+ points

What is it?

Anthropic's status page logged two separate Claude incidents on 13 November 2026. The first, at 09:58 UTC, stopped users from signing in to claude.ai and Claude Code. The second, at 13:09 UTC, brought elevated errors to claude.ai, the Claude API and Claude Code.

How does it work?

During the login incident, claude.ai was marked as a major outage, while Claude Code and the Console (platform.claude.com) had partial outages; the API stayed up. A fix went out at 11:05 UTC. In the afternoon incident the errors spread to connectors such as Docs and Sheets, Claude Security and Managed Agents before error levels returned to normal at 15:33 UTC.

Why does it matter?

Teams that run coding agents and scheduled jobs on Claude lost about four and a half hours of service in one day. Anthropic says scheduled tasks ran more than two hours late and some were skipped, so anyone who relies on them should check that their runs happened. The incidents came on top of a separate Microsoft 365 connector failure from 12 to 13 November.

Who is it for?

teams that depend on Claude, Claude Code or the Claude API

Frequently asked questions

Was the Claude API down during the 13 November login outage?: The Claude API was not listed as affected during the morning login incident on 13 November 2026, when claude.ai showed a major outage and Claude Code and the Console showed partial outages. The API was affected in the second incident, which Anthropic opened at 13:09 UTC for elevated errors on claude.ai, the Claude API and Claude Code.
Did Claude scheduled tasks run during the outage?: Anthropic's status update at 15:33 UTC on 13 November said Claude scheduled tasks ran more than two hours late during the afternoon incident and that some were skipped. Adding new connectors was also temporarily unavailable. Users who depend on scheduled Claude runs should check which ones did not happen and start them again by hand.
What caused the 13 November Claude outage?: Anthropic has not published a root cause for either 13 November Claude incident. Its status page only says a fix was deployed at 11:05 UTC for the login problem and that error levels returned to normal at 15:33 UTC for the second incident. The separate Microsoft 365 connector failure was caused by a Microsoft 365 service incident.
Is the Claude outage related to the Microsoft 365 outage?: The Microsoft 365 connector incident was a separate Claude status entry. It ran from 16:03 UTC on 12 November to 16:40 UTC on 13 November and broke mail, calendar and search requests, plus Claude for Outlook, because of a Microsoft 365 service incident. Anthropic did not link the two 13 November Claude incidents to that Microsoft failure.

Try it

https://status.claude.com/history