region·latency

GCP us-east5 latency

Columbus. 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-east5
Region nameColumbus
Datacentre cityColumbus, Ohio, US
Coordinates39.96, -83.00
Published IPv4 prefixes17
Probe endpointhttps://storage.us-east5.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 Columbus, Ohio and the latency no network can beat — not a measurement, a limit. What you actually measure is this plus routing.

FromDistanceFloor
New York766 km7.7 ms
Los Angeles3,176 km32 ms
São Paulo8,005 km80 ms
London6,206 km62 ms
Frankfurt6,830 km68 ms
Johannesburg13,571 km136 ms
Dubai11,579 km116 ms
Mumbai12,990 km130 ms
Singapore15,369 km154 ms
Tokyo10,539 km105 ms
Sydney15,222 km152 ms

Other regions in this metro

Within 75 km of Columbus, Ohio — 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-east5 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.