Cloudflare Clef slowdown on 3 November 2026
Cloudflare Clef full response from Tokyo: slower than usual; 2026-11-03 20:30 UTC to 2026-11-03 22:30 UTC: peak full response 698 ms vs a usual 399 ms.
- What our checks saw
- Slower than usual
- Cities affected
- Tokyo
- When
- to
- How long
- 2 hours
- Slowest check
- 698 ms, usually 399 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: Amsterdam, San Francisco, Montreal, Singapore, Mumbai.
Tokyo
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 17:30 | 426 ms | Normal |
| 18:00 | 659 ms | Slower than usual |
| 18:30 | 343 ms | Normal |
| 19:00 | 415 ms | Normal |
| 19:30 | 362 ms | Some requests failed |
| 20:00 | 396 ms | Normal |
| 20:30 | 989 ms | Slower than usual |
| 21:00 | 406 ms | Normal |
| 21:30 | 272 ms | Normal |
| 22:00 | 425 ms | Normal |
| 22:30 | 325 ms | Normal |
| 23:00 | 385 ms | Normal |
| 23:30 | 808 ms | Slower than usual |
| 00:00 | 343 ms | Normal |
| 00:30 | 371 ms | Normal |
| 01:00 | 419 ms | Normal |
| 01:30 | 490 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.