region·latency

GCP us-west3 latency

Salt Lake City. How long a round trip from your machine to this region takes — and how much of that distance alone demands.

The region

CloudGoogle Cloud
Region codeus-west3
Region nameSalt Lake City
Datacentre citySalt Lake City, Utah, US
Coordinates40.76, -111.89
Published IPv4 prefixes14
Probe endpointhttps://storage.us-west3.rep.googleapis.com/
Probe styletimed blind — the endpoint sends no CORS headers
VerificationProbed 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.

Distance, and the floor it sets

Light in fibre covers about 100 km per millisecond of round trip. These are the great-circle distances to Salt Lake City, Utah and the latency no network can beat — not a measurement, a limit. What you actually measure is this plus routing.

FromDistanceFloor
New York3,166 km32 ms
Los Angeles933 km9.3 ms
São Paulo9,818 km98 ms
London7,823 km78 ms
Frankfurt8,372 km84 ms
Johannesburg16,006 km160 ms
Dubai12,562 km126 ms
Mumbai13,343 km133 ms
Singapore14,103 km141 ms
Tokyo8,816 km88 ms
Sydney12,906 km129 ms

Other regions in this metro

Within 75 km of Salt Lake City, Utah — near enough that distance sets no meaningful floor between them. When several sit in one city, the fastest is the city’s real floor; a slower neighbour is usually the endpoint’s own server time.

Measure it yourself

These figures are geometry. Your own round trip to us-west3 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.