region·latency

GCP us-south1 latency

Dallas. 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-south1
Region nameDallas
Datacentre cityDallas, Texas, US
Coordinates32.78, -96.80
Published IPv4 prefixes16
Probe endpointhttps://storage.us-south1.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 Dallas, Texas and the latency no network can beat — not a measurement, a limit. What you actually measure is this plus routing.

FromDistanceFloor
New York2,205 km22 ms
Los Angeles1,992 km20 ms
São Paulo8,217 km82 ms
London7,641 km76 ms
Frankfurt8,256 km83 ms
Johannesburg14,686 km147 ms
Dubai12,922 km129 ms
Mumbai14,145 km141 ms
Singapore15,646 km156 ms
Tokyo10,401 km104 ms
Sydney13,819 km138 ms

Other regions in this metro

Within 75 km of Dallas, Texas — 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-south1 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.