Azure Latency Test
Test network latency from your IP location to Azure datacenters worldwide. Choose the datacenter closest to you and your clients for better performance. To compare with AWS regions, visit AWS Latency Test .
Testing steps
1 Select your Azure regions. 2 Let the latency check run. 3 Review the recommended regions.
Azure region groups
0 / 46 regions selected
Europe
Asia Pacific
Australia and New Zealand
Middle East and Africa
Recommended Azure Regions
No recommendations yet
Pick at least one region above. We surface the top matches once the first latency samples arrive.
Azure Latency Test Results
No latency results yet
Choose one or more regions above. We start the test automatically and stream results here once data is collected.
Important Note: This site enables easy Azure network connectivity testing in your browser. It compares latency across regions but does not measure the absolute lowest latency. Results are indicative. For more accurate measurements, visit PsPing Network Latency Test
Frequently asked questions
What is latency and what constitutes good latency?
Latency , often referred to as ping, is the duration for data to travel from the source to the destination and back. The results of this test represent the median round trip time (RTT) latency to Azure storage endpoints, with lower RTT indicating superior performance.
What constitutes good latency? Good latency varies by application type:
- Real-time applications (e.g., gaming, video conferencing): latency below 50 ms is ideal.
- Interactive applications (e.g., web browsing, online trading): latency between 50 ms and 100 ms is usually acceptable.
- Non-interactive applications (e.g., file transfers, backups): latency above 100 ms may be acceptable.
These guidelines may vary depending on specific application needs and user expectations.
How does Azure Latency Test work?
Your browser sends HTTPS requests to Azure blob files in each region. The median latency is calculated by measuring the time between the request and the response.
Why might my Azure Latency Test result differ from my PSPing result?
The Azure Latency Test measures latency using HTTPS requests to Azure blob storage, whereas PSPing measures TCP or ICMP echo requests. The two methods may yield different results due to varying protocols, network paths, and the nature of the tests. HTTPS requests involve more overhead compared to simple echo requests, which can lead to higher latencies in the Azure Latency Test.
Why are some Azure regions not listed?
Some regions may not appear due to special access requirements or restrictions for certain users or organizations. For example, US government regions require approval from the US government, and the Australia Central region is limited to Australian and New Zealand government organizations and their partners. Additionally, some regions might be too new and not yet included in the test. If you notice a missing recently announced region, please open an issue on GitHub .