Cloudflare Clef slowdown on 9 November 2026
Cloudflare Clef full response from Singapore: slower than usual; 2026-11-09 09:00 UTC to 2026-11-09 10:30 UTC: peak full response 657 ms vs a usual 411 ms.
- What our checks saw
- Slower than usual
- Cities affected
- Singapore
- When
- to
- How long
- 90 minutes
- Slowest check
- 657 ms, usually 411 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 |
|---|---|---|
| 06:00 | 473 ms | Normal |
| 06:30 | 407 ms | Normal |
| 07:00 | 413 ms | Normal |
| 07:30 | 541 ms | Normal |
| 08:00 | 813 ms | Slower than usual |
| 08:30 | 954 ms | Slower than usual |
| 09:00 | 360 ms | Normal |
| 09:30 | 398 ms | Normal |
| 10:00 | 563 ms | Normal |
| 10:30 | 579 ms | Normal |
| 11:00 | 647 ms | Slower than usual |
| 11:30 | 581 ms | Normal |
| 12:00 | 581 ms | Normal |
| 12:30 | 676 ms | Slower than usual |
| 13:00 | 509 ms | Normal |
| 13:30 | 372 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.