Is Claude down right now?
Authenticated API inference - 4 models monitored · How we classify outages
Claude is currently operational - 103ms HTTP response. Last checked . 90-day uptime: 99.6%. Claude API: all 4 models responding - fastest TTFT 507ms.
Stay informed
Follow @tickerr_ai
We post when tier 1 LLM APIs go down - before the official status page updates.
Follow on X →Or get the weekly reliability digest:
Add a status badge
Show live Claude status on your site, README, or docs.
HTTP uptime (90d)
99.6%
20 incidents (90d)
HTTP response now
103ms
HTTP p50 (7d)
224ms
median ping response
HTTP p95 (7d)
1072ms
tail ping response
Claude API Status
Live · every 5 minBest TTFT (p50)
507ms
time to first token
Best throughput
64tok/s
output tokens/sec (24h avg)
Min success rate
99%
worst model (24h)
P50 = typical speed. P95 = worst case 95% of the time. Measured by Tickerr's independent inference checks. Requires ≥10 checks to display.
TTFT over 24 hours
ⓘ Authenticated streaming API calls via native fetch. TTFT = milliseconds from request start to first streamed token chunk. Throughput = output tokens ÷ generation time. Checks run from Vercel us-east-1. Independent of the provider's official status page.
Agent monitoring active · 11 agents reporting · Powered by Tickerr MCP
HTTP endpoint response time (7 days)
p50 224ms·p95 1072msⓘ HTTP response times to Claude's status endpoint - measures infrastructure availability, not API inference speed. For TTFT and model-level API status, see the Claude API Status section above.
90-day uptime comparison
Independent monitoring catches issues faster - official pages sometimes lag by hours before acknowledging problems.
Service components
via status.anthropic.com ↗Incident history
We are currently investigating this issue.
We are currently investigating this issue.
We had an elevated error rate on Opus 4.7 from 6:30 UTC until 10:30 UTC
We are currently investigating this issue.
claude-sonnet-4-6 API Latency Degraded
Independent monitoring detected elevated API latency for claude-sonnet-4-6. Current TTFT is 4.3× above the rolling p50 baseline (4560ms vs p50 1054ms). The service is responding but slower than normal…
We are currently investigating this issue.
We are investigating elevated errors for users of Claude.ai, and will provide an update as soon as possible.
We are currently investigating this issue.
We are currently investigating this issue.
claude-haiku-4-5 API Latency Degraded
Independent monitoring detected elevated API latency for claude-haiku-4-5. Current TTFT is 3.8× above the rolling p50 baseline (1997ms vs p50 520ms). The service is responding but slower than normal. …
We are currently investigating this issue.
We are currently investigating this issue.
From 04:34–04:42 UTC, we saw elevated errors and latency on requests within the Claude.ai applications. Additionally, users may have experienced errors when attempting to login, including authenticati…
We are investigating elevated errors on requests to Claude Opus 4.7. We will provide an update as soon as possible.
claude-haiku-4-5 API Latency Degraded
Independent monitoring detected elevated API latency for claude-haiku-4-5. Current TTFT is 2.1× above the rolling p50 baseline (1026ms vs p50 482ms). The service is responding but slower than normal. …
We are currently investigating this issue.
claude-sonnet-4-6 API Latency Degraded
Independent monitoring detected elevated API latency for claude-sonnet-4-6. Current TTFT is 3.2× above the rolling p50 baseline (3576ms vs p50 1103ms). The service is responding but slower than normal…
We are currently investigating this issue.
We are currently investigating this issue.
We are currently investigating this issue.
Related pages
Claude API not working? Common error codes
If Claude's API is returning errors, the table below explains what each code means and how to fix it. If errors are widespread, check the live status above - a service incident will appear there within minutes.
| Error | What it means & what to do |
|---|---|
| HTTP 429 | Rate limit hit - check your plan tier, add exponential backoff |
| HTTP 529 (overload_error) | Anthropic is overloaded - retry after 30–60 seconds |
| HTTP 500 (api_error) | Unexpected server error - retry once, then check this page |
| HTTP 503 | Service unavailable - check for active incidents below |
Note: Tickerr monitors Claude's status endpoint, not individual API calls. An HTTP 429 or 500 in your app may be specific to your account tier - check the rate limits page for plan-specific thresholds.
About Claude status
Claude is Anthropic's AI assistant and API, available in Haiku, Sonnet, and Opus tiers. This page tracks two independent signals: HTTP availability (is Anthropic's infrastructure reachable?) and live API inference (is the Claude API actually working for developers?). Tickerr makes authenticated API calls to all six Claude models - claude-haiku-4-5, claude-haiku-3-5, claude-sonnet-4-6, claude-sonnet-4, claude-opus-4-6, and claude-opus-4 - every 5 minutes, measuring TTFT (time-to-first-token) and output throughput. This catches model-layer failures that don't show up as HTTP outages, covering roughly 35% of incidents. Common Claude API errors: HTTP 529 overloaded_error (Anthropic at capacity - retry after 30–60s), HTTP 429 rate_limit_error (you've hit plan limits - check the rate limits page), HTTP 500 api_error (unexpected server error - retry once). If the Claude API is not working or returning 529 overloaded responses, check the live status above - Tickerr typically detects these within 5 minutes. Claude API latency (TTFT) typically runs 300–800ms for Haiku models and 600ms–2s for Opus under normal load. Anthropic's official status page at status.anthropic.com is updated within 15–30 minutes of a confirmed incident; Tickerr's independent inference monitoring surfaces issues faster.
You can also check the official Claude status page.