Cloudflare Clef slowdown on 9 November 2026
Cloudflare Clef full response from San Francisco: slower than usual; 2026-11-09 17:00 UTC to 2026-11-09 20:00 UTC: peak full response 666 ms vs a usual 325 ms.
- What our checks saw
- Slower than usual
- Cities affected
- San Francisco
- When
- to
- How long
- 3 hours
- Slowest check
- 666 ms, usually 325 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, Montreal, Singapore, Tokyo, Mumbai.
San Francisco
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 14:00 | 190 ms | Normal |
| 14:30 | 379 ms | Normal |
| 15:00 | 197 ms | Normal |
| 15:30 | 368 ms | Normal |
| 16:00 | 740 ms | Slower than usual |
| 16:30 | 383 ms | Normal |
| 17:00 | 708 ms | Slower than usual |
| 17:30 | 623 ms | Slower than usual |
| 18:00 | 575 ms | Slower than usual |
| 18:30 | 442 ms | Normal |
| 19:00 | 491 ms | Slower than usual |
| 19:30 | 327 ms | Normal |
| 20:00 | 261 ms | Normal |
| 20:30 | 293 ms | Normal |
| 21:00 | 342 ms | Normal |
| 21:30 | 351 ms | Normal |
| 22:00 | 243 ms | Normal |
| 22:30 | 275 ms | Normal |
| 23:00 | 393 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.