---
type: "post"
id: "anthropic-status-page-major-incident-claude-unable-to-138dbc"
slug: "anthropic-status-page-major-incident-claude-unable-to-138dbc"
title: "Anthropic status page: major incident — Claude unable to join meetings"
description: "Anthropic says Claude Meetings (beta) may fail to join new calls, whether users add Claude manually or rely on Auto-join, which is paused."
retrieval_nugget: "Anthropic says Claude Meetings (beta) may fail to join new calls, whether users add Claude manually or rely on Auto-join, which is paused. Calls already in progress and other Claude features are unaffected. Teams testing meeting workflows should retain a human fallback for live participation."
published_at: "2026-11-16"
updated_at: "2026-11-16"
record_date: "2026-11-16"
date_kind: "published_at"
topics: ["claude","anthropic"]
entities: ["Anthropic","Claude Meetings","Claude","claude.ai"]
related_patterns: []
novelty_label: "new_fact"
what_changed: "Claude Meetings beta users may be unable to join new calls; Auto-join is paused, while ongoing calls and other Claude features are unaffected."
prior_refs: []
source_url: "https://status.claude.com/incidents/b5cq662qf2wm"
source_urls: ["https://status.claude.com/incidents/b5cq662qf2wm"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:anthropic-status-page-major-incident-claude-unable-to-138dbc"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/anthropic-status-page-major-incident-claude-unable-to-138dbc/","markdown":"https://newruntime.com/posts/anthropic-status-page-major-incident-claude-unable-to-138dbc.md","json":"https://newruntime.com/posts/anthropic-status-page-major-incident-claude-unable-to-138dbc.json"}
markdown_url: "https://newruntime.com/posts/anthropic-status-page-major-incident-claude-unable-to-138dbc.md"
---

# Anthropic status page: major incident — Claude unable to join meetings

## Retrieval answer

Anthropic says Claude Meetings (beta) may fail to join new calls, whether users add Claude manually or rely on Auto-join, which is paused. Calls already in progress and other Claude features are unaffected. Teams testing meeting workflows should retain a human fallback for live participation.

## Summary
Anthropic says Claude Meetings (beta) may fail to join new calls, whether users add Claude manually or rely on Auto-join, which is paused. Calls already in progress and other Claude features are unaffected. Teams testing meeting workflows should retain a human fallback for live participation.

## What happened
Anthropic’s Claude Status page reported an issue preventing Claude from joining new calls in Claude Meetings (beta). The incident affects claude.ai. The first investigation notice was posted on Nov. 16, 2026, at 15:10 UTC. Anthropic said calls already in progress were not affected and that core functionality was not impacted.

The notice defines the affected action narrowly: starting a new call with Claude as a participant. It does not describe a failure of a call that Claude had already joined. It also separates the meeting feature from the rest of Claude, saying that core functionality was not affected. For a user, that makes this a workflow-specific availability problem rather than a notice that every Claude surface is unavailable.

At 15:12 UTC, Anthropic said it was continuing to investigate an issue preventing Claude from joining new calls in Claude Meetings (beta). At 16:27 UTC, the company added a more specific operational change: it had temporarily paused Auto-join while it worked on the problem. The same update said that adding Claude to a call by hand was also affected. Calls already underway remained unaffected.

That distinction matters because Auto-join and manual addition are the two routes the status page identifies for getting Claude into a new meeting. Pausing the automated route does not create a reliable manual workaround; Anthropic explicitly says manual addition is affected too. The status page does not offer a configuration change, retry procedure, or alternative joining method for users to apply while the incident remains open.

In its latest update, posted at 18:10 UTC, Anthropic said Claude might still be unable to join some calls in Claude Meetings (beta), and that Auto-join remained paused. It expected the problem to take some time to fully resolve and said it would post another update when the status changed. The page continues to say that calls already in progress and other Claude features are not affected.

The report therefore describes a failure at the boundary where Claude enters a newly created or newly joined meeting. It does not say that meeting participation already underway was interrupted, that the Claude API was impaired, or that Claude Code was affected. It also does not state a cause, a restoration deadline, or an estimate of how many attempted joins have failed.

## What the archive adds
New Runtime’s earlier coverage on Oct. 24 described a separate Claude service disruption affecting Claude Fable 5 and 5.1 across the API, claude.ai, and Claude Code for about 35 minutes ([earlier coverage](https://newruntime.com/posts/claude-api-claude-ai-and-claude-code-saw-00966e/)). This is a new incident with a different stated scope: the current notice concerns entry into new Claude Meetings beta calls.

## Trend signal
This does not yet fit a pattern New Runtime tracks. The notice records a bounded service disruption, rather than a demonstrated shift in meeting interfaces, agent architecture, or the way model outputs are delivered.

## Why now
The incident remains operationally relevant because Anthropic’s latest update on Nov. 16, 2026 says some Claude Meetings joins may still fail and that Auto-join is still paused. The same-day sequence moved from investigation to a temporary pause of the automated joining route, without a stated restoration time.

## Connections to other events
The Oct. 24 disruption covered a broader set of Claude surfaces, including the API and Claude Code, while this one is confined by Anthropic’s description to new joins in Claude Meetings beta. Together, the two notices show why teams should distinguish the availability of a specific workflow from the availability of Claude generally.

## Why it matters
A meeting assistant is useful only if it can reliably enter the call at the required time. For a team evaluating Claude Meetings, a failed join can stop the workflow before any meeting assistance, capture, summarization, or follow-up can begin. Anthropic’s update sets a practical boundary: existing calls remain unaffected, but new-call attendance is unreliable and Auto-join is disabled.

That boundary should change immediate operating assumptions, not trigger a blanket pause on Claude. Teams need not infer that all Claude functionality is down. But they should not make an important new meeting dependent on Claude joining until Anthropic changes the incident status. A human participant who can take notes, or another already-tested capture process, remains necessary when the meeting cannot be missed.

The incident also demonstrates a design requirement for any workflow that relies on an assistant entering a live event. The important failure mode is not only whether the assistant can produce useful output after it arrives; it is whether the join itself can be verified before the event becomes irrecoverable. For meetings, that verification must happen before discussion begins, not afterward.

## Limits and uncertainty
Anthropic has not stated the cause, the number of affected users or calls, or a restoration time. It says the issue may persist for some calls and that full resolution will take time, but does not quantify reliability or identify particular meeting providers, account types, or configurations that are more affected. The status page does not say when the first failed join occurred or whether the issue is geographically concentrated. Its scope and operational claims have not been independently checked.

## Skill to build now
For any important meeting workflow, add a preflight ownership step this week: confirm that the assistant has joined before the meeting starts, and name a human owner for notes if it has not. Use that fallback when the assistant’s entry is essential to capture the discussion. This is particularly useful for beta features and automated joins, where a workflow can fail before downstream prompts, summaries, or automations have a chance to run.

## Reader takeaway
Treat Claude Meetings’ new-call joining as unavailable for now: Auto-join is paused, and manual addition can fail too. Anthropic says calls already in progress and other Claude features are unaffected. Keep a human fallback for meetings that cannot be missed, and watch the status page for a resolution update.

## Open question
When Anthropic resolves the incident, will it identify the cause and clarify whether the failure was tied to a particular meeting provider, configuration, or joining path?

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Claude](https://newruntime.com/topics/claude.md): Explore the claude topic hub.
- topic hub: [Anthropic](https://newruntime.com/topics/anthropic.md): Explore the anthropic topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)
