Brazil Southeast · Rio de Janeiro, BR. 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 | brazilsoutheast |
| Region name | Brazil Southeast |
| Datacentre city | Rio de Janeiro, BR |
| Coordinates | -22.91, -43.17 |
| Published IPv4 prefixes | 239 |
| Probe endpoint | https://brazilsoutheast.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 Rio de Janeiro 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 | 7,759 km | 78 ms |
| Los Angeles | 10,143 km | 101 ms |
| São Paulo | 360 km | 3.6 ms |
| London | 9,278 km | 93 ms |
| Frankfurt | 9,585 km | 96 ms |
| Johannesburg | 7,120 km | 71 ms |
| Dubai | 11,869 km | 119 ms |
| Mumbai | 13,414 km | 134 ms |
| Singapore | 15,722 km | 157 ms |
| Tokyo | 18,569 km | 186 ms |
| Sydney | 13,521 km | 135 ms |
Within 75 km of Rio de Janeiro — 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 brazilsoutheast 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.