Benchmark report
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
Montreal
57 msAmsterdam
85 msSan Francisco
136 msTokyo
197 msMumbai
240 msSingapore
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.
Singapore274 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 locationsHide the comparison
Click a city to see its stage-by-stage breakdown.
Amsterdam77 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
San Francisco136 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
Montreal64 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
Singapore274 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
Tokyo197 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
Mumbai242 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
A dot marks a day well above that location’s usual level.
Show the numbers
| Day | Amsterdam | San Francisco | Montreal | Singapore | Tokyo | Mumbai |
|---|---|---|---|---|---|---|
| 21 September 2026 | 84 ms | 139 ms | 56 ms | 281 ms | 187 ms | 242 ms |
| 22 September 2026 | 73 ms | 149 ms | 58 ms | 319 ms | 199 ms | 249 ms |
| 23 September 2026 | 75 ms | 134 ms | 54 ms | 290 ms | 195 ms | 264 ms |
| 24 September 2026 | 96 ms | 164 ms | 64 ms | 299 ms | 196 ms | 251 ms |
| 25 September 2026 | 73 ms | 132 ms | 52 ms | 293 ms | 193 ms | 247 ms |
| 26 September 2026 | 76 ms | 133 ms | 56 ms | 277 ms | 199 ms | 235 ms |
| 28 September 2026 | 80 ms | 134 ms | 59 ms | 290 ms | 192 ms | 239 ms |
| 29 September 2026 | 87 ms | 136 ms | 53 ms | 277 ms | 216 ms | 244 ms |
| 30 September 2026 | 74 ms | 130 ms | 64 ms | 273 ms | 195 ms | 239 ms |
| 1 October 2026 | 81 ms | 128 ms | 57 ms | 274 ms | 196 ms | 254 ms |
| 2 October 2026 | 88 ms | 150 ms | 62 ms | 269 ms | 195 ms | 226 ms |
| 3 October 2026 | 86 ms | 128 ms | 59 ms | 264 ms | 196 ms | 234 ms |
| 4 October 2026 | 86 ms | 126 ms | 54 ms | 281 ms | 188 ms | 233 ms |
| 5 October 2026 | 87 ms | 133 ms | 60 ms | 279 ms | 197 ms | 233 ms |
| 6 October 2026 | 79 ms | 138 ms | 53 ms | 264 ms | 191 ms | 230 ms |
| 7 October 2026 | 86 ms | 133 ms | 54 ms | 272 ms | 193 ms | 260 ms |
| 9 October 2026 | 84 ms | 124 ms | 56 ms | 281 ms | 196 ms | 248 ms |
| 10 October 2026 | 84 ms | 137 ms | 56 ms | 275 ms | 202 ms | 260 ms |
| 11 October 2026 | 87 ms | 135 ms | 50 ms | 271 ms | 197 ms | 240 ms |
| 12 October 2026 | 88 ms | 137 ms | 68 ms | 288 ms | 202 ms | 235 ms |
| 13 October 2026 | 90 ms | 135 ms | 63 ms | 282 ms | 192 ms | 231 ms |
| 14 October 2026 | 86 ms | 136 ms | 56 ms | 273 ms | 196 ms | 243 ms |
| 15 October 2026 | 73 ms | 132 ms | 67 ms | 287 ms | 199 ms | 240 ms |
| 16 October 2026 | 79 ms | 150 ms | 58 ms | 337 ms | 192 ms | 234 ms |
| 17 October 2026 | 88 ms | 144 ms | 55 ms | 290 ms | 200 ms | 243 ms |
| 18 October 2026 | 80 ms | 131 ms | 53 ms | 269 ms | 1075 ms ▲ | 232 ms |
| 19 October 2026 | 86 ms | 137 ms | 63 ms | 288 ms | 205 ms | 229 ms |
| 20 October 2026 | 79 ms | 139 ms | 64 ms | 271 ms | 195 ms | 230 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 location | Typical response time | Slower response time | Requests |
|---|---|---|---|
| Amsterdam | 85 ms | 106 ms | 64 |
| San Francisco | 136 ms | 165 ms | 65 |
| Montreal | 57 ms | 82 ms | 65 |
| Singapore | 281 ms | 400 ms | 63 |
| Tokyo | 197 ms | 1026 ms | 65 |
| Mumbai | 240 ms | 266 ms | 63 |
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.
No account required · Takes about 30 seconds.