Cloudflare logo

Cloudflare Clef slowdown on 12 November 2026

Cloudflare Clef full response from Tokyo: slower than usual; 2026-11-12 22:30 UTC to 2026-11-13 00:00 UTC: peak full response 558 ms vs a usual 368 ms.

What our checks saw
Slower than usual
Cities affected
Tokyo
When
to
How long
90 minutes
Slowest check
558 ms, usually 368 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 ms500 ms1.00 s19:3022:3001:30
Each check (UTC)Usual (367 ms)Slow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
19:30386 msNormal
20:00611 msSlower than usual
20:30334 msNormal
21:00761 msSlower than usual
21:30409 msNormal
22:00826 msSlower than usual
22:30290 msNormal
23:00350 msNormal
23:30276 msNormal
00:00331 msNormal
00:30340 msNormal
01:00316 msNormal
01:30283 msNormal
02:00785 msSlower than usual
02:30346 msNormal
03:00351 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.