Cloudflare logo

Cloudflare Clef slowdown on 3 November 2026

Cloudflare Clef full response from Tokyo: slower than usual; 2026-11-03 20:30 UTC to 2026-11-03 22:30 UTC: peak full response 698 ms vs a usual 399 ms.

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

Tokyo

Incident0 ms750 ms1.50 s17:3020:3023:30
Each check (UTC)Usual (399 ms)Slower than usualSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
17:30426 msNormal
18:00659 msSlower than usual
18:30343 msNormal
19:00415 msNormal
19:30362 msSome requests failed
20:00396 msNormal
20:30989 msSlower than usual
21:00406 msNormal
21:30272 msNormal
22:00425 msNormal
22:30325 msNormal
23:00385 msNormal
23:30808 msSlower than usual
00:00343 msNormal
00:30371 msNormal
01:00419 msNormal
01:30490 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.