region·latency

DO sfo3 latency

San Francisco 3 · Santa Clara, US. How long a round trip from your machine to this region takes — and how much of that distance alone demands.

The region

CloudDigitalOcean
Region codesfo3
Region nameSan Francisco 3
Datacentre citySanta Clara, US
Coordinates37.35, -121.96
Published IPv4 prefixes279
Probe endpointhttps://sfo3.digitaloceanspaces.com/
Probe styletimed blind — the endpoint sends no CORS headers
VerificationTCP 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.

Distance, and the floor it sets

Light in fibre covers about 100 km per millisecond of round trip. These are the great-circle distances to Santa Clara and the latency no network can beat — not a measurement, a limit. What you actually measure is this plus routing.

FromDistanceFloor
New York4,107 km41 ms
Los Angeles497 km5.0 ms
São Paulo10,376 km104 ms
London8,633 km86 ms
Frankfurt9,154 km92 ms
Johannesburg16,938 km169 ms
Dubai13,053 km131 ms
Mumbai13,550 km136 ms
Singapore13,642 km136 ms
Tokyo8,334 km83 ms
Sydney11,960 km120 ms

Other regions in this metro

Within 75 km of Santa Clara — 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.

Measure it yourself

These figures are geometry. Your own round trip to sfo3 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.