Azure Ping Test

Find your closest, lowest-latency Azure region. Test latency to every commercial Azure region from your browser. Catches Front Door routing, no Azure subscription needed.

40 Azure regions measured · browser-based · no signup

40regions
  • Azure
    Australia East
    australiaeastSydney, AU
  • Azure
    Australia Southeast
    australiasoutheastMelbourne, AU
  • Azure
    Brazil South
    brazilsouthSão Paulo, BR
  • Azure
    Canada Central
    canadacentralToronto, CA
  • Azure
    Canada East
    canadaeastQuebec, CA
  • Azure
    Central India
    centralindiaPune, IN
  • Azure
    Central US
    centralusIowa, US
  • Azure
    East Asia
    eastasiaHong Kong, HK
  • Azure
    East US
    eastusVirginia, US
  • Azure
    East US 2
    eastus2Virginia, US
  • Azure
    France Central
    francecentralParis, FR
  • Azure
    Germany West Central
    germanywestcentralFrankfurt, DE
  • Azure
    Israel Central
    israelcentralTel Aviv, IL
  • Azure
    Italy North
    italynorthMilan, IT
  • Azure
    Japan East
    japaneastTokyo, JP
  • Azure
    Japan West
    japanwestOsaka, JP
  • Azure
    Korea Central
    koreacentralSeoul, KR
  • Azure
    Malaysia West
    malaysiawestKuala Lumpur, MY
  • Azure
    North Central US
    northcentralusIllinois, US
  • Azure
    North Europe
    northeuropeDublin, IE
  • Azure
    Norway East
    norwayeastOslo, NO
  • Azure
    Poland Central
    polandcentralWarsaw, PL
  • Azure
    Qatar Central
    qatarcentralDoha, QA
  • Azure
    South Africa North
    southafricanorthJohannesburg, ZA
  • Azure
    South Central US
    southcentralusTexas, US
  • Azure
    Southeast Asia
    southeastasiaSingapore, SG
  • Azure
    South India
    southindiaChennai, IN
  • Azure
    Spain Central
    spaincentralMadrid, ES
  • Azure
    Sweden Central
    swedencentralGävle, SE
  • Azure
    Switzerland North
    switzerlandnorthZurich, CH
  • Azure
    Switzerland West
    switzerlandwestGeneva, CH
  • Azure
    Taiwan North
    taiwannorthTaipei, TW
  • Azure
    UAE North
    uaenorthDubai, AE
  • Azure
    UK South
    uksouthLondon, UK
  • Azure
    UK West
    ukwestCardiff, UK
  • Azure
    West Central US
    westcentralusWyoming, US
  • Azure
    West Europe
    westeuropeAmsterdam, NL
  • Azure
    West US
    westusCalifornia, US
  • Azure
    West US 2
    westus2Washington, US
  • Azure
    West US 3
    westus3Arizona, US

Frequently asked questions

Everything below is the precise methodology behind the numbers on this page.

What is an Azure ping test?
An Azure ping test measures the round-trip latency between your browser and an Azure public endpoint in each region. Unlike ICMP ping (which browsers can't send), it issues HTTPS HEAD requests so it works without local tools or an Azure subscription. Lower numbers point to the Azure region that will give your users the lowest latency for App Service, Azure Functions, AKS, and similar workloads.
How does this Azure ping test measure latency?
regionping pings the regional Azure Machine Learning API (https://{region}.api.azureml.ms) — chosen after curl-testing 16 Azure subdomain patterns because it has GA coverage in 40 commercial regions with consistent latency profiles. The numbers reflect the path through Azure's regional ingress that your browser actually traverses. Five 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.