Las Vegas. How long a round trip from your machine to this region takes — and how much of that distance alone demands.
| Cloud | Google Cloud |
|---|---|
| Region code | us-west4 |
| Region name | Las Vegas |
| Datacentre city | Las Vegas, Nevada, US |
| Coordinates | 36.17, -115.14 |
| Published IPv4 prefixes | 11 |
| Probe endpoint | https://storage.us-west4.rep.googleapis.com/ |
| Probe style | timed blind — the endpoint sends no CORS headers |
| Verification | Probed on this region’s dedicated regional storage endpoint — one address per region, no wildcard DNS — with identity confirmed by a single gcping call per sweep. The recorded range-check predates this endpoint and covered an earlier host. Checked 2026-08-21. |
Coordinates are the real datacentre city rather than the marketing region name, because they feed the distance maths below.
Light in fibre covers about 100 km per millisecond of round trip. These are the great-circle distances to Las Vegas, Nevada and the latency no network can beat — not a measurement, a limit. What you actually measure is this plus routing.
| From | Distance | Floor |
|---|---|---|
| New York | 3,585 km | 36 ms |
| Los Angeles | 368 km | 3.7 ms |
| São Paulo | 9,783 km | 98 ms |
| London | 8,401 km | 84 ms |
| Frankfurt | 8,954 km | 90 ms |
| Johannesburg | 16,367 km | 164 ms |
| Dubai | 13,117 km | 131 ms |
| Mumbai | 13,814 km | 138 ms |
| Singapore | 14,217 km | 142 ms |
| Tokyo | 8,905 km | 89 ms |
| Sydney | 12,433 km | 124 ms |
The closest regions to Las Vegas, Nevada on any cloud, with the distance between them and the floor that distance sets.
These figures are geometry. Your own round trip to us-west4 depends on your connection and the route it takes — open the instrument, pick GCP, and sweep. Every region is timed from your browser against the endpoint listed above, and the result is split into the part physics demands and the part the network added.
See every GCP region on the GCP latency page.