region·latency

GCP us-central1 latency

Iowa · Council Bluffs, Iowa, US. 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-central1
Region nameIowa
Datacentre cityCouncil Bluffs, Iowa, US
Coordinates41.26, -95.86
Published IPv4 prefixes107
Probe endpointhttps://storage.us-central1.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 Council Bluffs, Iowa and the latency no network can beat — not a measurement, a limit. What you actually measure is this plus routing.

FromDistanceFloor
New York1,830 km18 ms
Los Angeles2,119 km21 ms
São Paulo8,812 km88 ms
London6,894 km69 ms
Frankfurt7,490 km75 ms
Johannesburg14,663 km147 ms
Dubai12,048 km120 ms
Mumbai13,206 km132 ms
Singapore14,877 km149 ms
Tokyo9,760 km98 ms
Sydney14,193 km142 ms

Nearest other regions

The closest regions to Council Bluffs, Iowa on any cloud, with the distance between them and the floor that distance sets.

Measure it yourself

These figures are geometry. Your own round trip to us-central1 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.