Canada Central · Toronto, Ontario, CA. 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 | canadacentral |
| Region name | Canada Central |
| Datacentre city | Toronto, Ontario, CA |
| Coordinates | 43.65, -79.38 |
| Published IPv4 prefixes | 613 |
| Probe endpoint | https://canadacentral.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 Toronto, Ontario 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 | 550 km | 5.5 ms |
| Los Angeles | 3,494 km | 35 ms |
| São Paulo | 8,186 km | 82 ms |
| London | 5,712 km | 57 ms |
| Frankfurt | 6,333 km | 63 ms |
| Johannesburg | 13,338 km | 133 ms |
| Dubai | 11,071 km | 111 ms |
| Mumbai | 12,488 km | 125 ms |
| Singapore | 15,001 km | 150 ms |
| Tokyo | 10,351 km | 104 ms |
| Sydney | 15,568 km | 156 ms |
Within 75 km of Toronto, Ontario — 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 canadacentral 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.