Cloudflare Clef slowdown on 11 November 2026
Cloudflare Clef full response from Singapore: slower than usual; 2026-11-11 12:30 UTC to 2026-11-11 14:30 UTC: peak full response 823 ms vs a usual 408 ms.
- What our checks saw
- Slower than usual
- Cities affected
- Singapore
- When
- to
- How long
- 2 hours
- Slowest check
- 823 ms, usually 408 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, Tokyo, Mumbai.
Singapore
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 09:30 | 367 ms | Normal |
| 10:00 | 728 ms | Slower than usual |
| 10:30 | 557 ms | Normal |
| 11:00 | 393 ms | Normal |
| 11:30 | 1.33 s | Much slower, or failing |
| 12:00 | 553 ms | Normal |
| 12:30 | 893 ms | Slower than usual |
| 13:00 | 752 ms | Slower than usual |
| 13:30 | 447 ms | Normal |
| 14:00 | 606 ms | Normal |
| 14:30 | 453 ms | Normal |
| 15:00 | 527 ms | Normal |
| 15:30 | 391 ms | Normal |
| 16:00 | 415 ms | Normal |
| 16:30 | 619 ms | Slower than usual |
| 17:00 | 422 ms | Normal |
| 17:30 | 373 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.