Cloudflare Clef slowdown on 20 October 2026
Cloudflare Clef full response from Tokyo: slower than usual; 2026-10-20 01:00 UTC to 2026-10-20 02:30 UTC: peak full response 0.63 s vs a usual 0.4 s.
- What our checks saw
- Slower than usual
- Cities affected
- Tokyo
- When
- to
- How long
- 90 minutes
- Slowest check
- 631 ms, usually 404 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 |
|---|---|---|
| 22:00 | 305 ms | Normal |
| 22:30 | 404 ms | Normal |
| 23:00 | 350 ms | Normal |
| 23:30 | 424 ms | Normal |
| 00:00 | 863 ms | Slower than usual |
| 00:30 | 606 ms | Normal |
| 01:00 | 655 ms | Slower than usual |
| 01:30 | 352 ms | Normal |
| 02:00 | 356 ms | Normal |
| 02:30 | 331 ms | Normal |
| 03:00 | 390 ms | Normal |
| 03:30 | 505 ms | Normal |
| 04:00 | 748 ms | Slower than usual |
| 04:30 | 713 ms | Slower than usual |
| 05:00 | 448 ms | Normal |
| 05:30 | 376 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.