New York 3 · New York, US. How long a round trip from your machine to this region takes — and how much of that distance alone demands.
| Cloud | DigitalOcean |
|---|---|
| Region code | nyc3 |
| Region name | New York 3 |
| Datacentre city | New York, US |
| Coordinates | 40.71, -74.01 |
| Published IPv4 prefixes | 298 |
| Probe endpoint | https://nyc3.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 New York 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 | 0 km | under 0.5 ms |
| Los Angeles | 3,936 km | 39 ms |
| São Paulo | 7,686 km | 77 ms |
| London | 5,570 km | 56 ms |
| Frankfurt | 6,203 km | 62 ms |
| Johannesburg | 12,840 km | 128 ms |
| Dubai | 11,008 km | 110 ms |
| Mumbai | 12,538 km | 125 ms |
| Singapore | 15,333 km | 153 ms |
| Tokyo | 10,851 km | 109 ms |
| Sydney | 15,989 km | 160 ms |
Within 75 km of New York — 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 nyc3 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.