Cloudflare logo

Cloudflare Clef slowdown on 11 November 2026

Cloudflare Clef full response from Singapore: slower than usual; 2026-11-11 12:30 UTC to 2026-11-11 14:30 UTC: peak full response 823 ms vs a usual 408 ms.

What our checks saw
Slower than usual
Cities affected
Singapore
When
to
How long
2 hours
Slowest check
823 ms, usually 408 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, San Francisco, Montreal, Tokyo, Mumbai.

Singapore

Incident0 ms750 ms1.50 s09:3012:3015:30
Each check (UTC)Usual (408 ms)Slower than usualSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
09:30367 msNormal
10:00728 msSlower than usual
10:30557 msNormal
11:00393 msNormal
11:301.33 sMuch slower, or failing
12:00553 msNormal
12:30893 msSlower than usual
13:00752 msSlower than usual
13:30447 msNormal
14:00606 msNormal
14:30453 msNormal
15:00527 msNormal
15:30391 msNormal
16:00415 msNormal
16:30619 msSlower than usual
17:00422 msNormal
17:30373 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.