Linode Ping Test
Find your closest, lowest-latency Linode region. Linode (Akamai Cloud) latency test from the browser. Hits per-region object storage for every Linode datacenter that runs it.
21 Linode regions measured · browser-based · no signup
21regions
- LinodeMelbourneau-melMelbourne, AU—
- LinodeSão Paulobr-gruSão Paulo, BR—
- LinodeFrankfurtde-fraFrankfurt, DE—
- LinodeMadrides-madMadrid, ES—
- LinodeParisfr-parParis, FR—
- LinodeLondongb-lonLondon, UK—
- LinodeJakartaid-cgkJakarta, ID—
- LinodeMumbaiin-bomMumbai, IN—
- LinodeChennaiin-maaChennai, IN—
- LinodeMilanit-milMilan, IT—
- LinodeOsakajp-osaOsaka, JP—
- LinodeAmsterdamnl-amsAmsterdam, NL—
- LinodeStockholmse-stoStockholm, SE—
- LinodeSingaporesg-sinSingapore, SG—
- LinodeNewarkus-eastNewark, NJ, US—
- LinodeWashington DCus-iadWashington DC, US—
- LinodeLos Angelesus-laxLos Angeles, CA, US—
- LinodeMiamius-miaMiami, FL, US—
- LinodeChicagous-ordChicago, IL, US—
- LinodeSeattleus-seaSeattle, WA, US—
- LinodeAtlantaus-southeastAtlanta, GA, US—
| # | Provider | Region | Location | Latency |
|---|---|---|---|---|
| Linode | Melbourne au-mel | Melbourne, AU | — | |
| Linode | São Paulo br-gru | São Paulo, BR | — | |
| Linode | Frankfurt de-fra | Frankfurt, DE | — | |
| Linode | Madrid es-mad | Madrid, ES | — | |
| Linode | Paris fr-par | Paris, FR | — | |
| Linode | London gb-lon | London, UK | — | |
| Linode | Jakarta id-cgk | Jakarta, ID | — | |
| Linode | Mumbai in-bom | Mumbai, IN | — | |
| Linode | Chennai in-maa | Chennai, IN | — | |
| Linode | Milan it-mil | Milan, IT | — | |
| Linode | Osaka jp-osa | Osaka, JP | — | |
| Linode | Amsterdam nl-ams | Amsterdam, NL | — | |
| Linode | Stockholm se-sto | Stockholm, SE | — | |
| Linode | Singapore sg-sin | Singapore, SG | — | |
| Linode | Newark us-east | Newark, NJ, US | — | |
| Linode | Washington DC us-iad | Washington DC, US | — | |
| Linode | Los Angeles us-lax | Los Angeles, CA, US | — | |
| Linode | Miami us-mia | Miami, FL, US | — | |
| Linode | Chicago us-ord | Chicago, IL, US | — | |
| Linode | Seattle us-sea | Seattle, WA, US | — | |
| Linode | Atlanta us-southeast | Atlanta, GA, US | — |
Frequently asked questions
Everything below is the precise methodology behind the numbers on this page.
What is a Linode ping test?
A Linode (Akamai Cloud) ping test measures the round-trip latency between your browser and a Linode public endpoint in each datacenter. It runs entirely in the browser via HTTPS HEAD requests, so no Linode account or local tools are required. Lower numbers point to the Linode datacenter that will give your Compute Instances, NodeBalancers, and managed databases the lowest user-perceived latency.
How does this Linode ping test measure latency?
regionping pings Linode's object storage endpoints (https://{region}-1.linodeobjects.com), now operated as part of Akamai Cloud Computing after the 2022 acquisition. The result reflects the network path through Akamai's edge fabric to the Linode datacenter. Five timed HEAD samples per region, drop high and low, median of three, up to 16 regions in parallel.
How does regionping measure latency?
Your browser sends one warmup HEAD request per region to prime DNS, TCP, and TLS, then issues five timed HEAD requests. The highest and lowest samples are dropped and the median of the remaining three is shown. Up to 16 regions are measured in parallel.
Why are the numbers higher than what ICMP ping shows?
regionping runs inside a browser, which cannot send ICMP packets. Every sample is an HTTPS HEAD request, so the measured time includes TCP and TLS overhead. Expect regionping numbers to sit roughly 10–30 ms above ICMP ping from the same machine. The ordering between regions is still faithful, which is what matters when choosing one.
Which cloud providers and regions are supported?
AWS (32 regions), Google Cloud (41 regions), Azure (40 regions), Oracle Cloud (37 regions), DigitalOcean (10 regions), IBM Cloud (12 regions), Alibaba Cloud (29 regions), Linode (21 regions), OVHcloud (8 regions), Vultr (10 regions), Hetzner (3 regions), Huawei Cloud (26 regions), Exoscale (7 regions), Scaleway (4 regions), Gcore (3 regions), and Contabo (3 regions). 286 public regions in total.
What do the green, yellow, and red latency values mean?
Green (under 80 ms) is what you want for interactive workloads — API calls, real-time messaging, game servers. Yellow (80–149 ms) is acceptable for most web apps but noticeable in chatty request patterns. Red (150 ms and above) signals a region that is likely far from your network path; usable for batch and background jobs but a poor choice for anything user-interactive.
Why did a region return “failed”?
Most common causes, in roughly decreasing order of likelihood: a corporate firewall or enterprise proxy blocking the provider domain, an active VPN routing the request through a path that drops it, ISP-level blocks on cloud object-storage hostnames, the provider not yet deploying (or having deprecated) the public endpoint in that region, or a browser extension such as an ad blocker or privacy tool intercepting the request. Failures are surfaced explicitly instead of hidden so you can cross-check from a different network.