Mexico (Central) · Queretaro, MX. How long a round trip from your machine to this region takes — and how much of that distance alone demands.
| Cloud | Amazon Web Services |
|---|---|
| Region code | mx-central-1 |
| Region name | Mexico (Central) |
| Datacentre city | Queretaro, MX |
| Coordinates | 20.59, -100.39 |
| Published IPv4 prefixes | 72 |
| Probe endpoint | https://dynamodb.mx-central-1.amazonaws.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 Queretaro 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,348 km | 33 ms |
| Los Angeles | 2,306 km | 23 ms |
| São Paulo | 7,615 km | 76 ms |
| London | 8,910 km | 89 ms |
| Frankfurt | 9,538 km | 95 ms |
| Johannesburg | 14,749 km | 147 ms |
| Dubai | 14,284 km | 143 ms |
| Mumbai | 15,543 km | 155 ms |
| Singapore | 16,424 km | 164 ms |
| Tokyo | 11,126 km | 111 ms |
| Sydney | 12,920 km | 129 ms |
Within 75 km of Queretaro — 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 mx-central-1 depends on your connection and the route it takes — open the instrument, pick AWS, 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 AWS region on the AWS latency page.