Cloudflare Clef slowdown on 4 November 2026
Cloudflare Clef full response from Tokyo: slower than usual; 2026-11-04 09:30 UTC to 2026-11-04 11:30 UTC: peak full response 724 ms vs a usual 399 ms.
- What our checks saw
- Slower than usual
- Cities affected
- Tokyo
- When
- to
- How long
- 2 hours
- Slowest check
- 724 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 |
|---|---|---|
| 06:30 | 317 ms | Normal |
| 07:00 | 290 ms | Normal |
| 07:30 | 521 ms | Normal |
| 08:00 | 400 ms | Normal |
| 08:30 | 822 ms | Slower than usual |
| 09:00 | 391 ms | Normal |
| 09:30 | 948 ms | Slower than usual |
| 10:00 | 500 ms | Normal |
| 10:30 | 308 ms | Normal |
| 11:00 | 330 ms | Normal |
| 11:30 | 297 ms | Normal |
| 12:00 | 618 ms | Slower than usual |
| 12:30 | 474 ms | Normal |
| 13:00 | 689 ms | Slower than usual |
| 13:30 | 559 ms | Normal |
| 14:00 | 401 ms | Normal |
| 14:30 | 3.65 s | Much slower, or failing |
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.