Opus 5 hit with elevated errors; fix underway. Consider Sonnet fallback for now.
Claude Opus 5 experiencing degraded performance; Anthropic identifies root cause
Original: Degraded performance for Claude Opus 5
Importance: 本番APIの障害で既存ユーザーに即影響し、修正完了までの対応を要する。
Summary
Anthropic reported elevated error rates on requests to Claude Opus 5 as of August 5. The company has identified the root cause and is actively working on a fix. Updates will be provided as soon as resolution is available. This impacts developers and API users currently relying on Opus 5 for production workloads.
Key Points
- Elevated error rates confirmed on Claude Opus 5 API calls
- Anthropic has identified root cause and begun fixing
- Fix completion timeline TBD; further updates pending
- Production users should prepare retry & fallback strategies
- Continuous monitoring of status page essential
View developer notes (APIs, breaking changes, migration)
Claude Opus 5 API requests showing elevated error rates; Anthropic has identified the root cause and engineering team is actively fixing. Status marked 'Identified' on official status page. Specific error rate, affected regions, endpoint details (/messages, etc.) not disclosed in this alert. Production users of Opus 5 should reinforce retry logic, adjust timeout thresholds, and consider temporary fallback to Sonnet models. Continuous monitoring of status.claude.com critical until resolution.
Source: https://status.claude.com/incidents/mgp99sn4ynd4
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.