Cloudflare logo

Cloudflare Clef slowdown on 13 November 2026

Cloudflare Clef full response from Tokyo: slower than usual; 2026-11-13 15:00 UTC to 2026-11-13 18:30 UTC: peak full response 730 ms vs a usual 366 ms.

What our checks saw
Slower than usual
Cities affected
Tokyo
When
to
How long
3.5 hours
Slowest check
730 ms, usually 366 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 s12:0015:0018:0021:00
Each check (UTC)Usual (366 ms)Slower than usualSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
12:00381 msNormal
12:30327 msNormal
13:00374 msNormal
13:30508 msNormal
14:00750 msSlower than usual
14:30636 msSlower than usual
15:00644 msSlower than usual
15:30364 msNormal
16:00686 msSlower than usual
16:30773 msSlower than usual
17:00486 msNormal
17:30499 msNormal
18:00326 msNormal
18:30207 msNormal
19:001.01 sMuch slower, or failing
19:30339 msNormal
20:00343 msNormal
20:30542 msNormal
21:00465 msNormal
21:30355 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.