Cloudflare Clef slowdown on 10 November 2026
Cloudflare Clef full response from San Francisco: slower than usual; 2026-11-10 21:00 UTC to 2026-11-10 23:30 UTC: peak full response 669 ms vs a usual 319 ms.
- What our checks saw
- Slower than usual
- Cities affected
- San Francisco
- When
- to
- How long
- 2.5 hours
- Slowest check
- 669 ms, usually 319 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 |
|---|---|---|
| 18:00 | 370 ms | Normal |
| 18:30 | 506 ms | Slower than usual |
| 19:00 | 395 ms | Normal |
| 19:30 | 439 ms | Normal |
| 20:00 | 721 ms | Slower than usual |
| 20:30 | 420 ms | Normal |
| 21:00 | 613 ms | Slower than usual |
| 21:30 | 725 ms | Slower than usual |
| 22:00 | 440 ms | Normal |
| 22:30 | 371 ms | Normal |
| 23:00 | 331 ms | Normal |
| 23:30 | 364 ms | Normal |
| 00:00 | 485 ms | Slower than usual |
| 00:30 | 374 ms | Normal |
| 01:00 | 332 ms | Normal |
| 01:30 | 396 ms | Normal |
| 02:00 | 278 ms | Normal |
| 02:30 | 312 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.