Case · 2026-08-19

Opus 5 and Haiku 4.5, identified, fixed, next slide

Cause identified. Cause unnamed. Users already know the error code.

claudeinfrasev 4/5official
outagereliability

Summary: Status page identified a cause of elevated errors on Claude Opus 5 and Claude Haiku 4.5, implemented a fix, and marked the incident resolved the same morning UTC. Affected claude.ai, API, Claude Code, and Claude Cowork. No public root-cause detail beyond that sequence.

Source: status.claude.com · 19 Aug 2026

What landed

On 19 Aug 2026 at 09:42 UTC, status.claude.com said it had identified the cause of elevated errors on Claude Opus 5 and Claude Haiku 4.5 and was working on a fix.

Monitoring at 10:33 UTC. Resolved at 11:02 UTC.

Surfaces: claude.ai, Claude API, Claude Code, Claude Cowork. No public write-up of what the cause was.

Why it matters

Fourth consecutive calendar day with a status incident in this batch. Identified-then-resolved without a named cause is a complete official story and an incomplete user story.

Satire margin

They found it. They fixed it. They did not introduce you.

Primary source

Status: degraded performance for Claude Opus 5 and Claude Haiku 4.5 (19 Aug)

← Timeline· All cases· See a sibling failure? Submit it