Live

Elevated errors on claude.ai, Claude Code, Claude Cowork and the Claude API

The issue affecting Claude.ai, the Claude desktop and mobile apps, Claude Code, Claude Cowork, and the Claude API has been resolved, and services have been operating normally since recovery. Impact occurred from 07:00 PT / 14:00 UTC to 07:59 PT / 14:59 UTC.

The latest update from Anthropic.

State

Resolved

Started

33 d ago

2026-09-29 14:21 UTC

Lasted

2 h 6 min

until 2026-09-29 16:27 UTC

Worst impact

Partial outage

Timeline

8 updates
14:2114:5315:2415:5516:27
Partial outageUpdate postedTimes in UTC

Investigating

50 min 40%

Monitoring

1 h 16 min 60%

Updates

Times in UTC

As posted by Anthropic

Resolved2026-09-29 16:27 UTC

The issue affecting Claude.ai, the Claude desktop and mobile apps, Claude Code, Claude Cowork, and the Claude API has been resolved, and services have been operating normally since recovery. Impact occurred from 07:00 PT / 14:00 UTC to 07:59 PT / 14:59 UTC.

Monitoring2026-09-29 15:30 UTC

All services have been operating normally since 14:59 UTC. We are continuing to monitor.

Monitoring2026-09-29 15:11 UTC

Most services have recovered as of 14:59 UTC. Signing in, starting new chats, voice conversations, Claude Code and Cowork sessions, purchases and file uploads are working again. Some messages sent between 14:00 and 14:59 UTC may not have been saved. We are monitoring closely and will post another update within 30 minutes.

Investigating2026-09-29 15:00 UTC

The errors that began at 14:00 UTC were mitigated at 14:36 UTC, and existing conversations are mostly working again. A second issue is preventing many users from signing in (single sign-on and Sign in with Apple are unavailable), starting new chats, voice conversations and Claude Code or Cowork sessions, making purchases, and uploading files. If you're signed in, please don't sign out. We're working on a fix and will post another update within 30 minutes.

Investigating2026-09-29 14:41 UTC

We have applied a mitigation and error rates have dropped substantially. Some sign-in attempts, account actions and Claude Code and Cowork sessions are still failing. We are continuing to work on a full fix.

Investigating2026-09-29 14:30 UTC

We are investigating reports of degraded performance affecting claude.ai, platform.claude.com, the Claude API, Claude Code, and Claude Cowork. We will provide an update as soon as possible.

Investigating2026-09-29 14:28 UTC

We are investigating elevated error rates affecting Claude.ai (including the desktop and mobile apps), Claude Code and Claude Cowork. Some requests to the Claude API are also returning errors. We will provide an update as soon as possible.

Investigating2026-09-29 14:21 UTC

We are investigating elevated error rates affecting Claude.ai (including the desktop and mobile apps), Claude Code and Claude Cowork. Users may see failed requests, errors loading or sending conversations, or be asked to sign in again; retrying may succeed. We will provide an update as soon as possible.

Affected components

5
claude.aiClaude Console (platform.claude.com)Claude API (api.anthropic.com)Claude CodeClaude Cowork

Anthropic in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

50

Days with an incident

42

Median duration

1 h 8 min

This incident

1.9× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 days
median 1 h 8 min
90 days agoToday

Other Anthropic incidents

All incidents

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.

Prompt
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.cc/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.

RSS
https://outages.cc/feed.xml?providers=anthropic
Slack
/feed subscribe https://outages.cc/feed.xml?providers=anthropic

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane