Cloudflare Clef slowdown on 11 November 2026
Cloudflare Clef full response from Tokyo: slower than usual; 2026-11-11 09:00 UTC to 2026-11-11 10:30 UTC: peak full response 895 ms vs a usual 369 ms.
- What our checks saw
- Slower than usual
- Cities affected
- Tokyo
- When
- to
- How long
- 90 minutes
- Slowest check
- 895 ms, usually 369 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 |
|---|---|---|
| 06:00 | 459 ms | Normal |
| 06:30 | 386 ms | Normal |
| 07:00 | 386 ms | Normal |
| 07:30 | 373 ms | Normal |
| 08:00 | 830 ms | Slower than usual |
| 08:30 | 1.26 s | Much slower, or failing |
| 09:00 | 527 ms | Normal |
| 09:30 | 538 ms | Normal |
| 10:00 | 495 ms | Normal |
| 10:30 | 261 ms | Normal |
| 11:00 | 615 ms | Slower than usual |
| 11:30 | 768 ms | Slower than usual |
| 12:00 | 395 ms | Normal |
| 12:30 | 274 ms | Normal |
| 13:00 | 298 ms | Normal |
| 13:30 | 504 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.