Outage

Three separate Anthropic stories broke on April 13, and read together they form a single narrative: developer trust in Claude is under sustained pressure, from reliability to quality to transparency. The Outage Claude.ai went down. Not for long — the incident lasted from 15:31 to 16:19 UTC, roughly 48 minutes — but the timing and the way Anthropic communicated it added fuel to an already active fire. The official status page described “elevated error rates” affecting both Claude.ai and Claude Code, attributing it to “capacity-balancing measures.” ...

Anthropic’s Claude has now gone down three times in March 2026 — and the pattern is getting hard to dismiss as routine maintenance. The latest outage peaked at over 6,800 Downdetector reports, with API 500 errors cascading across agentic workflows, Claude Code sessions, and enterprise integrations worldwide. For teams running Claude-backbone pipelines, this isn’t just an inconvenience. It’s a reliability risk that demands a serious engineering response. What Happened (Again) On March 17, Claude’s API began returning 500 errors at scale. Users across multiple continents reported complete service unavailability, with Downdetector tracking reports surging past 6,800 complaints at peak — a figure confirmed across multiple independent sources including The Independent, Rolling Out, Economic Times, and Hindustan Times. ...

At 2:44 p.m. UTC on March 11, 2026, thousands of developers found themselves locked out of Claude Code mid-session. No warning. No graceful degradation. Just a dead CLI and a 15-second timeout loop. The good news: if you were connecting via API key, you noticed nothing. The Claude API stayed fully operational throughout the two-hour incident — a detail that matters enormously for anyone designing resilient agentic workflows. What Actually Broke The failure was isolated to OAuth authentication — the browser-based login flow that Claude Code uses to connect to Anthropic’s servers. When developers ran /login, their browser would open, they’d click “Authorize,” see a confirmation… and then the CLI would hang until hitting its hardcoded 15-second timeout. ...

Anthropic’s Claude went down twice in under 24 hours this week — and the developer community’s reaction tells a story about something bigger than a couple of bad server days. The second outage hit on March 3, investigation commencing at 03:15 UTC. It followed Monday’s first disruption, which Anthropic attributed to unprecedented demand. Chat, API, and Claude Code were all affected. Developers watched their pipelines stall, their autonomous agents go quiet, and their Claude Code sessions freeze mid-task — again. ...

Claude went dark on Monday morning, and for once it wasn’t a minor hiccup. Starting around 11:49 UTC on March 2, 2026, Anthropic’s consumer-facing AI products — Claude.ai, Claude Code, and the mobile app — began reporting widespread failures. Users across North America, Europe, and Asia flooded social media with screenshots of error pages, spinning loaders, and authentication failures. Anthropic’s official response came quickly: the company cited “unprecedented demand over the past week” as the root cause of service degradation. The statement, confirmed by Bloomberg and CNET, framed this as a capacity problem rather than a security incident — but it raised more questions than it answered. ...