Cloudflare Clef slowdown on 2 November 2026
Cloudflare Clef full response from Amsterdam: slower than usual; 2026-11-02 00:30 UTC to 2026-11-02 02:00 UTC: peak full response 487 ms vs a usual 299 ms.
- What our checks saw
- Slower than usual
- Cities affected
- Amsterdam
- When
- to
- How long
- 90 minutes
- Slowest check
- 487 ms, usually 299 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: San Francisco, Montreal, Singapore, Tokyo, Mumbai.
Amsterdam
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 21:30 | 169 ms | Normal |
| 22:00 | 370 ms | Our check could not be verified |
| 22:30 | 266 ms | Normal |
| 23:00 | 354 ms | Normal |
| 23:30 | 637 ms | Slower than usual |
| 00:00 | 751 ms | Slower than usual |
| 00:30 | 223 ms | Normal |
| 01:00 | 251 ms | Normal |
| 01:30 | 148 ms | Normal |
| 02:00 | 338 ms | Normal |
| 02:30 | 707 ms | Slower than usual |
| 03:00 | 382 ms | Normal |
| 03:30 | 283 ms | Normal |
| 04:00 | 442 ms | Normal |
| 04:30 | 219 ms | Normal |
| 05:00 | 824 ms | 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.