Claude Status: Elevated Errors Across All Models – Resolved

On July 29, 2026, Anthropic's Claude service experienced elevated errors across all models. The incident lasted from 19:45 UTC to 21:26 UTC, and the official status page has marked it as resolved. Here's the timeline and what you need to know if you were affected.

Incident Timeline

• 19:49 UTC – Investigation begins.
• 20:33 UTC – Root cause identified: elevated errors across multiple models, including increased latency and request failures.
• 21:38 UTC – Recovery observed across most models; team continues to resolve remaining issues.
• 22:20 UTC – Success rates recovering across all models; monitoring continues.
• 22:36 UTC – Officially resolved.

The error window matches roughly 12:45 PT to 1:26 PT. If you saw timeouts, 5xx responses, or degraded performance in your Claude-based workflows during that period, this was likely the cause.

What This Means for Developers

If you're building on the Claude API or using Claude Code, remember that even major providers can have hiccups. For production workloads, consider implementing retry logic with exponential backoff and fallback models. The incident is a good reminder to check Claude's status page regularly, especially before deploys that depend on LLM calls.

Anthropic hasn't yet posted a detailed post-mortem, but the status page indicates the incident is fully resolved. For the latest updates, the original report is linked below.