Anthropic resolves major Opus 4.6 error spike; no root cause disclosed, rollback status unclear
Published Mar 18, 2026, 3:21 PM UTC
Key entities
TLDR
Treat Opus 4.6 as operational again but maintain caution: the incident is marked resolved after a fix with major impact noted, yet no root cause or rollback detail is disclosed, so watch for regressions and official postmortem before adjusting risk posture.
Why this matters
The sequence (major impact → fix implemented → monitoring → resolved) indicates an operational intervention rather than a transient edge blip, but the lack of technical notes leaves whether this was a model configuration change or infrastructure fault unresolved (medium confidence).
What changed
- Anthropic reported increased errors affecting Claude Opus 4.6 with “Major” impact, implemented a fix, monitored, and then marked the incident resolved within roughly 40 minutes.
- No root cause, affected subsystems, or explicit rollback/patch details are disclosed in any of the public status updates.
Topic context
Use this page when you want fast context on confirmed model launches from OpenAI, Anthropic, Google DeepMind, xAI, Meta, and similar labs without scanning every release note, model card, or developer post yourself. Key angles: openai, anthropic, google deepmind, gemini.
Summary
Anthropic’s status page shows a major‑impact spike in errors specific to Claude Opus 4.6, followed by a fix, a monitoring period, and a final resolution, but with no stated root cause or confirmation of rollback versus configuration change; downstream consumers should consider the service recovered but keep contingency plans warm pending a formal incident report.