Cloudflare logo

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

Incident0 ms500 ms1.00 s14:0017:0020:0023:00
Each check (UTC)Usual (325 ms)Slower than usualSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
14:00190 msNormal
14:30379 msNormal
15:00197 msNormal
15:30368 msNormal
16:00740 msSlower than usual
16:30383 msNormal
17:00708 msSlower than usual
17:30623 msSlower than usual
18:00575 msSlower than usual
18:30442 msNormal
19:00491 msSlower than usual
19:30327 msNormal
20:00261 msNormal
20:30293 msNormal
21:00342 msNormal
21:30351 msNormal
22:00243 msNormal
22:30275 msNormal
23:00393 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.