Cloudflare Clef slowdown on 12 November 2026
Cloudflare Clef full response from Tokyo: slower than usual; 2026-11-12 22:30 UTC to 2026-11-13 00:00 UTC: peak full response 558 ms vs a usual 368 ms.
- What our checks saw
- Slower than usual
- Cities affected
- Tokyo
- When
- to
- How long
- 90 minutes
- Slowest check
- 558 ms, usually 368 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 |
|---|---|---|
| 19:30 | 386 ms | Normal |
| 20:00 | 611 ms | Slower than usual |
| 20:30 | 334 ms | Normal |
| 21:00 | 761 ms | Slower than usual |
| 21:30 | 409 ms | Normal |
| 22:00 | 826 ms | Slower than usual |
| 22:30 | 290 ms | Normal |
| 23:00 | 350 ms | Normal |
| 23:30 | 276 ms | Normal |
| 00:00 | 331 ms | Normal |
| 00:30 | 340 ms | Normal |
| 01:00 | 316 ms | Normal |
| 01:30 | 283 ms | Normal |
| 02:00 | 785 ms | Slower than usual |
| 02:30 | 346 ms | Normal |
| 03:00 | 351 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.