Claude failed twice on Friday, November 13 — a two-hour sign-in outage in the morning, then a wider afternoon outage that reached the Claude API and Anthropic’s agent products. Anthropic has marked both incidents resolved and has given no cause for either one.
November 13, 2026 — For teams that start their workday inside Claude, Friday was a rough one. Anthropic’s status page logged two separate incidents in a single day, and the second was the kind that breaks other companies’ products, not just a chat window.
What happened in the morning: a sign-in failure
The first incident opened at 09:58 UTC (4:58 a.m. ET), when Anthropic said it was investigating an issue with users authenticating to Claude.ai and Claude Code. The status page listed four affected services: Claude.ai on web and in the apps, Claude Code, Claude Cowork, and the Claude Console at platform.claude.com. The Claude API itself was not on the list, so apps built on Claude kept working. Anthropic said a fix had been deployed at 11:05 UTC and marked the incident resolved at 11:58 UTC — about two hours after it began. The company has not said how many users were affected or what went wrong.
The afternoon outage was the bigger one
A second incident opened at 13:09 UTC (8:09 a.m. ET) as degraded performance on Claude.ai, the Claude API, and Claude Code. By 14:03 UTC the affected list had grown to include connectors, Claude Security, and Claude Managed Agents. At 14:36 UTC Anthropic reported recovery on Claude.ai and the API, though it warned errors might return, while connectors, Claude in Meetings, Managed Agents, and Claude Security stayed degraded. A 15:33 UTC update added a detail builders will care about: scheduled tasks and routines could run more than two hours late, and some runs had been skipped, while adding a new connector was temporarily unavailable. The incident was marked resolved at 15:38 UTC, roughly two and a half hours after it opened.
Was this the Microsoft outage? Anthropic hasn’t said so
Friday’s failures landed while Microsoft’s global Microsoft 365 outage, which began Thursday, was still disrupting Outlook and Teams — and some coverage linked the two. Anthropic has not made that connection for either Friday incident, and neither status-page entry gives a cause. There is one separate, genuinely Microsoft-linked problem on Anthropic’s board: an incident open since 17:52 UTC on Thursday for Claude’s Microsoft 365 connector, which Anthropic attributes to the Microsoft 365 service incident. That connector issue is distinct from Friday’s two outages.
Why it matters
A sign-in failure is annoying; an API and agents outage is expensive. The morning incident locked people out of a tool many now work in all day. The afternoon one hit the layer other products are built on — the paid API, Managed Agents, and scheduled routines that either ran hours late or did not run at all. Anthropic has published no post-incident report for either failure, so customers still do not know what broke twice in one day. For subscribers, the practical takeaway is the boring one: when Claude misbehaves, check the status page before you troubleshoot your own account — and during an authentication incident, staying signed in beats signing out and hoping.
Frequently asked questions
Was the Claude API down on November 13?
Not in the morning — the first incident was an authentication failure and the API was not listed as affected. In the afternoon, yes: the API was degraded from 13:09 UTC until the incident was resolved at 15:38 UTC.
How long did the Claude outages last?
About two hours for the morning sign-in incident (09:58–11:58 UTC) and about two and a half hours for the afternoon incident (13:09–15:38 UTC).
Did Microsoft’s outage cause Claude to go down?
Anthropic has not said that. The only Claude problem Anthropic attributes to Microsoft is a separate Microsoft 365 connector incident that began on November 12; neither of Friday’s outages carries a stated cause.
Sources: Anthropic status page (both November 13 incidents and the Microsoft 365 connector incident), as reported by Agenccy and MadRobot; Jagran Josh; Men’s Journal.