Akamai Cloud Ping Test
Find your closest, lowest-latency Akamai Cloud region. Akamai Cloud (Linode) latency test from your browser using regional Object Storage endpoints.
23 Akamai Cloud regions measured · browser-based · no signup
23regions
- Akamai CloudMelbourneau-melMelbourne, AU—
- Akamai CloudSão Paulobr-gruSão Paulo, BR—
- Akamai CloudFrankfurt 2de-fra-2Frankfurt, DE—
- Akamai CloudMadrides-madMadrid, ES—
- Akamai CloudParisfr-parParis, FR—
- Akamai CloudLondongb-lonLondon, UK—
- Akamai CloudJakartaid-cgkJakarta, ID—
- Akamai CloudMumbai 2in-bom-2Mumbai, IN—
- Akamai CloudChennaiin-maaChennai, IN—
- Akamai CloudMilanit-milMilan, IT—
- Akamai CloudOsakajp-osaOsaka, JP—
- Akamai CloudTokyo 3jp-tyo-3Tokyo, JP—
- Akamai CloudAmsterdamnl-amsAmsterdam, NL—
- Akamai CloudStockholmse-stoStockholm, SE—
- Akamai CloudSingapore 2sg-sin-2Singapore, SG—
- Akamai CloudNewarkus-eastNewark, NJ, US—
- Akamai CloudWashington DCus-iadWashington DC, US—
- Akamai CloudWashington DC 2us-iad-2Washington DC, US—
- Akamai CloudLos Angelesus-laxLos Angeles, CA, US—
- Akamai CloudMiamius-miaMiami, FL, US—
- Akamai CloudChicagous-ordChicago, IL, US—
- Akamai CloudSeattleus-seaSeattle, WA, US—
- Akamai CloudAtlantaus-southeastAtlanta, GA, US—
| # | Provider | Region | Location | Latency |
|---|---|---|---|---|
| Akamai Cloud | Melbourne au-mel | Melbourne, AU | — | |
| Akamai Cloud | São Paulo br-gru | São Paulo, BR | — | |
| Akamai Cloud | Frankfurt 2 de-fra-2 | Frankfurt, DE | — | |
| Akamai Cloud | Madrid es-mad | Madrid, ES | — | |
| Akamai Cloud | Paris fr-par | Paris, FR | — | |
| Akamai Cloud | London gb-lon | London, UK | — | |
| Akamai Cloud | Jakarta id-cgk | Jakarta, ID | — | |
| Akamai Cloud | Mumbai 2 in-bom-2 | Mumbai, IN | — | |
| Akamai Cloud | Chennai in-maa | Chennai, IN | — | |
| Akamai Cloud | Milan it-mil | Milan, IT | — | |
| Akamai Cloud | Osaka jp-osa | Osaka, JP | — | |
| Akamai Cloud | Tokyo 3 jp-tyo-3 | Tokyo, JP | — | |
| Akamai Cloud | Amsterdam nl-ams | Amsterdam, NL | — | |
| Akamai Cloud | Stockholm se-sto | Stockholm, SE | — | |
| Akamai Cloud | Singapore 2 sg-sin-2 | Singapore, SG | — | |
| Akamai Cloud | Newark us-east | Newark, NJ, US | — | |
| Akamai Cloud | Washington DC us-iad | Washington DC, US | — | |
| Akamai Cloud | Washington DC 2 us-iad-2 | Washington DC, US | — | |
| Akamai Cloud | Los Angeles us-lax | Los Angeles, CA, US | — | |
| Akamai Cloud | Miami us-mia | Miami, FL, US | — | |
| Akamai Cloud | Chicago us-ord | Chicago, IL, US | — | |
| Akamai Cloud | Seattle us-sea | Seattle, WA, US | — | |
| Akamai Cloud | 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 Akamai Cloud Object Storage hosts under linodeobjects.com, using the published endpoint for each region. Endpoint suffixes vary, for example us-ord-10.linodeobjects.com for Chicago and us-iad-18.linodeobjects.com for Washington DC 2. 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 (33 regions), Google Cloud (43 regions), Azure (40 regions), Oracle Cloud (43 regions), DigitalOcean (13 regions), IBM Cloud (13 regions), Alibaba Cloud (30 regions), Akamai Cloud (23 regions), OVHcloud (13 regions), Vultr (14 regions), Hetzner (3 regions), Huawei Cloud (26 regions), Exoscale (8 regions), Scaleway (4 regions), Gcore (3 regions), Contabo (3 regions), Tencent Cloud (17 regions), IONOS Cloud (4 regions), and Backblaze B2 (4 regions). 337 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.