Cloudflare Clef slowdown on 2 November 2026
Cloudflare Clef full response from Amsterdam: slower than usual; 2026-11-02 06:00 UTC to 2026-11-02 08:00 UTC: peak full response 537 ms vs a usual 301 ms.
- What our checks saw
- Slower than usual
- Cities affected
- Amsterdam
- When
- to
- How long
- 2 hours
- Slowest check
- 537 ms, usually 301 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 |
|---|---|---|
| 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 |
| 05:30 | 292 ms | Normal |
| 06:00 | 781 ms | Much slower, or failing |
| 06:30 | 215 ms | Normal |
| 07:00 | 319 ms | Normal |
| 07:30 | 201 ms | Normal |
| 08:00 | 278 ms | Normal |
| 08:30 | 264 ms | Normal |
| 09:00 | 247 ms | Normal |
| 09:30 | 226 ms | Normal |
| 10:00 | 299 ms | Normal |
| 10:30 | 352 ms | Normal |
| 11:00 | 311 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.