Cloudflare Clef slowdown on 9 November 2026
Cloudflare Clef full response from Amsterdam, San Francisco, Tokyo: slower than usual; 2026-11-09 11:00 UTC to 2026-11-09 14:30 UTC: peak full response 620 ms vs a usual 325 ms.
- What our checks saw
- Slower than usual
- Cities affected
- Amsterdam, San Francisco, Tokyo
- When
- to
- How long
- 3.5 hours
- Slowest check
- 620 ms, usually 325 ms
- Cloudflare's status page
- Open it
Where our checks saw it
Each glowing city had slow or failing checks during the incident, shown at its worst. We test from 6 cities, so other places may have been hit too.
Our checks, city by city
Each point is one check every 30 minutes, from three hours before the incident to three hours after. Coloured points are the checks we counted as slower or failing. The shaded area shows how far above the usual time they were. Not affected: Montreal, Singapore, Mumbai.
Amsterdam
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 08:00 | 528 ms | Slower than usual |
| 08:30 | 338 ms | Normal |
| 09:00 | 321 ms | Normal |
| 09:30 | 337 ms | Normal |
| 10:00 | 273 ms | Normal |
| 10:30 | 816 ms | Much slower, or failing |
| 11:00 | 210 ms | Normal |
| 11:30 | 294 ms | Normal |
| 12:00 | 278 ms | Normal |
| 12:30 | 253 ms | Normal |
| 13:00 | 525 ms | Slower than usual |
| 13:30 | 294 ms | Normal |
| 14:00 | 304 ms | Normal |
| 14:30 | 444 ms | Normal |
| 15:00 | 339 ms | Normal |
| 15:30 | 308 ms | Normal |
| 16:00 | 301 ms | Normal |
| 16:30 | 321 ms | Normal |
| 17:00 | 581 ms | Slower than usual |
| 17:30 | 333 ms | Normal |
San Francisco
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 08:00 | 189 ms | Normal |
| 08:30 | 330 ms | Normal |
| 09:00 | 340 ms | Normal |
| 09:30 | 322 ms | Normal |
| 10:00 | 347 ms | Normal |
| 10:30 | 696 ms | Slower than usual |
| 11:00 | 322 ms | Normal |
| 11:30 | 348 ms | Normal |
| 12:00 | 569 ms | Slower than usual |
| 12:30 | 671 ms | Slower than usual |
| 13:00 | 505 ms | Slower than usual |
| 13:30 | 249 ms | Normal |
| 14:00 | 190 ms | Normal |
| 14:30 | 379 ms | Normal |
| 15:00 | 197 ms | Normal |
| 15:30 | 368 ms | Normal |
| 16:00 | 740 ms | Slower than usual |
| 16:30 | 383 ms | Normal |
| 17:00 | 708 ms | Slower than usual |
| 17:30 | 623 ms | Slower than usual |
Tokyo
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 08:00 | 518 ms | Normal |
| 08:30 | 1.06 s | Much slower, or failing |
| 09:00 | 426 ms | Normal |
| 09:30 | 371 ms | Normal |
| 10:00 | 606 ms | Slower than usual |
| 10:30 | 418 ms | Normal |
| 11:00 | 756 ms | Slower than usual |
| 11:30 | 327 ms | Normal |
| 12:00 | 577 ms | Slower than usual |
| 12:30 | 311 ms | Normal |
| 13:00 | 606 ms | Slower than usual |
| 13:30 | 440 ms | Normal |
| 14:00 | 368 ms | Normal |
| 14:30 | 274 ms | Normal |
| 15:00 | 584 ms | Slower than usual |
| 15:30 | 413 ms | Normal |
| 16:00 | 310 ms | Normal |
| 16:30 | 385 ms | Normal |
| 17:00 | 371 ms | Normal |
| 17:30 | 460 ms | Normal |
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.