Azure latency test
Measure network latency from your IP location to Azure datacenters worldwide and compare selected regions by median latency from your connection. To compare with AWS regions, visit AWS Latency Test .
Latency test
Test Steps
- Select regions
- Wait ~15 seconds
- Scroll down to review results
Europe
North America
Asia
Australia and New Zealand
Middle East and Africa
South America
Lowest-latency Azure regions
Latency-only ranking
This ranking compares median browser-to-Azure Blob Storage HTTPS latency from your current connection. It does not evaluate service availability, data residency, pricing, capacity, or application architecture. Use it as initial guidance, not as the sole basis for choosing a region. For a lower-overhead network measurement, visit PsPing Network Latency Test.
Select 2+ regions above to compare latency from your connection
Azure latency test results
No regions selected.
No latency data yet
Select regions above and wait for results to appear.
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.
Does the latency test reflect actual application performance?
Partially. This test is a network-focused indicator, not a full application benchmark.
- ✓ Good for comparing relative latency between Azure regions
- ✓ Useful for region-selection discussions
- ✗ Not a substitute for application-level load or performance testing
Use this test as a signal for initial guidance, not as the sole decision-maker.
Is my speed test result private?
Yes. AzureSpeed does not require authentication and does not collect personal or corporate identity information. Test results are generated entirely in your browser and are only visible to you. Other users cannot view, discover, or search for your results unless you explicitly share them (e.g., via screenshot). Results are not published, stored, or retained on our servers.
Do you support upload, download tests, packet loss, and jitter?
Run the Azure upload speed test or Run the Azure download speed test. Currently, measuring packet loss or jitter is not supported.
Why might my Azure Latency Test result differ from my PSPing result?
Browser-based latency tests include additional overhead that PSPing does not measure. This test uses HTTPS requests which include:
- DNS resolution time
- TLS/SSL handshake negotiation
- HTTP request/response header processing
- Browser JavaScript execution overhead
PSPing measures raw TCP or ICMP echo requests with minimal overhead. Expect browser results to be higher than PSPing. Both are valid — this test reflects real-world browser application latency, while PSPing shows pure network latency.
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 .