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
Collecting a baseline
Collecting a full response baseline for Cloudflare Clef from Amsterdam.
- Typical full response time
- 380 ms
- Last 24 hours · usually 366 ms
- Slower full response time
- 877 ms
- 95% of checks came in under this
- Failed requests
- 0
- Out of 810 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 |
|---|---|---|---|---|
 Amsterdam | Collecting baseline | 329 ms | 290 ms | |
 San Francisco | Collecting baseline | 481 ms | 326 ms | |
 Montreal | Collecting baseline | 360 ms | 327 ms | |
 Singapore | Collecting baseline | 578 ms | 434 ms | |
 Tokyo | Collecting baseline | 478 ms | 404 ms | |
 Mumbai | Collecting baseline | 334 ms | 718 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 usualTokyo
, lasted 90 minutes · peak 631 ms, usually 404 ms
What happened → - Slower than usualMumbai, Tokyo, Montreal
, lasted 90 minutes · peak 1.40 s, usually 742 ms
What happened → - Slower than usualTokyo
, lasted 90 minutes · peak 686 ms, usually 425 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.
- Amsterdam · slower for about an hour · peak 493 ms, usually 289 ms
- Tokyo · slower for about an hour · peak 748 ms, usually 404 ms
- San Francisco · slower for about an hour · peak 695 ms, usually 331 ms
Show 15 more
- Amsterdam · slower for about an hour · peak 560 ms, usually 292 ms
- Tokyo · slower for about an hour · peak 1.36 s, usually 401 ms
- Tokyo · slower for about an hour · peak 616 ms, usually 397 ms
- Tokyo · slower for about an hour · peak 689 ms, usually 403 ms
- Tokyo · slower for about an hour · peak 757 ms, usually 400 ms
- Montreal · slower for about an hour · peak 680 ms, usually 341 ms
- San Francisco · slower for about an hour · peak 922 ms, usually 341 ms
- Tokyo · slower for about an hour · peak 828 ms, usually 422 ms
- Amsterdam · slower for about an hour · peak 556 ms, usually 332 ms
- Singapore · slower for about an hour · peak 1.19 s, usually 536 ms
- Tokyo · slower for about an hour · peak 1.03 s, usually 428 ms
- San Francisco · slower for about an hour · peak 1.45 s, usually 342 ms
- San Francisco · slower for about an hour · peak 776 ms, usually 340 ms
- Amsterdam · slower for about an hour · peak 654 ms, usually 325 ms
- Tokyo · slower for about an hour · peak 1.21 s, usually 432 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.