HTTPS latency, not ping
Your browser times requests to each region's official health endpoint. TLS and service handling are included, so values run a few to tens of ms above ICMP ping, but regions remain comparable.
Cloud Region Latency Test
Before you buy a VPS, test from your own network: 156 regions across AWS, Google Cloud, Oracle Cloud, Vultr and Sharktech, ranked by speed and stability.
Testing from (your network)United States · Anthropic, PBC · AS16509
0/0
Tests contact the listed providers' health endpoints, which see your exit IP. Quick-test results are kept for 30 days as described in the privacy policy; full tests and continuous comparisons are computed in your browser only. Not measured
1
Measure
Each region gets one warm-up request (shown as first-connection time), then five timed samples.
2
Rank
Regions are ranked by median, jitter and timeout rate, so you see which is fastest and most stable.
3
Compare over time
Pick 2–5 candidates from the ranking and test them for 5–60 minutes, ideally again at the evening peak.
Continuous comparison
Each region is tested once every 5 seconds while this page stays open; it pauses in a background tab.
Use "+ Compare" in the ranking below to pick 2–5 regions.
The evening peak (20:00–23:00 local time) is when routes congest most. Recheck regions that were fast during the day.
Low latency ≠ high bandwidth: two checks before you buy
A browser measures HTTPS round trips; it cannot see the route type or bandwidth. Once you have a candidate, confirm with the provider's test IP, Looking Glass or test files.
What this measures
This page measures the HTTPS response time from your browser to regional nodes. It is not download/upload bandwidth and not ICMP ping.
Median, P90, jitter, timeouts
The median is the typical value, P90 the slow 10%, jitter the mean difference between consecutive samples. A region with many timeouts is not recommended even with a low median.
Your network only
Results reflect your current network and time of day. Google Cloud is edge-fronted, so it is shown but not ranked.
Region code reference
Order pages often show only region codes; match them to cities here.
| City | AWS | Google Cloud | Oracle Cloud | Vultr |
|---|---|---|---|---|
| Tokyo | ap-northeast-1 | asia-northeast1 | ap-tokyo-1 | nrt |
| Osaka | ap-northeast-3 | asia-northeast2 | ap-osaka-1 | itm |
| Hong Kong | ap-east-1 | asia-east2 | — | — |
| Singapore | ap-southeast-1 | asia-southeast1 | ap-singapore-1 | sgp |
| Seoul | ap-northeast-2 | asia-northeast3 | ap-seoul-1 | icn |
| Los Angeles / California | us-west-1 | us-west2 | us-sanjose-1 | lax |
| Frankfurt | eu-central-1 | europe-west3 | eu-frankfurt-1 | fra |
FAQ
Which Oracle Cloud region has the lowest latency?
It depends on your ISP and city. After a full test, filter the ranking to Oracle Cloud to see all 42 of its regions in order for your network.
Why are the numbers higher than ping?
This page times browser HTTPS requests, including the encryption handshake and service handling; ping measures only the network round trip. The order of regions usually matches.
Why is Google Cloud not ranked?
Its test endpoints connect through the nearest Google edge first, so the values are not comparable with other providers.
Are results stored?
Quick-test results are kept for 30 days as described in the privacy policy. Full tests and continuous comparisons are computed in your browser and not uploaded.