Quick Ping: aws
Real-time latency testing to aws.amazon.com
Ping Test - aws.amazon.com
Test network latency and connection quality
AWS Ping Test
This test measures latency from seven independent global test nodes — six in Europe and one in Australia — to AWS public endpoints. Because AWS serves traffic through anycast and CDN edge locations, the numbers reflect the quality of the path from those nodes to the AWS network edge. They are not a direct measurement of the latency you would see from your own device.
Even so, the same global network that answers this test also carries traffic for EC2, S3, CloudFront and Route 53, so a poor result here is a strong hint that something on the path toward AWS is congested or degraded.
Why Test AWS Ping?
- Global Reach: See how well AWS edge locations are reachable from different parts of the world.
- Region Selection: Compare reachability to help decide which AWS region is closest to your users.
- CDN Performance: Verify that the network path to CloudFront endpoints is healthy and consistent.
- Application Troubleshooting: Confirm whether latency to AWS, rather than your application code, is behind slow responses.
- Hybrid Connectivity: Sanity-check the path toward AWS before investing in dedicated links such as Direct Connect.
How to Run the AWS Ping Test
- Use the default target (aws.amazon.com), or replace it with one of your own regional endpoints or service IPs.
- Start the test and let it run for a few seconds so each node can send several probes.
- Read the results per node, rather than focusing on only the fastest or slowest single number.
What the Results Mean
Latency is the round-trip time between a test node and the AWS network edge. A healthy path gives you stable, low numbers; results that swing wildly or sit consistently in the red deserve a closer look. As a rough guide:
- Under 60 ms (green): a healthy, fast path to the AWS edge.
- 60–120 ms (teal): acceptable, and typical over longer geographic distances.
- 120–200 ms (yellow): noticeably high; check routing or local congestion.
- Over 200 ms (red): poor; expect slow API calls and downloads.
Packet loss above 0 is a real warning sign — even a small percentage means some requests never arrive and must be retried. Because AWS is served from a global edge network, the latency measured here describes the network path, not how quickly AWS itself processes a request.
When This Test Is Not Enough
This test uses ICMP pings, which only check reachability and basic round-trip time — they do not measure application-level performance such as TLS handshakes, throughput or API latency. Some providers rate-limit or block ICMP entirely, so a failed probe does not always mean a service is unreachable. To measure the latency of your own connection, run a ping to the same endpoint from your local machine. For intermittent problems, a packet loss or jitter test will reveal far more than a single ping average.