Round-trip time from your browser to every Google Cloud region — 43 of them, 13 in Europe, 12 in North America, 10 in Asia, 3 in the Middle East, 2 in Oceania, 2 in South America, 1 in Africa — and how much of each is distance rather than the network.
Timed on storage.{region}.rep.googleapis.com, which terminates inside the region — its handshake tracks real distance where the gcping frontend answers in 8 ms from anywhere. Each region has a dedicated address and no wildcard DNS, so a made-up region name does not resolve. Identity is then confirmed by one call to gcping, whose reply is the region code.
One exception: asia-southeast3 has no regional endpoint yet and is still timed against the shared gcping frontend, so its figure reflects Google’s nearest edge rather than the region.
The first request of a sweep is discarded — it pays for DNS, TCP and TLS — so every sample after it is essentially one round trip, and the reported figure is the fastest of them.
| Region | City | Country | IPv4 prefixes |
|---|---|---|---|
| africa-south1 | Johannesburg | ZA | 6 |
| asia-southeast3 | Bangkok, Thailand | TH | 4 |
| asia-east1 | Changhua County, Taiwan | TW | 30 |
| asia-south2 | Delhi, India | IN | 14 |
| asia-east2 | Hong Kong | HK | 11 |
| asia-southeast2 | Jakarta, Indonesia | ID | 16 |
| asia-southeast1 | Jurong West, Singapore | SG | 43 |
| asia-south1 | Mumbai, India | IN | 32 |
| asia-northeast2 | Osaka, Japan | JP | 9 |
| asia-northeast3 | Seoul, South Korea | KR | 26 |
| asia-northeast1 | Tokyo, Japan | JP | 25 |
| europe-west10 | Berlin, Germany | DE | 4 |
| europe-west4 | Eemshaven, Netherlands | NL | 36 |
| europe-west3 | Frankfurt, Germany | DE | 31 |
| europe-north1 | Hamina, Finland | FI | 8 |
| europe-west2 | London, United Kingdom | GB | 36 |
| europe-southwest1 | Madrid, Spain | ES | 9 |
| europe-west8 | Milan, Italy | IT | 15 |
| europe-west9 | Paris, France | FR | 7 |
| europe-west1 | St. Ghislain, Belgium | BE | 55 |
| europe-north2 | Stockholm, Sweden | SE | 4 |
| europe-west12 | Turin, Italy | IT | 11 |
| europe-central2 | Warsaw, Poland | PL | 8 |
| europe-west6 | Zurich, Switzerland | CH | 10 |
| me-central2 | Dammam, Saudi Arabia | SA | 15 |
| me-central1 | Doha, Qatar | QA | 6 |
| me-west1 | Tel Aviv, Israel | IL | 12 |
| us-east4 | Ashburn, Virginia | US | 51 |
| us-east5 | Columbus, Ohio | US | 17 |
| us-central1 | Council Bluffs, Iowa | US | 107 |
| us-south1 | Dallas, Texas | US | 16 |
| us-west4 | Las Vegas, Nevada | US | 11 |
| us-west2 | Los Angeles, California | US | 19 |
| us-east1 | Moncks Corner, South Carolina | US | 48 |
| northamerica-northeast1 | Montréal, Quebec, Canada | CA | 24 |
| northamerica-south1 | Querétaro, Mexico | MX | 4 |
| us-west3 | Salt Lake City, Utah | US | 14 |
| us-west1 | The Dalles, Oregon | US | 60 |
| northamerica-northeast2 | Toronto, Ontario, Canada | CA | 11 |
| australia-southeast2 | Melbourne, Australia | AU | 8 |
| australia-southeast1 | Sydney, Australia | AU | 25 |
| southamerica-east1 | Osasco, São Paulo, Brazil | BR | 14 |
| southamerica-west1 | Santiago, Chile | CL | 14 |
Prefix counts come from GCP’s own published feed. Each region links to its distance, its physical floor and the endpoint used to time it.
Open the instrument, select GCP, choose regions and run a sweep. Nothing is pre-selected and nothing runs until you press the button.