Cloudflare logo

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

Incident0 ms500 ms1.00 s16:0019:0022:00
Each check (UTC)Usual (322 ms)Slower than usualSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
16:00306 msNormal
16:30300 msNormal
17:00330 msNormal
17:30176 msNormal
18:00846 msMuch slower, or failing
18:30367 msNormal
19:00603 msSlower than usual
19:30441 msNormal
20:00297 msNormal
20:30288 msNormal
21:00226 msNormal
21:30187 msNormal
22:00308 msNormal
22:30323 msNormal
23:00322 msNormal
23:30202 msNormal
00:00285 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.