Amsterdam 3 · Amsterdam, NL. How long a round trip from your machine to this region takes — and how much of that distance alone demands.
| Cloud | DigitalOcean |
|---|---|
| Region code | ams3 |
| Region name | Amsterdam 3 |
| Datacentre city | Amsterdam, NL |
| Coordinates | 52.37, 4.90 |
| Published IPv4 prefixes | 149 |
| Probe endpoint | https://ams3.digitaloceanspaces.com/ |
| Probe style | timed blind — the endpoint sends no CORS headers |
| Verification | TCP 443 open. DigitalOcean’s geofeed covers droplets rather than object storage, so the address cannot be placed from the feed — the location is corroborated by agreement with unrelated clouds in the same city. 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 Amsterdam 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 | 5,864 km | 59 ms |
| Los Angeles | 8,940 km | 89 ms |
| São Paulo | 9,805 km | 98 ms |
| London | 358 km | 3.6 ms |
| Frankfurt | 363 km | 3.6 ms |
| Johannesburg | 9,022 km | 90 ms |
| Dubai | 5,160 km | 52 ms |
| Mumbai | 6,852 km | 69 ms |
| Singapore | 10,492 km | 105 ms |
| Tokyo | 9,288 km | 93 ms |
| Sydney | 16,643 km | 166 ms |
Within 75 km of Amsterdam — 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 ams3 depends on your connection and the route it takes — open the instrument, pick DO, 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 DO region on the DO latency page.