Central US · Des Moines, Iowa, US. How long a round trip from your machine to this region takes — and how much of that distance alone demands.
| Cloud | Microsoft Azure |
|---|---|
| Region code | centralus |
| Region name | Central US |
| Datacentre city | Des Moines, Iowa, US |
| Coordinates | 41.59, -93.62 |
| Published IPv4 prefixes | 1,378 |
| Probe endpoint | https://centralus.livediagnostics.monitor.azure.com/ |
| Probe style | timed blind — the endpoint sends no CORS headers |
| Verification | Resolved to an address inside this region’s own published range, TCP 443 open. Checked 2026-08-21. |
Coordinates are the real datacentre city rather than the marketing region name, because they feed the distance maths below.
Light in fibre covers about 100 km per millisecond of round trip. These are the great-circle distances to Des Moines, Iowa 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 | 1,641 km | 16 ms |
| Los Angeles | 2,309 km | 23 ms |
| São Paulo | 8,709 km | 87 ms |
| London | 6,736 km | 67 ms |
| Frankfurt | 7,336 km | 73 ms |
| Johannesburg | 14,477 km | 145 ms |
| Dubai | 11,927 km | 119 ms |
| Mumbai | 13,127 km | 131 ms |
| Singapore | 14,927 km | 149 ms |
| Tokyo | 9,856 km | 99 ms |
| Sydney | 14,383 km | 144 ms |
Within 75 km of Des Moines, Iowa — 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.
These figures are geometry. Your own round trip to centralus depends on your connection and the route it takes — open the instrument, pick Azure, 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 Azure region on the Azure latency page.