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 [2][1][3].
  • No root cause, affected subsystems, or explicit rollback/patch details are disclosed in any of the public status updates [2][1][3].

Cross-Source Inference

  • 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) [2][3][1].
  • Because the incident is scoped to “Opus 4.6” on the status page and not to broader Claude APIs, impact likely concentrated on calls targeting that specific model variant rather than the entire platform (medium confidence) [2][3][1].

Implications and What to Watch

  • For integrators pinning to Opus 4.6: service appears restored, but hold on declaring full normalcy until Anthropic provides a postmortem; monitor error rates and latency dashboards closely for the next 24–48 hours.
  • Procurement and risk: do not adjust vendor risk ratings yet; absence of root cause and mitigation detail limits confidence shifts versus peers.
  • What to watch: an official incident report clarifying root cause, scope (API endpoints/subsystems), and whether a rollback or config change altered model behavior; any corroborating notices from major partners if downstream disruptions surface.