AWS Ping Test
Find your closest, lowest-latency AWS region. Browser-based ping test for every public AWS region. Five HEAD samples, median of three, no signup.
32 AWS regions measured · browser-based · no signup
32regions
- AWSAfrica (Cape Town)af-south-1Cape Town, ZA—
- AWSAsia Pacific (Hong Kong)ap-east-1Hong Kong, HK—
- AWSAsia Pacific (Tokyo)ap-northeast-1Tokyo, JP—
- AWSAsia Pacific (Seoul)ap-northeast-2Seoul, KR—
- AWSAsia Pacific (Osaka)ap-northeast-3Osaka, JP—
- AWSAsia Pacific (Mumbai)ap-south-1Mumbai, IN—
- AWSAsia Pacific (Hyderabad)ap-south-2Hyderabad, IN—
- AWSAsia Pacific (Singapore)ap-southeast-1Singapore, SG—
- AWSAsia Pacific (Sydney)ap-southeast-2Sydney, AU—
- AWSAsia Pacific (Jakarta)ap-southeast-3Jakarta, ID—
- AWSAsia Pacific (Melbourne)ap-southeast-4Melbourne, AU—
- AWSAsia Pacific (Malaysia)ap-southeast-5Kuala Lumpur, MY—
- AWSAsia Pacific (Thailand)ap-southeast-7Bangkok, TH—
- AWSCanada (Central)ca-central-1Montreal, CA—
- AWSCanada West (Calgary)ca-west-1Calgary, CA—
- AWSEurope (Frankfurt)eu-central-1Frankfurt, DE—
- AWSEurope (Zurich)eu-central-2Zurich, CH—
- AWSEurope (Stockholm)eu-north-1Stockholm, SE—
- AWSEurope (Milan)eu-south-1Milan, IT—
- AWSEurope (Spain)eu-south-2Madrid, ES—
- AWSEurope (Ireland)eu-west-1Dublin, IE—
- AWSEurope (London)eu-west-2London, UK—
- AWSEurope (Paris)eu-west-3Paris, FR—
- AWSIsrael (Tel Aviv)il-central-1Tel Aviv, IL—
- AWSMiddle East (UAE)me-central-1Dubai, AE—
- AWSMiddle East (Bahrain)me-south-1Manama, BH—
- AWSMexico (Central)mx-central-1Querétaro, MX—
- AWSSouth America (São Paulo)sa-east-1São Paulo, BR—
- AWSUS East (N. Virginia)us-east-1Ashburn, US—
- AWSUS East (Ohio)us-east-2Columbus, US—
- AWSUS West (N. California)us-west-1San Jose, US—
- AWSUS West (Oregon)us-west-2Boardman, US—
| # | Provider | Region | Location | Latency |
|---|---|---|---|---|
| AWS | Africa (Cape Town) af-south-1 | Cape Town, ZA | — | |
| AWS | Asia Pacific (Hong Kong) ap-east-1 | Hong Kong, HK | — | |
| AWS | Asia Pacific (Tokyo) ap-northeast-1 | Tokyo, JP | — | |
| AWS | Asia Pacific (Seoul) ap-northeast-2 | Seoul, KR | — | |
| AWS | Asia Pacific (Osaka) ap-northeast-3 | Osaka, JP | — | |
| AWS | Asia Pacific (Mumbai) ap-south-1 | Mumbai, IN | — | |
| AWS | Asia Pacific (Hyderabad) ap-south-2 | Hyderabad, IN | — | |
| AWS | Asia Pacific (Singapore) ap-southeast-1 | Singapore, SG | — | |
| AWS | Asia Pacific (Sydney) ap-southeast-2 | Sydney, AU | — | |
| AWS | Asia Pacific (Jakarta) ap-southeast-3 | Jakarta, ID | — | |
| AWS | Asia Pacific (Melbourne) ap-southeast-4 | Melbourne, AU | — | |
| AWS | Asia Pacific (Malaysia) ap-southeast-5 | Kuala Lumpur, MY | — | |
| AWS | Asia Pacific (Thailand) ap-southeast-7 | Bangkok, TH | — | |
| AWS | Canada (Central) ca-central-1 | Montreal, CA | — | |
| AWS | Canada West (Calgary) ca-west-1 | Calgary, CA | — | |
| AWS | Europe (Frankfurt) eu-central-1 | Frankfurt, DE | — | |
| AWS | Europe (Zurich) eu-central-2 | Zurich, CH | — | |
| AWS | Europe (Stockholm) eu-north-1 | Stockholm, SE | — | |
| AWS | Europe (Milan) eu-south-1 | Milan, IT | — | |
| AWS | Europe (Spain) eu-south-2 | Madrid, ES | — | |
| AWS | Europe (Ireland) eu-west-1 | Dublin, IE | — | |
| AWS | Europe (London) eu-west-2 | London, UK | — | |
| AWS | Europe (Paris) eu-west-3 | Paris, FR | — | |
| AWS | Israel (Tel Aviv) il-central-1 | Tel Aviv, IL | — | |
| AWS | Middle East (UAE) me-central-1 | Dubai, AE | — | |
| AWS | Middle East (Bahrain) me-south-1 | Manama, BH | — | |
| AWS | Mexico (Central) mx-central-1 | Querétaro, MX | — | |
| AWS | South America (São Paulo) sa-east-1 | São Paulo, BR | — | |
| AWS | US East (N. Virginia) us-east-1 | Ashburn, US | — | |
| AWS | US East (Ohio) us-east-2 | Columbus, US | — | |
| AWS | US West (N. California) us-west-1 | San Jose, US | — | |
| AWS | US West (Oregon) us-west-2 | Boardman, US | — |
Frequently asked questions
Everything below is the precise methodology behind the numbers on this page.
What is an AWS ping test?
An AWS ping test measures the round-trip latency between your browser and an AWS public endpoint in each region. Unlike ICMP ping (which browsers can't send), it issues HTTPS HEAD requests so it works without local tools or AWS credentials. Lower numbers point to the AWS region that will give your users the lowest latency for service calls like API Gateway, ALB, or DynamoDB.
How does this AWS ping test measure latency?
regionping pings the regional DynamoDB endpoint (https://dynamodb.{region}.amazonaws.com) — a globally available control-plane host that exists in every commercial and most government AWS regions. Your browser sends one warmup HEAD request to prime DNS, TCP, and TLS, then five timed HEAD requests; the highest and lowest are dropped and the median of the remaining three is shown. Up to 16 regions are measured in parallel.
How does regionping measure latency?
Your browser sends one warmup HEAD request per region to prime DNS, TCP, and TLS, then issues five timed HEAD requests. The highest and lowest samples are dropped and the median of the remaining three is shown. Up to 16 regions are measured in parallel.
Why are the numbers higher than what ICMP ping shows?
regionping runs inside a browser, which cannot send ICMP packets. Every sample is an HTTPS HEAD request, so the measured time includes TCP and TLS overhead. Expect regionping numbers to sit roughly 10–30 ms above ICMP ping from the same machine. The ordering between regions is still faithful, which is what matters when choosing one.
Which cloud providers and regions are supported?
AWS (32 regions), Google Cloud (41 regions), Azure (40 regions), Oracle Cloud (37 regions), DigitalOcean (10 regions), IBM Cloud (12 regions), Alibaba Cloud (29 regions), Linode (21 regions), OVHcloud (8 regions), Vultr (10 regions), Hetzner (3 regions), Huawei Cloud (26 regions), Exoscale (7 regions), Scaleway (4 regions), Gcore (3 regions), and Contabo (3 regions). 286 public regions in total.
What do the green, yellow, and red latency values mean?
Green (under 80 ms) is what you want for interactive workloads — API calls, real-time messaging, game servers. Yellow (80–149 ms) is acceptable for most web apps but noticeable in chatty request patterns. Red (150 ms and above) signals a region that is likely far from your network path; usable for batch and background jobs but a poor choice for anything user-interactive.
Why did a region return “failed”?
Most common causes, in roughly decreasing order of likelihood: a corporate firewall or enterprise proxy blocking the provider domain, an active VPN routing the request through a path that drops it, ISP-level blocks on cloud object-storage hostnames, the provider not yet deploying (or having deprecated) the public endpoint in that region, or a browser extension such as an ad blocker or privacy tool intercepting the request. Failures are surfaced explicitly instead of hidden so you can cross-check from a different network.