Find Your Lowest-Latency Cloud Region
A browser-based cloud ping test that measures real network latency to 286 public regions across AWS, Google Cloud, Azure, Oracle Cloud, DigitalOcean, IBM Cloud, Alibaba Cloud, Linode, OVHcloud, Vultr, Hetzner, Huawei Cloud, Exoscale, Scaleway, Gcore, and Contabo. Find the closest cloud region to you — no signup, no install.
0regions
Choose providers to start
How regionping works
Pick one or more cloud providers in the toolbar above. The app will measure your network latency to each of their public regions directly from your browser — so numbers reflect your connection, not a datacenter probe in someone else's lab.
- 286 regions
- Across AWS, Google Cloud, Azure, Oracle Cloud, DigitalOcean, IBM Cloud, Alibaba Cloud, Linode, OVHcloud, Vultr, Hetzner, Huawei Cloud, Exoscale, Scaleway, Gcore, and Contabo — the full public footprint of each.
- Runs in your browser
- Latency probes run client-side. No backend, no account, no install.
Frequently asked questions
Everything below is the precise methodology behind the numbers on this page.
What is a cloud ping test?
A cloud ping test measures the round-trip latency between your device and a cloud provider’s regional endpoint. Unlike traditional ICMP ping, browser-based cloud ping tests like regionping use HTTPS HEAD requests so they work from any modern browser without local tools or special permissions. Lower numbers mean a faster, more responsive region for your network path.
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.