Crowd Signal Monitor
← Back to tracker

Opus 4.6 saw elevated errors on April 16, 2026

This was another model-specific event. It adds to the pattern that Claude reliability issues often sit at the model layer rather than looking like a single monolithic outage.

Published: Apr 16, 2026, 2:50 AM EDT

Updated: Apr 21, 2026, 8:40 AM EDT

Incident started: Apr 16, 2026, 1:58 AM EDT

Crowd spike noticed: Apr 16, 2026, 2:05 AM EDT

Resolved: Apr 16, 2026, 2:50 AM EDT

degradedModel/API52 minutes

Affected surface: Opus 4.6 requests

Official incident notes described elevated errors on Opus 4.6 before the model returned to baseline.

  • Model instability does not always appear clearly on the main Claude web surface.
  • Repeated Opus incidents suggest why model-level history deserves its own archive treatment.
  • Users tied to one model family can feel a much sharper outage than the broader site suggests.

A reviewed note on the April 16, 2026 Opus 4.6 incident that affected model reliability without necessarily taking all Claude surfaces down together.

Review the methodology page for how crowd reports are deduplicated and the status lag explainer for how independent reports differ from provider updates.

If you want the broader archive context, go back to the Claude outage history page.

Related notes in the same incident category: