region·latency

GCP northamerica-south1 latency

México · Querétaro, Mexico, MX. 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 codenorthamerica-south1
Region nameMéxico
Datacentre cityQuerétaro, Mexico, MX
Coordinates20.59, -100.39
Published IPv4 prefixes4
Probe endpointhttps://storage.northamerica-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 Querétaro, Mexico and the latency no network can beat — not a measurement, a limit. What you actually measure is this plus routing.

FromDistanceFloor
New York3,348 km33 ms
Los Angeles2,306 km23 ms
São Paulo7,615 km76 ms
London8,910 km89 ms
Frankfurt9,538 km95 ms
Johannesburg14,749 km147 ms
Dubai14,284 km143 ms
Mumbai15,544 km155 ms
Singapore16,424 km164 ms
Tokyo11,126 km111 ms
Sydney12,920 km129 ms

Other regions in this metro

Within 75 km of Querétaro, Mexico — 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 northamerica-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.