Is Claude down right now?
Live public-endpoint check for Claude (claude.ai). We compare EU and US reachability, then link to the provider reference for broader context.
Checking Claude…
Pinging claude.ai from our servers
About Claude
Claude is Anthropic's AI assistant, with a consumer product at claude.ai (chat, Projects, Artifacts, Computer Use) and a developer API at api.anthropic.com used by Cursor, Zed, Raycast, and thousands of LLM-powered apps. Claude Code, Anthropic's terminal/IDE agent, runs against the same API. Outages show up as chat responses failing mid-stream, Artifacts not rendering, Projects losing context between turns, or the API returning 529 "overloaded" errors. Different model tiers (Opus, Sonnet, Haiku) can be affected independently, a Sonnet outage may leave Opus healthy and vice versa. Claude-powered agents hit rate-limit surges first during any capacity incident.
The official Claude status page is available as a reference. Official pages are useful, but they can lag behind real outages by minutes or hours. Independent monitoring catches issues faster.
How Claude outages affect production workloads
Developer-platform outages have outsized impact because they cascade. When Claude is degraded, every customer's build pipeline, deploy hook, or webhook delivery can stall, and the failure mode often looks like a customer problem before engineers realize the dependency is the cause. CI runs hang, status checks never report, and queued jobs pile up silently.
The live check above provides independent public-endpoint evidence from EU and US, including status and response timing. That helps separate a broad reachability problem from a local client issue, but it does not execute your private API call, build, webhook, or deploy. Test the exact dependency path before attributing the incident to Claude.
Common signs Claude is having issues
- API rate limits returning earlier than the documented thresholds
- Webhook deliveries showing 5xx errors or unusual latency tail
- Deploy or build hooks accepted by Claude but never firing downstream
- OAuth or token endpoints failing intermittently for the same client credentials
What to do when Claude is degraded
When Claude is having trouble, the fastest mitigation is usually feature-flagging the dependency off if your application can degrade gracefully. Check the multi-region results on this page first; if both regions report healthy but your application still sees failures, the issue is likely your network path or DNS, not Claude itself.
Monitor Claude automatically.
Get independent alerts when the public Claude endpoint fails a confirmed check. Start free with 10-minute checks, or use Business or Agency for 60-second uptime checks.
10-minute free checks
Business and Agency support 60-second uptime checks.
Multi-region
EU & US checks. Catch regional outages.
Email + push on Free
Paid plans unlock additional team and incident channels.
free forever · paid trials last 10 days
Provider status references
and endpoint checks answer different questions.
Independent endpoint evidence
The regional check can show that a public endpoint is failing before or after a provider posts broader incident context. It does not validate every product subsystem.
Scheduled alerts
Monitor Claude on your plan interval and route confirmed endpoint failures through the notification channels available to your workspace.
Multi-region verification
EU and US results can reveal a regional difference in public-endpoint reachability. Confirm the exact workflow and provider region you use.
Historical data
Track Claude uptime over time. See trends, identify recurring issues, and make informed decisions about your dependency.