Resolved in 31 min — swift response, but shared component issue it seems
claude.ai and API unavailable
Original: claude.ai and API unavailable
Importance: 本番環境への直接影響を伴う API 障害であり、ユーザーおよび開発者に即座の影響を与えました
Summary
claude.ai and API services became unavailable on April 30, with investigation starting at 01:20 UTC, a fix implemented by 01:34 UTC, and full resolution confirmed by 01:51 UTC. Root cause details were not disclosed, but the roughly 30-minute incident window suggests a contained issue rather than systemic failure. Web users and developers integrating the API were affected.
Key Points
- Claude.ai and API unavailable for ~31 minutes on April 30
- Detected 01:20 UTC, fix deployed 01:34 UTC, resolved 01:51 UTC
- Root cause undisclosed; quick recovery suggests contained incident
- Both Web users and API-integrated developers affected
View developer notes (APIs, breaking changes, migration)
Claude API and claude.ai backend outage lasted approximately 31 minutes: incident detection and investigation at 01:20 UTC → fix deployed by 01:34 UTC → full recovery confirmed at 01:51 UTC. Root cause (DB connectivity, deployment issue, resource exhaustion, etc.) not disclosed. Simultaneous failure of REST API endpoints (/v1/messages, etc.) and claude.ai web interface suggests a shared core service disruption. Production workflows dependent on Claude likely returned timeouts or 5xx errors during the window.
Source: https://status.claude.com/incidents/2gf1jpyty350
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.