Cloudflare Clef slowdown on 14 October 2026

Cloudflare Clef full response from Amsterdam, San Francisco, Tokyo, Montreal: slower than usual; 2026-10-14 17:30 UTC to 2026-10-14 21:00 UTC: peak full response 1.86 s vs a usual 0.43 s.

What our checks saw: Slower than usual
Cities affected: Amsterdam, San Francisco, Tokyo, Montreal
When: 14 Oct, 17:30 UTC to 14 Oct, 21:00 UTC
How long: 3.5 hours
Slowest check: 1.86 s, usually 430 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: Singapore, Mumbai.

Amsterdam

Each check (UTC)Usual (329 ms)Slower than usualSlow check outside the incidentIncident

Every check as a table

Time (UTC)	Check	Reading
14:30	543 ms	Slower than usual
15:00	378 ms	Normal
15:30	447 ms	Normal
16:00	424 ms	Normal
16:30	422 ms	Normal
17:00	823 ms	Much slower, or failing
17:30	628 ms	Slower than usual
18:00	491 ms	Normal
18:30	486 ms	Normal
19:00	368 ms	Normal
19:30	377 ms	Normal
20:00	319 ms	Normal
20:30	389 ms	Normal
21:00	346 ms	Normal
21:30	265 ms	Normal
22:00	387 ms	Normal
22:30	304 ms	Normal
23:00	936 ms	Much slower, or failing
23:30	388 ms	Normal
00:00	534 ms	Slower than usual

San Francisco

Each check (UTC)Usual (341 ms)Slower than usualIncident

Every check as a table

Time (UTC)	Check	Reading
14:30	456 ms	Normal
15:00	343 ms	Normal
15:30	374 ms	Normal
16:00	461 ms	Normal
16:30	313 ms	Normal
17:00	470 ms	Normal
17:30	610 ms	Slower than usual
18:00	282 ms	Normal
18:30	235 ms	Normal
19:00	730 ms	Slower than usual
19:30	360 ms	Normal
20:00	313 ms	Normal
20:30	329 ms	Normal
21:00	333 ms	Normal
21:30	369 ms	Normal
22:00	467 ms	Normal
22:30	289 ms	Normal
23:00	382 ms	Normal
23:30	293 ms	Normal
00:00	410 ms	Normal

Montreal

Each check (UTC)Usual (337 ms)Slower than usualIncident

Every check as a table

Time (UTC)	Check	Reading
14:30	203 ms	Normal
15:00	372 ms	Normal
15:30	258 ms	Normal
16:00	367 ms	Normal
16:30	363 ms	Normal
17:00	392 ms	Normal
17:30	680 ms	Slower than usual
18:00	497 ms	Normal
18:30	328 ms	Normal
19:00	330 ms	Normal
19:30	340 ms	Normal
20:00	345 ms	Normal
20:30	368 ms	Normal
21:00	249 ms	Normal
21:30	269 ms	Normal
22:00	408 ms	Normal
22:30	208 ms	Normal
23:00	360 ms	Normal
23:30	359 ms	Normal
00:00	259 ms	Normal

Tokyo

Each check (UTC)Usual (430 ms)Slower than usualMuch slower, or failingSlow check outside the incidentIncident

Every check as a table

Time (UTC)	Check	Reading
14:30	676 ms	Slower than usual
15:00	320 ms	Normal
15:30	585 ms	Normal
16:00	384 ms	Normal
16:30	306 ms	Normal
17:00	326 ms	Normal
17:30	1.49 s	Much slower, or failing
18:00	734 ms	Slower than usual
18:30	389 ms	Normal
19:00	3.32 s	Much slower, or failing
19:30	244 ms	Normal
20:00	317 ms	Normal
20:30	366 ms	Normal
21:00	645 ms	Normal
21:30	338 ms	Normal
22:00	965 ms	Slower than usual
22:30	296 ms	Normal
23:00	597 ms	Normal
23:30	276 ms	Normal
00:00	533 ms	Normal

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.