US East (Ohio) · Columbus, Ohio, US. 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 | us-east-2 |
| Region name | US East (Ohio) |
| Datacentre city | Columbus, Ohio, US |
| Coordinates | 39.96, -82.99 |
| Published IPv4 prefixes | 608 |
| Probe endpoint | https://dynamodb.us-east-2.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 Columbus, Ohio 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 | 765 km | 7.7 ms |
| Los Angeles | 3,177 km | 32 ms |
| São Paulo | 8,005 km | 80 ms |
| London | 6,205 km | 62 ms |
| Frankfurt | 6,829 km | 68 ms |
| Johannesburg | 13,570 km | 136 ms |
| Dubai | 11,578 km | 116 ms |
| Mumbai | 12,989 km | 130 ms |
| Singapore | 15,370 km | 154 ms |
| Tokyo | 10,540 km | 105 ms |
| Sydney | 15,223 km | 152 ms |
Within 75 km of Columbus, Ohio — 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 us-east-2 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.