Cloudflare logo

Cloudflare Clef slowdown on 2 November 2026

Cloudflare Clef full response from Amsterdam: slower than usual; 2026-11-02 06:00 UTC to 2026-11-02 08:00 UTC: peak full response 537 ms vs a usual 301 ms.

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

Amsterdam

Incident0 ms500 ms1.00 s03:0006:0009:00
Each check (UTC)Usual (302 ms)Much slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
03:00382 msNormal
03:30283 msNormal
04:00442 msNormal
04:30219 msNormal
05:00824 msMuch slower, or failing
05:30292 msNormal
06:00781 msMuch slower, or failing
06:30215 msNormal
07:00319 msNormal
07:30201 msNormal
08:00278 msNormal
08:30264 msNormal
09:00247 msNormal
09:30226 msNormal
10:00299 msNormal
10:30352 msNormal
11:00311 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.