Opus 4.7 errors spike, restored in 3 hours. Transparent timeline, but root cause still unclear.
Elevated errors on Claude Opus 4.7 — incident resolved
Original: Elevated errors on Claude Opus 4.7
Importance: 本番環境ユーザーに直接影響を与えた障害のため、迅速な認知と対応検証が必要。
Summary
Anthropic reported elevated error rates on Claude Opus 4.7 on April 25. The issue was identified at 08:43 UTC, a fix was implemented and monitoring began at 08:57 UTC, and full resolution was confirmed at 11:58 UTC. No specific error causes or affected users were disclosed. Service is now fully restored.
Key Points
- Opus 4.7 error rate spike detected and identified at 08:43 UTC
- Fix deployed at 08:57 UTC; full resolution confirmed at 11:58 UTC
- Specific root cause and scope remain undisclosed
- Timeline communicated transparently via status page
View developer notes (APIs, breaking changes, migration)
Elevated errors occurred on Claude Opus 4.7. Timeline: identified at 08:43 UTC, fix deployed at 08:57 UTC, fully resolved by 11:58 UTC (~3-hour monitoring window). Specific details absent: error rate percentage, affected endpoints (messages, embeddings, etc.), HTTP status codes, rate limit interactions, or recommended retry strategies. Developers should review logs from the incident window for 5xx responses and evaluate backoff logic robustness.
Source: https://status.claude.com/incidents/87m29x6sk78g
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.