China (Beijing) · Beijing, CN. 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 | cn-north-1 |
| Region name | China (Beijing) |
| Datacentre city | Beijing, CN |
| Coordinates | 39.90, 116.41 |
| Published IPv4 prefixes | 132 |
| Probe endpoint | https://dynamodb.cn-north-1.amazonaws.com.cn/ |
| 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 Beijing 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 | 10,990 km | 110 ms |
| Los Angeles | 10,062 km | 101 ms |
| São Paulo | 17,599 km | 176 ms |
| London | 8,141 km | 81 ms |
| Frankfurt | 7,781 km | 78 ms |
| Johannesburg | 11,706 km | 117 ms |
| Dubai | 5,843 km | 58 ms |
| Mumbai | 4,744 km | 47 ms |
| Singapore | 4,472 km | 45 ms |
| Tokyo | 2,089 km | 21 ms |
| Sydney | 8,948 km | 89 ms |
The closest regions to Beijing on any cloud, with the distance between them and the floor that distance sets.
These figures are geometry. Your own round trip to cn-north-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.