Cloudflare logo

Cloudflare Clef slowdown on 11 November 2026

Cloudflare Clef full response from Tokyo: slower than usual; 2026-11-11 09:00 UTC to 2026-11-11 10:30 UTC: peak full response 895 ms vs a usual 369 ms.

What our checks saw
Slower than usual
Cities affected
Tokyo
When
to
How long
90 minutes
Slowest check
895 ms, usually 369 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 s06:0009:0012:00
Each check (UTC)Usual (369 ms)Slow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
06:00459 msNormal
06:30386 msNormal
07:00386 msNormal
07:30373 msNormal
08:00830 msSlower than usual
08:301.26 sMuch slower, or failing
09:00527 msNormal
09:30538 msNormal
10:00495 msNormal
10:30261 msNormal
11:00615 msSlower than usual
11:30768 msSlower than usual
12:00395 msNormal
12:30274 msNormal
13:00298 msNormal
13:30504 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.