Opus 4.7 outage resolved in 20 min. Prod users should verify retry + fallback logic
Elevated errors on Claude Opus 4.7 — incident resolved
Original: Elevated errors on Claude Opus 4.7
Importance: 本番環境で Opus 4.7 を使用するユーザーに約13分間の API 利用不可を招いた障害
Summary
Anthropic's status page reported elevated error rates on Claude Opus 4.7. The issue was identified at 23:38 UTC on May 12, a fix was implemented by 23:51 UTC, and full recovery was confirmed at 23:58 UTC. No detailed root cause information was disclosed, but the incident was resolved within roughly 20 minutes.
Key Points
- Opus 4.7 experienced elevated errors, recovered within ~20 min
- Issue identified to fix deployed in ~13 min, then monitored
- Root cause details not yet disclosed
View developer notes (APIs, breaking changes, migration)
Claude Opus 4.7 API endpoints experienced elevated error rates. Issue identified 23:38 UTC May 12, fix implemented 23:51 UTC, recovery confirmed 23:58 UTC. Production consumers calling Opus 4.7 likely faced ~13 minutes of response failures. Root cause analysis not yet disclosed. Developers should ensure retry logic and fallback model support (e.g., Sonnet 4.5) for Opus 4.7–dependent applications.
Source: https://status.claude.com/incidents/3kkmgccb9z85
Outlet: Anthropic Status
This article is an AI-generated summary (OpenAI GPT-4o-mini) of publicly available information from Anthropic, OpenAI, Google, Meta, Mistral, DeepSeek, Sakana, and other vendors. The original source URL is always provided in accordance with fair-use citation requirements. Summaries are AI-generated and may contain mistranslations or misinterpretations. Always verify details with the original source.