Made in / Donate

Linode ping test

Latency from your browser to every Linode (Linode (Akamai)) region (25), measured live, round after round. The fastest regions are greenest; click a column heading to sort.

Starting…

1 US East Newark newark – – – – –
2 US Central Dallas dallas – – – – –
3 US West Fremont fremont – – – – –
4 US Southeast Atlanta atlanta – – – – –
5 US-IAD Washington washington – – – – –
6 US-ORD Chicago chicago – – – – –
7 CA Central Toronto toronto1 – – – – –
8 EU West London london – – – – –
9 EU Central Frankfurt frankfurt – – – – –
10 FR-PAR Paris paris – – – – –
11 AP South Singapore singapore – – – – –
12 AP Northeast-2 Tokyo 2 tokyo2 – – – – –
13 AP West Mumbai mumbai1 – – – – –
14 AP-Southeast Sydney syd1 – – – – –
15 SE-STO Stockholm stockholm – – – – –
16 US-SEA Seattle seattle – – – – –
17 IT-MIL Milan milan – – – – –
18 JP-OSA Osaka osaka – – – – –
19 IN-MAA Chennai chennai – – – – –
20 ID-CGK Jakarta jakarta – – – – –
21 BR-GRU Sao Paulo sao-paulo – – – – –
22 NL-AMS Amsterdam amsterdam – – – – –
23 US-MIA Miami miami – – – – –
24 US-LAX Los Angeles los-angeles – – – – –
25 ES-MAD Madrid madrid – – – – –
  • How it's measured: your browser fetches a tiny file from each region in turn and times the reply. That is an HTTPS round trip, so it reads a little higher than a raw ping, but it ranks regions the same way.
  • The first round only warms up connections: it's shown, but the median, mean, min and max leave it out. A region that doesn't answer within 3 seconds counts as failed for that round.
  • Testing pauses while this tab is hidden, as browsers slow down background tabs and the times would be wrong.

Missing a provider or a region? Ask for it on GitHub.