Canada East · Quebec City, Quebec, 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 | canadaeast |
| Region name | Canada East |
| Datacentre city | Quebec City, Quebec, CA |
| Coordinates | 46.81, -71.21 |
| Published IPv4 prefixes | 403 |
| Probe endpoint | https://canadaeast.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 Quebec City, Quebec 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 | 715 km | 7.1 ms |
| Los Angeles | 4,155 km | 42 ms |
| São Paulo | 8,205 km | 82 ms |
| London | 4,988 km | 50 ms |
| Frankfurt | 5,612 km | 56 ms |
| Johannesburg | 12,774 km | 128 ms |
| Dubai | 10,375 km | 104 ms |
| Mumbai | 11,852 km | 119 ms |
| Singapore | 14,638 km | 146 ms |
| Tokyo | 10,339 km | 103 ms |
| Sydney | 16,198 km | 162 ms |
The closest regions to Quebec City, Quebec on any cloud, with the distance between them and the floor that distance sets.
These figures are geometry. Your own round trip to canadaeast 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.