Cloudflare Clef slowdown on 17 November 2026
Cloudflare Clef full response from Montreal: slower than usual; 2026-11-17 21:30 UTC to 2026-11-17 23:00 UTC: peak full response 545 ms vs a usual 266 ms.
- What our checks saw
- Slower than usual
- Cities affected
- Montreal
- When
- to
- How long
- 90 minutes
- Slowest check
- 545 ms, usually 266 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, Singapore, Tokyo, Mumbai.
Montreal
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 18:30 | 380 ms | Normal |
| 19:00 | 355 ms | Normal |
| 19:30 | 263 ms | Normal |
| 20:00 | 509 ms | Slower than usual |
| 20:30 | 336 ms | Normal |
| 21:00 | 865 ms | Much slower, or failing |
| 21:30 | 225 ms | Normal |
| 22:00 | 357 ms | Normal |
| 22:30 | 317 ms | Normal |
| 23:00 | 354 ms | Normal |
| 23:30 | 293 ms | Normal |
| 00:00 | 448 ms | Slower than usual |
| 00:30 | 620 ms | Slower than usual |
| 01:00 | 260 ms | Normal |
| 01:30 | 417 ms | Slower than usual |
| 02:00 | 399 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.