Mexico City. How long a round trip from your machine to this region takes — and how much of that distance alone demands.
| Cloud | Vultr |
|---|---|
| Region code | mex-mx |
| Region name | Mexico City |
| Datacentre city | Mexico City, MX |
| Coordinates | 19.43, -99.13 |
| Published IPv4 prefixes | 2 |
| Probe endpoint | https://mex-mx-ping.vultr.com/vultr.com.100MB.bin |
| 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 Mexico City 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 | 3,359 km | 34 ms |
| Los Angeles | 2,490 km | 25 ms |
| São Paulo | 7,432 km | 74 ms |
| London | 8,928 km | 89 ms |
| Frankfurt | 9,560 km | 96 ms |
| Johannesburg | 14,585 km | 146 ms |
| Dubai | 14,332 km | 143 ms |
| Mumbai | 15,645 km | 156 ms |
| Singapore | 16,607 km | 166 ms |
| Tokyo | 11,310 km | 113 ms |
| Sydney | 12,973 km | 130 ms |
The closest regions to Mexico City on any cloud, with the distance between them and the floor that distance sets.
These figures are geometry. Your own round trip to mex-mx depends on your connection and the route it takes — open the instrument, pick Vultr, 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 Vultr region on the Vultr latency page.