Cloudflare logo

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

Incident0 ms400 ms800 ms18:0021:0000:00
Each check (UTC)Usual (319 ms)Slower than usualSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
18:00370 msNormal
18:30506 msSlower than usual
19:00395 msNormal
19:30439 msNormal
20:00721 msSlower than usual
20:30420 msNormal
21:00613 msSlower than usual
21:30725 msSlower than usual
22:00440 msNormal
22:30371 msNormal
23:00331 msNormal
23:30364 msNormal
00:00485 msSlower than usual
00:30374 msNormal
01:00332 msNormal
01:30396 msNormal
02:00278 msNormal
02:30312 msNormal

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.

Test my API

No account required · Takes about 30 seconds.