Anthropic's status incident reports elevated errors across claude.ai, Claude Code, Cowork and the API from 14:00 UTC Sep 29 with most services recovered by 14:59 UTC, while users simultaneously hit 'at capacity' errors the status page first showed as clear — the incident's closure and root-cause disclosure settle whether this was a contained blip or a recurring capacity strain behind Claude workflows.

state: resolvedheat: lowuncertainty: lowconvergesscott: mediumanthropic ai-infrastructure service-reliabilityAnthropic

What is this?

Anthropic operates the Claude product line — claude.ai, the developer API, the Claude Code coding agent, and Claude Cowork — and reports incidents on a public status page, with Claude Console and Claude for Government typically listed as unaffected. The supplied coverage establishes a pattern rather than this specific event: repeated elevated-error and partial-outage incidents across all four surfaces through 2026 (a streak spanning Aug 5–24 marked by '529 Overloaded' and 'unexpected capacity constraints' errors, an ~80-minute multi-model incident in late September, and similar April events), with Anthropic consistently not naming root causes or publishing postmortems; one industry tracker counted the Aug 5 incident as the company's 164th disruption of the year, and coverage links the strain to demand outpacing compute despite a disclosed ~$71B compute investment push. However, none of the snippets corroborate the case's specific Sep 29 incident (14:00 UTC start, recovery by 14:59 UTC) or the reported 'at capacity' errors while the status page showed clear — the coverage describes other incidents — so whether this particular episode was a contained blip versus part of the recurring capacity strain remains unsettled on this material, though the documented recurrence pattern and capacity-flavored error messaging lend weight to the latter reading.

Why it matters to Scott

Continues the tracked deterioration of Scott's primary coding-agent dependency — July ECONNRESET spike, Aug 16 full-surface outage, Sep 14 usage-limit cut, now another all-surfaces blip — delivering fresh dated receipts for the single-vendor fragility his vendor-lock-in doctrine and LiteLLM multi-provider routing are built to hedge. The status-page-clear-while-users-hit-'at-capacity' detail is also a live instance of the gap his external Uptime.com monitoring exists to catch, and the closure's root-cause handling (another silent closure vs a real postmortem) settles the capacity-strain question the radar's Anthropic compute-deal thread is circling.

dev:technology.claude-codedev:technology.anthropicdev:technology.litellmip:concept.vendor-lock-indev:technology.uptime-comradar:anthropic-claude-aug-2026-outageradar:openai-codex-full-outageradar:claude-code-usage-limit-cutradar:claude-code-econnreset-spikeradar:frontier-labs-small-capacity-dealsradar:concept.claude-code

queries asked of Scott's wikis

coding agent outage fallback multi-provider routing
Claude Code retry backoff harness degraded mode handling
Anthropic capacity constraints compute economics notes
single-vendor dependency risk in agent workflows
local model fallback when frontier API is down
status page monitoring automation dev project

Measured heat

no measured readings yet — the hourly heat pass fills this in

How the heat travelled

09-28 14:00	⭐ origin echo-reconstructed	Anthropic's official incident report, titled "Elevated errors on claude.ai, Claude Code, Claude Cowork and the Claude API". First update (Se Anthropic (Claude status page) on other (echo) · attributed from hn.story.49893876, hn.story.49893877	—
09-29 14:21	first on r/ClaudeAI · published · +24.4h	Discussion Hub for new Claude incident: Elevated errors on claude.ai, Claude Code and Claude Cowork on Sep 29, 2026 ClaudeAI-mod-bot	—
09-29 14:25	first on hacker news · published · +24.4h	Claude partial outage sidcool	—
09-29 14:21	amplified on r/ClaudeAI	reddit.post.1wtbgj0 ClaudeAI-mod-bot	peak 65 · 72 comments · 19% of case engagement
09-29 14:25	amplified on hacker news 👑	hn.story.49893876 sidcool	peak 166 · 142 comments · 78% of case engagement
09-29 14:25	amplified on hacker news	hn.story.49893877 throw03172019	peak 12 · 2 comments · 4% of case engagement
09-29 15:20	our radar first saw it · +25.4h	discovery anchor: hn.story.49893876	—

Evidence (4) — ⭐ canonical anchor

