Jio India Central · Nagpur, 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 | jioindiacentral |
| Region name | Jio India Central |
| Datacentre city | Nagpur, IN |
| Coordinates | 21.15, 79.09 |
| Published IPv4 prefixes | 166 |
| Probe endpoint | https://jioindiacentral.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 Nagpur 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,596 km | 126 ms |
| Los Angeles | 13,609 km | 136 ms |
| São Paulo | 14,459 km | 145 ms |
| London | 7,449 km | 74 ms |
| Frankfurt | 6,837 km | 68 ms |
| Johannesburg | 7,614 km | 76 ms |
| Dubai | 2,473 km | 25 ms |
| Mumbai | 688 km | 6.9 ms |
| Singapore | 3,469 km | 35 ms |
| Tokyo | 6,044 km | 60 ms |
| Sydney | 9,774 km | 98 ms |
The closest regions to Nagpur on any cloud, with the distance between them and the floor that distance sets.
These figures are geometry. Your own round trip to jioindiacentral 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.