AWS Latency Test
Measure network latency from your location to AWS data centers worldwide. To compare with Azure regions, visit Azure Latency Test .
Getting started
1 Choose the AWS regions to test.
2 Let the latency check run for a few samples.
3 Review the recommended regions below.
0 / 34 regions selected
Americas
Europe
Middle East and Africa
Australia and New Zealand
Recommended AWS Regions
Waiting for region selection…
Pick at least one AWS region above to see the best performing locations.
AWS Latency Test Results
No latency samples yet
Choose one or more regions above. We start the test automatically and stream results here.
Important note
This browser test helps compare latency across AWS regions. Results are indicative and may differ from production workloads. For deeper analysis, consider command-line tools such as 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 AWS test 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 AWS Latency Test work?
Your browser sends HTTPS requests to AWS resources hosted in each region. The median latency is calculated by measuring the time between the request and the response.
Why might my AWS Latency Test result differ from my PsPing result?
The AWS Latency Test measures latency using HTTPS requests to AWS endpoints, 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 AWS Latency Test.
Why are some AWS regions not listed?
Some regions may not appear due to special access requirements or restrictions. Examples include AWS GovCloud (US) and AWS China regions, which require separate accounts and may have additional compliance prerequisites. A complete list of AWS regions is available on the AWS Global Infrastructure site. These restricted partitions are not currently supported by this test.
Additionally, some regions might be too new and not yet included in the test. If you notice a recently announced region that is missing, please open an issue on GitHub .
Do you support upload, download tests, packet loss, and jitter?
This AWS Latency Test focuses on measuring HTTPS latency. Upload and download throughput benchmarks, along with packet loss and jitter measurements, are not supported at this time.