SafetyPublished All news from that day
Anthropic's status page logs two Claude incidents of elevated errors on 13 November
The first ran from 09:58 to 11:58 UTC and the second from 13:09 to 15:38 UTC; Anthropic says the connector fault came from a Microsoft 365 service incident.
Check our sources · 8 facts from 3 sourcesClaude was degraded twice on 13 November, according to Anthropic's own status page. A sign-in problem hit claude.ai, Claude Code and platform.claude.com from 09:58 UTC until 11:58 UTC, and a second incident hit claude.ai, the API and Claude Code from 13:09 UTC until 15:38 UTC.
The second incident reached connectors, Claude in Meetings, Managed Agents and Claude Security as well. Anthropic's 15:33 UTC update said scheduled tasks and routines had run more than two hours late, with some runs skipped.
Separately, the Microsoft 365 connector, which handles mail, calendar, SharePoint and Teams chat, had been failing since 17:52 UTC on 12 November. Anthropic's status page says the cause was a Microsoft 365 service incident, and by 15:40 UTC on 13 November it reported signs of recovery with the Microsoft incident still open.
Underlined sentences link to the facts we checked. Dotted words open a short explainer.
Fact 5 of 8 · from Anthropic (Claude status), 13 Nov 2026
Adding a new connector on claude.ai is temporarily unavailable. Scheduled tasks and routines can run more than two hours late and some runs have been skipped (15:33 UTC)
Your reaction
We count reactions per story and day, never who reacted. The counts help us choose what goes in the monthly issue. If you are signed in, your own page shows yours too.
We count reactions per story and day, never who reacted. They help choose what goes in the monthly issue.
Check our sources
Every sentence above is checked against these 3 sources.
1 Elevated errors on claude.ai, Claude Code, and platform.claude.com
Open the source archived copy-
Anthropic's status page lists an incident titled "Elevated errors on claude.ai, Claude Code, and platform.claude.com", opened at 09:58 UTC on 13 November 2026 as "an issue with users authenticating to Claude.ai and Claude Code"
citeWe are investigating an issue with users authenticating to Claude.ai and Claude Code.
-
Anthropic's status page marks that incident resolved at 11:58 UTC on 13 November 2026, with a fix reported deployed at 11:05 UTC
citeA fix has been deployed for the issue affecting Claude services and we are monitoring for recovery. (11:05 UTC) / The issue affecting claude.ai and Claude Cowork has been resolved. (11:58 UTC, 13 Nov 2026)
2 Elevated errors on claude.ai, the Claude API, and Claude Code
Open the source archived copy-
Anthropic's status page lists a second incident, "Elevated errors on claude.ai, the Claude API, and Claude Code", opened at 13:09 UTC on 13 November 2026 and marked resolved at 15:38 UTC
citeWe are investigating reports of degraded performance affecting claude.ai, the Claude API, and Claude Code. (13:09 UTC) / The issue affecting multiple surfaces has been resolved. (15:38 UTC)
-
Anthropic's status page says the second incident widened to connectors including Claude Docs and Claude Sheets, Claude in Meetings, Claude Managed Agents and Claude Security, and the mobile apps
citeConnectors, including Docs and Sheets, remain degraded, as do Claude in Meetings, Claude Managed Agents, Claude Security and connector use in Claude Code. Mobile apps are affected in the same way as claude.ai. (14:36 UTC)
-
Anthropic's 15:33 UTC update on the second incident said scheduled tasks and routines were more than two hours late with some runs skipped, and that adding new connectors on claude.ai was temporarily unavailable
citeAdding a new connector on claude.ai is temporarily unavailable. Scheduled tasks and routines can run more than two hours late and some runs have been skipped (15:33 UTC)
3 Elevated errors affecting the Microsoft 365 connector
Open the source archived copy-
Anthropic's status page lists an incident "Elevated errors affecting the Microsoft 365 connector", opened at 17:52 UTC on 12 November 2026, saying requests to mail, SharePoint, Teams chat and calendar may fail
citeWe are investigating elevated errors and slow responses affecting the Microsoft 365 connector. (17:52 UTC, 12 Nov; mail, SharePoint, Teams chat and calendar requests may fail)
-
Anthropic's status page said at 22:23 UTC on 12 November that the Microsoft 365 connector issue "is caused by a Microsoft 365 service incident" and pointed to Microsoft's status page
citeThis issue is caused by a Microsoft 365 service incident. (22:23 UTC, 12 Nov)
-
Anthropic's status page reported at 15:40 UTC on 13 November 2026 signs of recovery for the Microsoft 365 connector and Claude for Outlook, with Microsoft's incident still open and some SharePoint search requests still failing; the incident was not marked resolved
citeWe're seeing signs of recovery for the Microsoft 365 connector. (15:40 UTC, 13 Nov; Microsoft incident still open, some SharePoint search requests still erroring; not resolved)
Every sentence above is checked against these 3 sources. Each fact has its own address you can cite.
Source 1 · Anthropic (Claude status) · 13 Nov 2026
Elevated errors on claude.ai, Claude Code, and platform.claude.com
Anthropic's status page lists an incident titled "Elevated errors on claude.ai, Claude Code, and platform.claude.com", opened at 09:58 UTC on 13 November 2026 as "an issue with users authenticating to Claude.ai and Claude Code"
We are investigating an issue with users authenticating to Claude.ai and Claude Code.
Anthropic's status page marks that incident resolved at 11:58 UTC on 13 November 2026, with a fix reported deployed at 11:05 UTC
A fix has been deployed for the issue affecting Claude services and we are monitoring for recovery. (11:05 UTC) / The issue affecting claude.ai and Claude Cowork has been resolved. (11:58 UTC, 13 Nov 2026)
Source 2 · Anthropic (Claude status) · 13 Nov 2026
Elevated errors on claude.ai, the Claude API, and Claude Code
Anthropic's status page lists a second incident, "Elevated errors on claude.ai, the Claude API, and Claude Code", opened at 13:09 UTC on 13 November 2026 and marked resolved at 15:38 UTC
We are investigating reports of degraded performance affecting claude.ai, the Claude API, and Claude Code. (13:09 UTC) / The issue affecting multiple surfaces has been resolved. (15:38 UTC)
Anthropic's status page says the second incident widened to connectors including Claude Docs and Claude Sheets, Claude in Meetings, Claude Managed Agents and Claude Security, and the mobile apps
Connectors, including Docs and Sheets, remain degraded, as do Claude in Meetings, Claude Managed Agents, Claude Security and connector use in Claude Code. Mobile apps are affected in the same way as claude.ai. (14:36 UTC)
Anthropic's 15:33 UTC update on the second incident said scheduled tasks and routines were more than two hours late with some runs skipped, and that adding new connectors on claude.ai was temporarily unavailable
Adding a new connector on claude.ai is temporarily unavailable. Scheduled tasks and routines can run more than two hours late and some runs have been skipped (15:33 UTC)
Source 3 · Anthropic (Claude status) · 12 Nov 2026
Elevated errors affecting the Microsoft 365 connector
Anthropic's status page lists an incident "Elevated errors affecting the Microsoft 365 connector", opened at 17:52 UTC on 12 November 2026, saying requests to mail, SharePoint, Teams chat and calendar may fail
We are investigating elevated errors and slow responses affecting the Microsoft 365 connector. (17:52 UTC, 12 Nov; mail, SharePoint, Teams chat and calendar requests may fail)
Anthropic's status page said at 22:23 UTC on 12 November that the Microsoft 365 connector issue "is caused by a Microsoft 365 service incident" and pointed to Microsoft's status page
This issue is caused by a Microsoft 365 service incident. (22:23 UTC, 12 Nov)
Anthropic's status page reported at 15:40 UTC on 13 November 2026 signs of recovery for the Microsoft 365 connector and Claude for Outlook, with Microsoft's incident still open and some SharePoint search requests still failing; the incident was not marked resolved
We're seeing signs of recovery for the Microsoft 365 connector. (15:40 UTC, 13 Nov; Microsoft incident still open, some SharePoint search requests still erroring; not resolved)
Topics
The morning email
On the mornings we publish: the three top stories and up to four short ones. Free.
We email you a link to confirm. An issue may include one sponsor, always labelled Sponsored · Advertisement. Our emails count opens and clicks, not who made them. Unsubscribe in one click. What we keep