Claude unable to join meetings
Anthropic reports that Claude cannot join new calls in Claude Meetings (beta) on claude.ai. Claude was unable to join many calls. Anthropic identified the issue and put mitigations in place. Claude Meetings is re-enabled for Enterprise customers. Adding Claude to new calls and Auto-join stay paused for Team customers.
State
Identified
Started
Ongoing for
19 h 40 min
Worst impact
Partial outage
Timeline
6 updatesInvestigating
10 h 53 min 55%
Identified
8 h 47 min 45%
Updates
Times in UTCAs posted by Anthropic
Claude Meetings (beta) saw higher than expected demand today, and Claude was unable to join many calls. We have put mitigations in place and are continuing to monitor and improve join reliability. Claude Meetings is now re-enabled for all Enterprise customers, though Claude may take a little longer than usual to join. Adding Claude to new calls and Auto-join remain paused for Team customers. We will share more updates as we expand capacity and begin restoring the feature for Team customers.
Claude may still be unable to join some calls in Claude Meetings (beta), and Auto-join remains paused. Calls already in progress and other Claude features are not affected. We expect this to take some time to fully resolve and will post an update when the status changes.
We have temporarily paused Auto-join while we work on this. Adding Claude to a call by hand is also affected. Calls already in progress are not affected. We will provide another update as soon as possible.
We are continuing to investigate an issue preventing Claude from joining new calls in Claude Meetings (beta). We have temporarily paused Auto-join while we work on this. Adding Claude to a call by hand is also affected. Calls already in progress are not affected. We will provide another update as soon as possible.
We are investigating reports of degraded performance affecting claude.ai. We will provide an update as soon as possible.
We are investigating an issue preventing Claude from joining new calls in Claude Meetings (beta). Calls already in progress are not affected, and core functionality is not impacted. We will provide an update as soon as possible.
Affected components
1Anthropic in the last 90 days
Full historyIncidents in 90 days
48
Days with an incident
41
Median duration
1 h 13 min
This incident
16× the median
Other Anthropic incidents
All incidentsAnthropic·Elevated errors for Claude Sonnet 5.5 and Claude Fable 5.2
Anthropic reports elevated errors for Claude Sonnet 5.5 and Claude Fable 5.2. The errors affected claude.ai, the Claude API, Claude Code, and Claude Cowork. The issue is resolved and lasted about 73 minutes.
Anthropic·Some users unable to sign up with Apple on the Claude iOS app
Sign in with Apple does not work on the Claude iOS app. The problem mainly affects new accounts on claude.ai. Anthropic reports that the issue is resolved. The outage lasted from 00:29 UTC on November 14 to 18:31 UTC on November 16.
Anthropic·Elevated purchasing errors on claude.ai
Anthropic reports errors on purchases, plan upgrades and cancellations on claude.ai. The issue is resolved. It lasted about 89 minutes. Delayed plan changes and payments are applied. Anthropic says customers do not need to pay again.
Anthropic·Elevated errors on claude.ai, the Claude API, and Claude Code
On 13 November 2026, Anthropic reported elevated errors on claude.ai, the Claude API, Claude Code and Claude Cowork. Anthropic later reported normal error levels on claude.ai and the Claude API, and is monitoring. The incident lasted 2 hours and 30 minutes and is resolved.
Anthropic·Elevated errors on claude.ai, Claude Code, and platform.claude.com
Anthropic reported elevated errors on claude.ai, Claude Code, platform.claude.com, and Claude Cowork. Anthropic later confirmed the issue is resolved. The outage lasted about 120 minutes.
Follow Anthropic
Your coding agent knows when Anthropic is down, and tells you when a failure is theirs, not yours. You can also get Anthropic incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "anthropic" and tell me if Anthropic has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.live/feed.xml?providers=anthropic/feed subscribe https://outages.live/feed.xml?providers=anthropicFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane