Cloudflare Clef slowdown on 15 October 2026
Cloudflare Clef full response from Amsterdam: slower than usual; 2026-10-15 05:30 UTC to 2026-10-15 07:00 UTC: peak full response 0.55 s vs a usual 0.33 s.
- What our checks saw
- Slower than usual
- Cities affected
- Amsterdam
- When
- to
- How long
- 90 minutes
- Slowest check
- 549 ms, usually 329 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 |
|---|---|---|
| 02:30 | 154 ms | Normal |
| 03:00 | 606 ms | Slower than usual |
| 03:30 | 310 ms | Normal |
| 04:00 | 357 ms | Normal |
| 04:30 | 1.08 s | Much slower, or failing |
| 05:00 | 779 ms | Slower than usual |
| 05:30 | 319 ms | Normal |
| 06:00 | 592 ms | Slower than usual |
| 06:30 | 305 ms | Normal |
| 07:00 | 417 ms | Normal |
| 07:30 | 327 ms | Normal |
| 08:00 | 289 ms | Normal |
| 08:30 | 221 ms | Normal |
| 09:00 | 243 ms | Normal |
| 09:30 | 250 ms | Normal |
| 10:00 | 278 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.