Cloudflare logo

Cloudflare Clef slowdown on 4 November 2026

Cloudflare Clef full response from Tokyo: slower than usual; 2026-11-04 09:30 UTC to 2026-11-04 11:30 UTC: peak full response 724 ms vs a usual 399 ms.

What our checks saw
Slower than usual
Cities affected
Tokyo
When
to
How long
2 hours
Slowest check
724 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 ms2.50 s5.00 s06:3009:3012:30
Each check (UTC)Usual (399 ms)Slower than usualSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
06:30317 msNormal
07:00290 msNormal
07:30521 msNormal
08:00400 msNormal
08:30822 msSlower than usual
09:00391 msNormal
09:30948 msSlower than usual
10:00500 msNormal
10:30308 msNormal
11:00330 msNormal
11:30297 msNormal
12:00618 msSlower than usual
12:30474 msNormal
13:00689 msSlower than usual
13:30559 msNormal
14:00401 msNormal
14:303.65 sMuch slower, or failing

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.