Mexico Northeast (Monterrey) · Monterrey, MX. 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 | mx-monterrey-1 |
| Region name | Mexico Northeast (Monterrey) |
| Datacentre city | Monterrey, MX |
| Coordinates | 25.69, -100.32 |
| Published IPv4 prefixes | 10 |
| Probe endpoint | https://objectstorage.mx-monterrey-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 Monterrey 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 | 2,945 km | 29 ms |
| Los Angeles | 1,958 km | 20 ms |
| São Paulo | 7,959 km | 80 ms |
| London | 8,463 km | 85 ms |
| Frankfurt | 9,084 km | 91 ms |
| Johannesburg | 14,888 km | 149 ms |
| Dubai | 13,778 km | 138 ms |
| Mumbai | 14,983 km | 150 ms |
| Singapore | 16,043 km | 160 ms |
| Tokyo | 10,732 km | 107 ms |
| Sydney | 13,187 km | 132 ms |
The closest regions to Monterrey on any cloud, with the distance between them and the floor that distance sets.
These figures are geometry. Your own round trip to mx-monterrey-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.