India South Central · Hyderabad, IN. 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 | indiasouthcentral |
| Region name | India South Central |
| Datacentre city | Hyderabad, IN |
| Coordinates | 17.39, 78.49 |
| Published IPv4 prefixes | 125 |
| Probe endpoint | https://indiasouthcentral.handler.control.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 Hyderabad 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 | 12,958 km | 130 ms |
| Los Angeles | 14,028 km | 140 ms |
| São Paulo | 14,289 km | 143 ms |
| London | 7,722 km | 77 ms |
| Frankfurt | 7,101 km | 71 ms |
| Johannesburg | 7,292 km | 73 ms |
| Dubai | 2,553 km | 26 ms |
| Mumbai | 621 km | 6.2 ms |
| Singapore | 3,293 km | 33 ms |
| Tokyo | 6,311 km | 63 ms |
| Sydney | 9,569 km | 96 ms |
Within 75 km of Hyderabad — 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 indiasouthcentral 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.