South Central US · San Antonio, Texas, 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 | southcentralus |
| Region name | South Central US |
| Datacentre city | San Antonio, Texas, US |
| Coordinates | 29.42, -98.49 |
| Published IPv4 prefixes | 1,233 |
| Probe endpoint | https://southcentralus.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 San Antonio, Texas 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 | 2,545 km | 25 ms |
| Los Angeles | 1,933 km | 19 ms |
| São Paulo | 8,088 km | 81 ms |
| London | 8,028 km | 80 ms |
| Frankfurt | 8,647 km | 86 ms |
| Johannesburg | 14,791 km | 148 ms |
| Dubai | 13,327 km | 133 ms |
| Mumbai | 14,543 km | 145 ms |
| Singapore | 15,852 km | 159 ms |
| Tokyo | 10,562 km | 106 ms |
| Sydney | 13,526 km | 135 ms |
Within 75 km of San Antonio, Texas — 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 southcentralus 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.