Cloudflare Clef status
How fast the Cloudflare Clef starts answering from 6 cities, checked every 30 minutes.
- AI API
- Cloudflare
- clef
Last checked Every 30 minutes
Responding normally from 6 cities
Cloudflare Clef is responding normally from all 6 cities.
- Typical full response time
- 345 ms
- Last 24 hours · usually 336 ms
- Slower full response time
- 733 ms
- 95% of checks came in under this
- Failed requests
- 0
- Out of 855 requests in 24 hours
- Open incidents
- 0
- None right now
Cloudflare Clef by city
The latest full response time from each test location against its usual value. Each mark in the strip is one check.
| City | Status | Now | Usual | Last 24 hours |
|---|---|---|---|---|
| Normal | 433 ms | 287 ms | ||
| Normal | 260 ms | 308 ms | ||
| Normal | 322 ms | 275 ms | ||
| Normal | 635 ms | 381 ms | ||
| Normal | 388 ms | 364 ms | ||
| Normal | 337 ms | 512 ms |
- 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
Full response time for each check, as the median across all cities.
Recent incidents
All incidents →- Slower than usualMumbai, San Francisco, Singapore, Tokyo, Montreal
, lasted 6.5 hours · peak 951 ms, usually 515 ms
What happened → - Slower than usualMontreal
, lasted 90 minutes · peak 545 ms, usually 266 ms
What happened → - Slower than usualMontreal
, lasted 4.5 hours · peak 474 ms, usually 269 ms
What happened →
Brief slowdowns in our checks
Two or more slow checks in a row over the last seven days that didn't last long enough to count as an incident.
- Singapore · slower, for about an hour so farSince · peak 686 ms, usually 381 ms
- Singapore · slower for about an hour · peak 841 ms, usually 381 ms
- Montreal · slower for about an hour · peak 620 ms, usually 271 ms
Show 11 more
- Amsterdam · slower for about an hour · peak 492 ms, usually 287 ms
- Singapore · slower for about an hour · peak 973 ms, usually 385 ms
- Singapore · slower for about an hour · peak 598 ms, usually 383 ms
- Tokyo · slower for about an hour · peak 882 ms, usually 372 ms
- Singapore · slower for about an hour · peak 653 ms, usually 382 ms
- Amsterdam · slower for about an hour · peak 489 ms, usually 287 ms
- Singapore · slower for about an hour · peak 759 ms, usually 392 ms
- Tokyo · slower for about an hour · peak 698 ms, usually 370 ms
- San Francisco · slower for about an hour · peak 660 ms, usually 322 ms
- Singapore · slower for about an hour · peak 628 ms, usually 399 ms
- Singapore · slower for about an hour · peak 860 ms, usually 399 ms
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.