Azure latency test
Measure network latency from your IP location to Azure datacenters worldwide and find the best region for your location. To compare with AWS regions, visit AWS Latency Test .
Latency test
Europe
North America
Asia
Australia and New Zealand
Middle East and Africa
South America
Recommended Azure regions
Select 2+ regions above to compare and find out
- Network
- Location
- IP
Important note
Important note
This site gives a quick, indicative view of latency to Azure regions from your location, use it for initial guidance, not for SLAs or final performance decisions. 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 storage files in each region. The median latency is calculated by measuring the time between the request and the response.
Do you support upload, download tests, packet loss, and jitter?
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 .