Benchmark report

Cloudflare thumbnail

Ping and load times to cloudflare.com from 6 cities

Mixed by location

Response times ranged from 57 ms in Montreal to 281 ms in Singapore. Where you are matters.

Fastest
57 ms
Montreal
Slowest
281 ms
Singapore
Successful requests
100%
6 locations

Response time around the world

Amsterdam 85ms typicalSan Francisco 136ms typicalMontreal 57ms typicalSingapore 281ms typicalTokyo 197ms typicalMumbai 240ms typical
  • CanadaMontreal
    57 ms
  • NetherlandsAmsterdam
    85 ms
  • United StatesSan Francisco
    136 ms
  • JapanTokyo
    197 ms
  • IndiaMumbai
    240 ms
  • SingaporeSingapore
    281 ms

Why is Singapore slower?

Every city was answered by a Cloudflare server in or near it, London for Amsterdam, San Jose for San Francisco and local ones in Montreal, Singapore, Tokyo and Mumbai, so distance doesn’t explain it. Connecting took 2 to 9 ms and the secure connection 5 to 11 ms everywhere in the controlled run of 4 October. The difference is the wait before the first byte of the 1.3 MB page: 26 ms in Amsterdam, 48 ms in Montreal, 109 ms in San Francisco, 180 ms in Tokyo, 220 ms in Mumbai and 256 ms in Singapore. From outside we can’t see whether each of those servers had the page in its cache or fetched it first.

Click the location to see each stage.

ConnectTLSServer waitDownload
SingaporeSingapore
274 ms
Finding the server
3 ms
Reaching the server
3 ms
Setting up security
5 ms
Waiting for the server: most of the time
256 ms
Receiving the response
10 ms
Total
274 ms

Finding the server is measured once per location, so it sits outside these bars. Open a city to see it.

Bars show the typical request, so the parts add up to its total. Why

Compare all locations

Click a city to see its stage-by-stage breakdown.

ConnectTLSServer waitDownload
NetherlandsAmsterdam
77 ms
Finding the server
1 ms
Reaching the server
9 ms
Setting up security
11 ms
Waiting for the server
26 ms
Receiving the response: most of the time
31 ms
Total
77 ms
United StatesSan Francisco
136 ms
Finding the server
13 ms
Reaching the server
5 ms
Setting up security
8 ms
Waiting for the server: most of the time
109 ms
Receiving the response
14 ms
Total
136 ms
CanadaMontreal
64 ms
Finding the server
2 ms
Reaching the server
2 ms
Setting up security
6 ms
Waiting for the server: most of the time
48 ms
Receiving the response
8 ms
Total
64 ms
SingaporeSingapore
274 ms
Finding the server
3 ms
Reaching the server
3 ms
Setting up security
5 ms
Waiting for the server: most of the time
256 ms
Receiving the response
10 ms
Total
274 ms
JapanTokyo
197 ms
Finding the server
1 ms
Reaching the server
2 ms
Setting up security
7 ms
Waiting for the server: most of the time
180 ms
Receiving the response
8 ms
Total
197 ms
IndiaMumbai
242 ms
Finding the server
3 ms
Reaching the server
3 ms
Setting up security
7 ms
Waiting for the server: most of the time
220 ms
Receiving the response
12 ms
Total
242 ms

The phases come from the controlled run of 4 October 2026. Typical and slower times pool the daily requests. 6 of 6 test locations included: Amsterdam, San Francisco, Montreal, Singapore, Tokyo, Mumbai.

Finding the server is measured once per location, so it sits outside these bars. Open a city to see it.

Bars show the typical request, so the parts add up to its total. Why

Cloudflare still feels slow?

Check Cloudflare’s status page
Edge incidents are posted per location there. If your city is listed, that explains a slow result better than this page can.
This is not a benchmark of your site on Cloudflare
Your site’s speed on Cloudflare depends on your cache rules, your origin and your plan. Workers, R2, the 1.1.1.1 resolver and the dashboard are separate systems again.
Ping is the connection time
A ping times one round trip. The closest number here is the connection time, 2 to 9 ms in every city we test from. When cloudflare.com loads slowly, the time goes to waiting for the page; the network to Cloudflare stays fast.

Response time over the last 30 days

Daily median of 5 requests per location, 21 September 2026 to 20 October 2026.
010002000 ms21 Sept20 OctTokyo, 18 October 2026: 1075 ms, well above its usual level.

A dot marks a day well above that location’s usual level.

