region·latency

Azure latency test

Round-trip time from your browser to every Microsoft Azure region — 60 of them, 20 in Europe, 14 in Asia, 12 in North America, 5 in Oceania, 4 in the Middle East, 3 in South America, 2 in Africa — each against the speed-of-light floor its distance sets, so a slow region is visibly far rather than badly routed.

Is this an Azure ping?

Every Azure region answers 401 on its live-diagnostics host — a control-plane host in two of them — and that 401, timed, is the closest a browser can get to an Azure ping. ICMP is not available to a web page at all. The status code does not matter to a stopwatch: the round trip is what is being measured.

How Azure is probed

{region}.livediagnostics.monitor.azure.com answers 401 from inside the region — every resolved IP was checked against that region's own Service Tags prefix. No CORS headers, so it is timed blind.

The first request of a sweep is discarded — it pays for DNS, TCP and TLS — so every sample after it is essentially one round trip, and the reported figure is the fastest of them.

Every Azure region

RegionCityCountryIPv4 prefixes
southafricawestCape TownZA263
southafricanorthJohannesburgZA418
koreasouthBusanKR311
southindiaChennaiIN375
eastasiaHong KongHK668
indiasouthcentralHyderabadIN125
indonesiacentralJakartaID203
jioindiawestJamnagarIN220
malaysiawestKuala LumpurMY198
jioindiacentralNagpurIN166
japanwestOsakaJP519
centralindiaPuneIN576
koreacentralSeoulKR461
southeastasiaSingaporeSG814
taiwannorthTaipeiTW210
japaneastTokyo, SaitamaJP639
westeuropeAmsterdamNL1,656
germanynorthBerlinDE279
belgiumcentralBrusselsBE156
ukwestCardiffGB541
denmarkeastCopenhagenDK151
northeuropeDublinIE1,393
germanywestcentralFrankfurtDE453
swedencentralGavleSE424
switzerlandwestGenevaCH293
uksouthLondonGB816
spaincentralMadridES238
francesouthMarseilleFR293
italynorthMilanIT278
norwayeastOsloNO368
francecentralParisFR606
swedensouthStaffanstorp (Malmo)SE187
norwaywestStavangerNO248
austriaeastViennaAT178
polandcentralWarsawPL268
switzerlandnorthZurichCH397
uaecentralAbu DhabiAE285
qatarcentralDohaQA251
uaenorthDubaiAE413
israelcentralTel AvivIL250
eastusBoydton, VirginiaUS1,700
eastus2Boydton, VirginiaUS1,902
westcentralusCheyenne, WyomingUS594
northcentralusChicago, IllinoisUS708
centralusDes Moines, IowaUS1,378
westus3Phoenix, ArizonaUS584
canadaeastQuebec City, QuebecCA403
mexicocentralQueretaroMX219
westus2Quincy, WashingtonUS1,012
southcentralusSan Antonio, TexasUS1,233
westusSan Francisco Bay Area, CaliforniaUS1,440
canadacentralToronto, OntarioCA613
newzealandnorthAucklandNZ219
australiacentralCanberra, ACTAU213
australiacentral2Canberra, ACTAU182
australiasoutheastMelbourne, VICAU571
australiaeastSydney, NSWAU662
brazilsoutheastRio de JaneiroBR239
chilecentralSantiagoCL183
brazilsouthSao PauloBR558

Prefix counts come from Azure’s own published feed. Each region links to its distance, its physical floor and the endpoint used to time it.

Measure it yourself

Open the instrument, select Azure, choose regions and run a sweep. Nothing is pre-selected and nothing runs until you press the button.