AWS Speed Test
AWS Speed Test

AWS Latency Test

Measure network latency from your location to AWS datacenters worldwide. To compare with Azure regions, visit Azure Latency Test .

Testing Instructions:
  1. Select one or more AWS regions below.
  2. Wait for the results to appear below.
  3. Review the recommended regions and latency chart.
Please select at least one region to start test.
Asia Pacific
Americas
Europe
Middle East and Africa
Australia and New Zealand

Recommended AWS Regions

Waiting for region selection...
Select regions above to see your closest AWS datacenters.

AWS Latency Test Results

No results yet
Select regions and wait for the test to complete.
Important Note: This site enables easy AWS 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, consider command-line tools such as PsPing Network Latency Test .

Frequently Asked Questions

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.

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.

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.

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 .

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.