source	object	author	score	comments
🟧 hn	Claude partial outage Retrieved article excerpt Open article · Retrieved 2026-09-29T15:28:45.356432+00:00 # Elevated errors on claude.ai, Claude Code, Claude Cowork and the Claude API Incident Report for [Claude](https://status.claude.com/) [Subscribe to Updates](https://status.claude.com/incidents/4xvtc2gnq73l#subscribe-modal-4xvtc2gnq73l) ## Monitoring 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. Posted 17 minutes ago. Sep 29, 2026 - 15:11 UTC ## Update 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. Posted 28 minutes ago. Sep 29, 2026 - 15:00 UTC ## Update 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. Posted 48 minutes ago. Sep 29, 2026 - 14:41 UTC ## Update 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. Posted 58 minutes ago. Sep 29, 2026 - 14:30 UTC ## Update 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. Posted 1 hour ago. Sep 29, 2026 - 14:28 UTC ## Investigating 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. Posted 1 hour ago. Sep 29, 2026 - 14:21 UTC This incident affects: claude.ai, Claude Console (platform.claude.com), Claude API (api.anthropic.com), Claude Code, and Claude Cowork. [← Current Status](https://status.claude.com/) [Powered by Atlassian Statuspage](https://www.atlassian.com/software/statuspage?utm_campaign=status.claude.com&utm_content=SP-notifications&utm_medium=powered-by&utm_source=inapp)	sidcool	169	143
🟧 hn	Claude Is "At Capacity"	throw03172019	12	3
🟧 echo.other ⭐	Anthropic's official incident report, titled "Elevated errors on claude.ai, Claude Code, Claude Cowork and the Claude API". First update (Se	Anthropic (Claude status page)	—	—
🟠 reddit	Discussion Hub for new Claude incident: Elevated errors on claude.ai, Claude Code and Claude Cowork on Sep 29, 2026 ClaudeAI	ClaudeAI-mod-bot	70	72

Interpretation history

2026-09-29T23:04:50Z
The episode settled: officially resolved 16:27 UTC after a bounded 59-minute all-surface outage with no root-cause disclosure — another silent closure extending Anthropic's documented 2026 no-postmortem pattern — and the incident's anatomy (SSO/Sign-in-with-Apple failures, unsaved messages, 'at capacity' as a session-error surface) reads as an auth/application-layer fault rather than compute exhaustion, weakening the capacity-strain reading for this specific event. The recurrence question stays with the open sibling pattern threads; this case is done.
2026-09-29T20:53:11Z
evidence attached: reddit.post.1wtbgj0 — Independent community hub (65 points, 72 comments) corroborating the incident's spread and user impact including unsaved messages — key spread evidence for re-judging closure vs recurring capacity strain.
2026-09-29T16:04:30Z
origin walked (opencode/cheap-glm, conf 0.95): anchor hn.story.49893876 -> echo.other.c51de47a49 by Anthropic (Claude status page)
2026-09-29T15:49:28Z
grounded: converges/medium — Continues the tracked deterioration of Scott's primary coding-agent dependency — July ECONNRESET spike, Aug 16 full-surface outage, Sep 14 usage-limit cut, now
2026-09-29T15:40:30Z
case created — A first-party incident touching every Claude surface on Scott's primary coding-agent provider, with a contradicting in-batch user report, is a bounded availability episode that parallels the precedent Codex outage case.

Decision trace

09-30 09:04resolveThe episode settled: officially resolved 16:27 UTC after a bounded 59-minute all-surface outage with no root-cause disclosure — another silent closure extending Anthropic's documented 2026 no-pos
09-30 06:53attachIndependent community hub (65 points, 72 comments) corroborating the incident's spread and user impact including unsaved messages — key spread evidence for re-judging closure vs recurring capacit
09-30 06:36propose_attachIndependent community hub (65 points, 72 comments) corroborating the incident's spread and user impact including unsaved messages — key spread evidence for re-judging closure vs recurring capacit
09-30 06:23sensor_dirtyvelocity_spike
09-30 03:24sensor_dirtycomment_update
09-30 02:04promote_anchororigin walk conf 0.95
09-30 01:49groundContinues the tracked deterioration of Scott's primary coding-agent dependency — July ECONNRESET spike, Aug 16 full-surface outage, Sep 14 usage-limit cut, now another all-surfaces blip — deliver
09-30 01:40createA first-party incident touching every Claude surface on Scott's primary coding-agent provider, with a contradicting in-batch user report, is a bounded availability episode that parallels the prec