Show the numbers
DayAmsterdamSan FranciscoMontrealSingaporeTokyoMumbai
21 September 202684 ms139 ms56 ms281 ms187 ms242 ms
22 September 202673 ms149 ms58 ms319 ms199 ms249 ms
23 September 202675 ms134 ms54 ms290 ms195 ms264 ms
24 September 202696 ms164 ms64 ms299 ms196 ms251 ms
25 September 202673 ms132 ms52 ms293 ms193 ms247 ms
26 September 202676 ms133 ms56 ms277 ms199 ms235 ms
28 September 202680 ms134 ms59 ms290 ms192 ms239 ms
29 September 202687 ms136 ms53 ms277 ms216 ms244 ms
30 September 202674 ms130 ms64 ms273 ms195 ms239 ms
1 October 202681 ms128 ms57 ms274 ms196 ms254 ms
2 October 202688 ms150 ms62 ms269 ms195 ms226 ms
3 October 202686 ms128 ms59 ms264 ms196 ms234 ms
4 October 202686 ms126 ms54 ms281 ms188 ms233 ms
5 October 202687 ms133 ms60 ms279 ms197 ms233 ms
6 October 202679 ms138 ms53 ms264 ms191 ms230 ms
7 October 202686 ms133 ms54 ms272 ms193 ms260 ms
9 October 202684 ms124 ms56 ms281 ms196 ms248 ms
10 October 202684 ms137 ms56 ms275 ms202 ms260 ms
11 October 202687 ms135 ms50 ms271 ms197 ms240 ms
12 October 202688 ms137 ms68 ms288 ms202 ms235 ms
13 October 202690 ms135 ms63 ms282 ms192 ms231 ms
14 October 202686 ms136 ms56 ms273 ms196 ms243 ms
15 October 202673 ms132 ms67 ms287 ms199 ms240 ms
16 October 202679 ms150 ms58 ms337 ms192 ms234 ms
17 October 202688 ms144 ms55 ms290 ms200 ms243 ms
18 October 202680 ms131 ms53 ms269 ms1075 ms ▲232 ms
19 October 202686 ms137 ms63 ms288 ms205 ms229 ms
20 October 202679 ms139 ms64 ms271 ms195 ms230 ms

About this measurement

GET www.cloudflare.com · 63 to 65 requests per location over 13 daily runs · 7 October 2026 to 20 October 2026

What we tested · Marketing website. The www.cloudflare.com marketing homepage, a 1.3 MB HTML document served from Cloudflare's own edge cache.

How LatencyRadar measures response time →Also measured: Cloudflare Clef →

Technical details

Doesn’t measure: The CDN edge that serves your zone, Workers, 1.1.1.1 or the dashboard. A cdnjs asset surface is planned.

This page covers one Cloudflare surface: the www.cloudflare.com marketing homepage, a 1.3 MB HTML document that Cloudflare serves from its own edge. It shows how a Cloudflare server near each of our cities answers a cold request for that page. It does not tell you how Cloudflare serves your site, which depends on your cache rules, origin and plan. A small CSS file on cdnjs is also in our catalog as a separate request; it has no report yet. Workers, R2, the dashboard, WARP and the 1.1.1.1 resolver are not measured here.

Between 7 and 20 October 2026 the typical time was 57 ms in Montreal and 85 ms in Amsterdam, 136 ms in San Francisco, 197 ms in Tokyo, 240 ms in Mumbai and 281 ms in Singapore. If you came here for the ping to cloudflare.com, the connection itself took 2 to 9 ms in every city in the controlled run, which is about one round trip. The daily medians barely moved: Amsterdam stayed between 73 and 90 ms, San Francisco between 124 and 150 ms, Mumbai between 229 and 260 ms and Singapore between 269 and 337 ms. Tokyo was steady at 192 to 205 ms except on 18 October, when its median was 1,075 ms. That one day is why Tokyo’s slower time, which 95% of requests finished within, is 1,026 ms; on the other twelve days no Tokyo median passed 205 ms.

Test locationTypical response timeSlower response timeRequests
Amsterdam85 ms106 ms64
San Francisco136 ms165 ms65
Montreal57 ms82 ms65
Singapore281 ms400 ms63
Tokyo197 ms1026 ms65
Mumbai240 ms266 ms63

Typical: half of the requests finished within this time (technical: p50). Slower: 95% of requests finished within this time (technical: p95). Statistics

Request
GET www.cloudflare.com
Measured from
Amsterdam · San Francisco · Montreal · Singapore · Tokyo · Mumbai
Requests
Daily measurements from 7 October 2026 to 20 October 2026. 6 of 6 test locations included: Amsterdam, San Francisco, Montreal, Singapore, Tokyo, Mumbai. · 7 October 2026 to 20 October 2026
Timings taken
DNS, connect, TLS, waiting for the server, download
Report coverage
6 of 6 test locations included: Amsterdam, San Francisco, Montreal, Singapore, Tokyo, Mumbai.
Daily requests in each location
Amsterdam: 64 · San Francisco: 65 · Montreal: 65 · Singapore: 63 · Tokyo: 65 · Mumbai: 63
Typical response time
Median of the eligible daily requests in each included location.
Slower response time
The 95th percentile of the same eligible daily requests in each included location.

Cloudflare website

https://www.cloudflare.com/

Independent measurement by LatencyRadar. Not affiliated with Cloudflare. · How we measure (v1.3)

How fast does your site load 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 site

No account required · Takes about 30 seconds.

More benchmarks

All benchmarks →