Cloudflare Clef slowdown on 16 October 2026
Cloudflare Clef full response from Tokyo: slower than usual; 2026-10-16 19:00 UTC to 2026-10-16 20:30 UTC: peak full response 0.69 s vs a usual 0.42 s.
- What our checks saw
- Slower than usual
- Cities affected
- Tokyo
- When
- to
- How long
- 90 minutes
- Slowest check
- 686 ms, usually 425 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 |
|---|---|---|
| 16:00 | 448 ms | Normal |
| 16:30 | 902 ms | Slower than usual |
| 17:00 | 381 ms | Normal |
| 17:30 | 670 ms | Slower than usual |
| 18:00 | 685 ms | Slower than usual |
| 18:30 | 702 ms | Slower than usual |
| 19:00 | 670 ms | Slower than usual |
| 19:30 | 370 ms | Normal |
| 20:00 | 481 ms | Normal |
| 20:30 | 334 ms | Normal |
| 21:00 | 385 ms | Normal |
| 21:30 | 508 ms | Normal |
| 22:00 | 590 ms | Normal |
| 22:30 | 365 ms | Normal |
| 23:00 | 333 ms | Normal |
| 23:30 | 282 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.