South America (Chile) · Santiago, CL. 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 | sa-west-1 |
| Region name | South America (Chile) |
| Datacentre city | Santiago, CL |
| Coordinates | -33.45, -70.67 |
| Published IPv4 prefixes | 35 |
| Probe endpoint | https://dynamodb.sa-west-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 Santiago 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 | 8,253 km | 83 ms |
| Los Angeles | 8,998 km | 90 ms |
| São Paulo | 2,586 km | 26 ms |
| London | 11,673 km | 117 ms |
| Frankfurt | 12,110 km | 121 ms |
| Johannesburg | 9,178 km | 92 ms |
| Dubai | 14,753 km | 148 ms |
| Mumbai | 16,071 km | 161 ms |
| Singapore | 16,400 km | 164 ms |
| Tokyo | 17,239 km | 172 ms |
| Sydney | 11,346 km | 113 ms |
Within 75 km of Santiago — 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 sa-west-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.