Canada Southeast (Montreal) · Montreal, CA. How long a round trip from your machine to this region takes — and how much of that distance alone demands.
| Cloud | Oracle Cloud Infrastructure |
|---|---|
| Region code | ca-montreal-1 |
| Region name | Canada Southeast (Montreal) |
| Datacentre city | Montreal, CA |
| Coordinates | 45.50, -73.57 |
| Published IPv4 prefixes | 15 |
| Probe endpoint | https://objectstorage.ca-montreal-1.oraclecloud.com/ |
| Probe style | a CORS request whose reply the page can read |
| 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 Montreal 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 | 534 km | 5.3 ms |
| Los Angeles | 3,967 km | 40 ms |
| São Paulo | 8,147 km | 81 ms |
| London | 5,221 km | 52 ms |
| Frankfurt | 5,845 km | 58 ms |
| Johannesburg | 12,921 km | 129 ms |
| Dubai | 10,608 km | 106 ms |
| Mumbai | 12,075 km | 121 ms |
| Singapore | 14,799 km | 148 ms |
| Tokyo | 10,392 km | 104 ms |
| Sydney | 16,029 km | 160 ms |
Within 75 km of Montreal — 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 ca-montreal-1 depends on your connection and the route it takes — open the instrument, pick Oracle, 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 Oracle region on the Oracle latency page.