Cloudflare Clef slowdown on 14 November 2026
Cloudflare Clef full response from San Francisco: slower than usual; 2026-11-14 19:00 UTC to 2026-11-14 21:00 UTC: peak full response 522 ms vs a usual 322 ms.
- What our checks saw
- Slower than usual
- Cities affected
- San Francisco
- When
- to
- How long
- 2 hours
- Slowest check
- 522 ms, usually 322 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 |
|---|---|---|
| 16:00 | 306 ms | Normal |
| 16:30 | 300 ms | Normal |
| 17:00 | 330 ms | Normal |
| 17:30 | 176 ms | Normal |
| 18:00 | 846 ms | Much slower, or failing |
| 18:30 | 367 ms | Normal |
| 19:00 | 603 ms | Slower than usual |
| 19:30 | 441 ms | Normal |
| 20:00 | 297 ms | Normal |
| 20:30 | 288 ms | Normal |
| 21:00 | 226 ms | Normal |
| 21:30 | 187 ms | Normal |
| 22:00 | 308 ms | Normal |
| 22:30 | 323 ms | Normal |
| 23:00 | 322 ms | Normal |
| 23:30 | 202 ms | Normal |
| 00:00 | 285 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.