April 8, 2026
AI hits a wrong note, crowd hits caps lock
Sonnet 4.6 Elevated Rate of Errors
Sonnet hits a sour note: outage sparks meme-fest and “spend the cash” chants
TLDR: Claude’s Sonnet 4.6 glitched for a couple hours overnight and was quickly fixed, but the comment section erupted. Users mocked the uptime, questioned why a cash-rich company can’t keep servers steady, and split between “minor blip” and “trust issue” camps—because reliability matters when your work depends on it.
Claude’s Sonnet 4.6 hit a late‑night wobble, throwing extra errors from about 11 pm to 1:50 am Pacific. It’s fixed now, says the official status page. But the real show was the comments, where users turned a routine hiccup into a roast. The harshest zinger: it’s “probably more newsworthy when it’s up, not down,” a burn that had the crowd cackling. Others demanded Anthropic open the checkbook, pointing to talk of a “$30B run rate” and yelling: if the cash is flowing, the servers shouldn’t be wobbling.
Then came the literary shade: a “Flowers for Algernon moment,” implying the smarter the bot gets, the more it stumbles—brutal. Some tried to downshift the drama, noting Hacker News loves a front-page panic but that models “are up or down on any given day,” linking back to the status page receipts. Meanwhile, another jab mocked the company’s big-brain aura—“mythos” won’t fix outages—while devs groaned that everything from the website to the API and coding tools took a hit. The vibe split cleanly: pragmatists saying “it was short and overnight, chill,” versus uptime purists saying reliability is the whole product. Verdict from the crowd? Fix landed, but trust took a dent—and they want fewer sonnets, more stability.
Key Points
- •Incident: Elevated error rates for Claude Sonnet 4.6.
- •Impact window: Approximately 23:00 PT (07:00 UTC) to 1:50 PT (09:50 UTC) on Apr 8, 2026.
- •Affected services: claude.ai, platform.claude.com, Claude API (api.anthropic.com), Claude Code, Claude Cowork.
- •Timeline: Investigating (06:23 UTC) → Update (07:06 UTC) → Identified/Fix in progress (07:59 UTC) → Monitoring (09:01 UTC) → Resolved (09:33 UTC).
- •Status: Fix implemented and incident resolved; error rates returned to baseline.