GCP asia-south2 latency

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

The region

Cloud	Google Cloud
Region code	asia-south2
Region name	Delhi
Datacentre city	Delhi, India, IN
Coordinates	28.61, 77.21
Published IPv4 prefixes	14
Probe endpoint	https://storage.asia-south2.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.

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 Delhi, India 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	11,755 km	118 ms
Los Angeles	12,860 km	129 ms
São Paulo	14,428 km	144 ms
London	6,711 km	67 ms
Frankfurt	6,116 km	61 ms
Johannesburg	8,042 km	80 ms
Dubai	2,205 km	22 ms
Mumbai	1,148 km	11 ms
Singapore	4,143 km	41 ms
Tokyo	5,834 km	58 ms
Sydney	10,428 km	104 ms

Other regions in this metro

Within 75 km of Delhi, India — 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 asia-south2 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.