Operational Anthropic (Claude) status
anthropic.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
Anthropic (Claude) looks fine itself, but Amazon Web Services, a provider it may run on (inferred), reports major outage. Watch for knock-on effects.
confidence: low Vendor: operational · users: normal · routing: no data · upstream providers: major.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) Amazon Web Services: Major outage
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: claude.ai
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 4 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “Claude Meetings auto-join limited on the Team plan”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
- Amazon Web Services reports an issue. Anthropic (Claude) may depend on it (inferred from public sources). Coincidence, not causation. evidence confidence: low
What we don't know: what is happening inside Anthropic (Claude)'s own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp. Routing data shows reachability, not whether the app works.
Coincidence, not causation: signals that overlap in time are shown side by side, not as proof of cause.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data · upstream providers: major. Vendor status and outside signals roughly agree.
Who depends on whom
Anthropic (Claude) may run on Google Cloud, Amazon Web Services (inferred). We don't map other services that depend on Anthropic (Claude). Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Anthropic (Claude) or its upstream providers, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Anthropic (Claude). No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Claude Meetings auto-join limited on the Team plan
minor resolved · started · resolved
7 updates
- investigating
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.
- investigating
We are continuing to investigate an issue preventing Claude from joining new calls in Claude Meetings (beta).
- investigating
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.
- investigating
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.
- identified
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.
- identified
Claude Meetings (beta) is joining calls more reliably, and we are monitoring it. It remains enabled for all Enterprise customers. Team customers can again add Claude to new calls manually, and Auto-join is being restored gradually for Team customers.
- resolved
Claude Meetings (beta) is joining calls normally. Enterprise and Team customers can add Claude to calls. Auto-join is available for all Enterprise customers and some Team customers. We'll continue rolling out auto-join to additional Team customers in the coming days.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.