Claude API status
How fast the Claude API starts answering from 6 cities, checked every 30 minutes.
- AI API
- Anthropic
- claude-opus-5
Last checked Every 30 minutes
Some checks are missing
Collecting a first visible token baseline for Claude API from San Francisco.
- Typical time to first token
- 976 ms
- Last 24 hours ยท usually 874 ms
- Slower time to first token
- 2.51 s
- 95% of checks came in under this
- Failed requests
- 0
- Out of 849 requests in 24 hours
- Open incidents
- 0
- None right now
Claude API by city
The latest time to first token from each test location against its usual value. Each mark in the strip is one check.
| City | Status | Now | Usual | Last 24 hours |
|---|---|---|---|---|
| Normal | 795 ms | 871 ms | ||
| Collecting baseline | 685 ms | 756 ms | ||
| Normal | 617 ms | 625 ms | ||
| Normal | 870 ms | 962 ms | ||
| Normal | 843 ms | 876 ms | ||
| Normal | 912 ms | 1.50 s |
- Normal
- Slower than usual
- Some requests failed or degraded
- No check, or ours couldn't be verified
Colours compare each city with its own usual value, not with other services or cities. In the strip, grey marks are normal checks.
Last 24 hours
Time to first token for each check, as the median across all cities.
Recent incidents
All incidents โ- DegradedAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal
, lasted 11 hours ยท peak 4.98 s, usually 1.53 s
What happened โ - Slower than usualAmsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal
, lasted 11 hours ยท peak 2.67 s, usually 1.56 s
What happened โ - DegradedAmsterdam, San Francisco, Singapore, Tokyo, Montreal
, lasted 9.5 hours ยท peak 2.21 s, usually 968 ms
What happened โ
How these checks work
- Every 30 minutes, each of our 6 test locations sends 3 requests to every service on this page.
- We compare each result with the same city's usual value over the last 7 days. A city is slower than usual above 1.5ร that value (and at least 100 ms more), and degraded above 2.5ร.
- If 10% or more of a city's recent requests fail, it shows "Some requests failed"; from 25% it is degraded.
- One city has to stay that way for 90 minutes before we show it. When 3 or more cities see it at the same time, we show it straight away. It takes 90 minutes of normal checks to clear.
- Each city also fetches two small files from two unrelated networks. If both are slow too, the problem is most likely on our side, and we say so instead of blaming the service.
How fast is your API around the world?
Run a free speed test from multiple cities and find out where your users are waiting. No setup, no account required.
No account required ยท Takes about 30 seconds.