</>

WebDevTools

Cloud Ping

HTTP latency from your browser to datacenters worldwide

Click measure to send requests to each region's public endpoints (AWS DynamoDB, GCP, Vultr, etc.). Values are HTTP RTT estimates — not ICMP — and vary with your network, VPN and browser restrictions.

RegionLatency
us-east-1 (Virginia)
us-east-2 (Ohio)
us-west-1 (California)
us-west-2 (Oregon)
ca-central-1 (Canada Central)
ca-west-1 (Canada West)
eu-west-1 (Ireland)
eu-west-2 (London)
eu-west-3 (Paris)
eu-central-1 (Frankfurt)
eu-central-2 (Zurich)
eu-south-1 (Milan)
eu-south-2 (Spain)
eu-north-1 (Stockholm)
il-central-1 (Tel Aviv)
me-south-1 (Bahrain)
me-central-1 (UAE)
af-south-1 (Cape Town)
ap-east-1 (Hong Kong)
ap-east-2 (Taipei)
ap-southeast-3 (Jakarta)
ap-south-1 (Mumbai)
ap-south-2 (Hyderabad)
ap-northeast-3 (Osaka)
ap-northeast-2 (Seoul)
ap-southeast-1 (Singapore)
ap-southeast-2 (Sydney)
ap-southeast-4 (Melbourne)
ap-northeast-1 (Tokyo)
sa-east-1 (São Paulo)
cn-north-1 (Beijing)
cn-northwest-1 (Ningxia)
mx-central-1 (Mexico)
us-gov-east-1
us-gov-west-1

RegionLatency
SFO2 (San Francisco)
SFO3 (San Francisco)
TOR1 (Toronto)
ATL1 (Atlanta)
NYC1 (New York)
unavailable
NYC2 (New York)
unavailable
NYC3 (New York)
LON1 (London)
AMS3 (Amsterdam)
FRA1 (Frankfurt)
BLR1 (Bangalore)
SGP1 (Singapore)
SYD1 (Sydney)

RegionLatency
africa-south1 (Johannesburg)
asia-east1 (Taiwan)
asia-east2 (Hong Kong)
asia-northeast1 (Tokyo)
asia-northeast2 (Osaka)
asia-northeast3 (Seoul)
asia-south1 (Mumbai)
asia-south2 (Delhi)
asia-southeast1 (Singapore)
asia-southeast2 (Jakarta)
australia-southeast1 (Sydney)
australia-southeast2 (Melbourne)
europe-central2 (Warsaw)
europe-north1 (Finland)
europe-north2 (Stockholm)
europe-southwest1 (Madrid)
europe-west1 (Belgium)
europe-west10 (Berlin)
europe-west12 (Turin)
europe-west2 (London)
europe-west3 (Frankfurt)
europe-west4 (Netherlands)
europe-west6 (Zurich)
europe-west8 (Milan)
europe-west9 (Paris)
global (Global External HTTPS Load Balancer)
me-central1 (Doha)
me-central2 (Dammam)
me-west1 (Tel Aviv)
northamerica-northeast1 (Montréal)
northamerica-northeast2 (Toronto)
southamerica-east1 (São Paulo)
southamerica-west1 (Santiago)
us-central1 (Iowa)
us-east1 (South Carolina)
us-east4 (North Virginia)
us-east5 (Columbus)
us-south1 (Dallas)
us-west1 (Oregon)
us-west2 (Los Angeles)
us-west3 (Salt Lake City)
us-west4 (Las Vegas)

Measurements run only in your browser; nothing is sent to our servers. Non-CORS endpoints may be inaccurate. Use as a guide when choosing a region — not a substitute for load tests or traceroute.

Guide: measure latency to cloud regions

Picking a deploy region from the provider map alone ignores the real path from your team and users. An HTTP ping from your browser shows which datacenter responds fastest on your current network.

The tool fires requests to each region's public endpoints (for example AWS DynamoDB `/ping`). The number is HTTP round-trip time — not ICMP — and is best used to compare regions relative to each other.

Use before provisioning staging, when testing a corporate VPN, or when explaining why São Paulo beats Virginia for a Brazil-based team. Re-run after changing networks or ISPs.

Step by step

  1. Click Measure latencyMany regions are tested in parallel; the first run may take a few minutes.
  2. Compare providersOpen AWS, GCP, DigitalOcean and others in the accordion. Unavailable or non-CORS endpoints may fail or look slower.
  3. Sort by latencyAfter the run, sort results to quickly see the best options for your location.
  4. Validate in productionConfirm with real API tests and end users — latency of an empty GET is not a full workload benchmark.

Frequently asked questions