Case · 2026-09-29
Do not sign out: an hour when login was the outage
The official advice was stay where you are. Logging in had become a feature you might not get back.
Summary: On 29 Sep 2026 elevated errors hit claude.ai (web, desktop, mobile), Claude Code, Claude Cowork, the console, and the API from 14:00 to 14:59 UTC. A second issue blocked sign-in, including SSO and Sign in with Apple, plus new chats, voice, purchases, and uploads. Some messages sent in that hour may not have been saved.
Source: status.claude.com · 29 Sep 2026
What landed
On 29 Sep 2026, status.claude.com investigated elevated error rates from 14:21 UTC.
Scope in the early notes: Claude.ai including desktop and mobile apps, Claude Code, Claude Cowork, and some Claude API requests. Users might see failed requests, errors loading or sending conversations, or a prompt to sign in again.
14:36 UTC: first wave mitigated. Existing conversations mostly working again.
A second issue then blocked many users from signing in. Single sign-on and Sign in with Apple were unavailable. New chats, voice, Claude Code or Cowork sessions, purchases, and file uploads failed. Status told signed-in users not to sign out.
14:59 UTC: most services recovered. Signing in, new chats, voice, Code and Cowork sessions, purchases, and uploads worked again. Some messages sent between 14:00 and 14:59 UTC may not have been saved.
Resolved note at 16:27 UTC: impact from 07:00 PT / 14:00 UTC to 07:59 PT / 14:59 UTC. Affected: claude.ai, Claude Console, Claude API, Claude Code, Claude Cowork.
No public root cause.
Why it matters
An hour across chat, Code, Cowork, and API, plus a sign-in failure that made “just refresh” the wrong move. Unsaved messages are a data-loss footnote, not a latency footnote.
Satire margin
“If you’re signed in, please don’t sign out” is a status update and a hostage note.
Primary source
← Timeline· All cases· See a sibling failure? Submit it