region·latency

GCP asia-northeast2 latency

Osaka. 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 codeasia-northeast2
Region nameOsaka
Datacentre cityOsaka, Japan, JP
Coordinates34.69, 135.50
Published IPv4 prefixes9
Probe endpointhttps://storage.asia-northeast2.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 Osaka, Japan and the latency no network can beat — not a measurement, a limit. What you actually measure is this plus routing.

FromDistanceFloor
New York11,103 km111 ms
Los Angeles9,190 km92 ms
São Paulo18,759 km188 ms
London9,499 km95 ms
Frankfurt9,237 km92 ms
Johannesburg13,143 km131 ms
Dubai7,603 km76 ms
Mumbai6,348 km63 ms
Singapore4,951 km50 ms
Tokyo393 km3.9 ms
Sydney7,798 km78 ms

Other regions in this metro

Within 75 km of Osaka, Japan — 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-northeast2 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.