Silicon Valley · Santa Clara, US. How long a round trip from your machine to this region takes — and how much of that distance alone demands.
| Cloud | Vultr |
|---|---|
| Region code | sjo-ca-us |
| Region name | Silicon Valley |
| Datacentre city | Santa Clara, US |
| Coordinates | 37.35, -121.96 |
| Published IPv4 prefixes | 11 |
| Probe endpoint | https://sjo-ca-us-ping.vultr.com/vultr.com.100MB.bin |
| 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 Santa Clara 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 | 4,107 km | 41 ms |
| Los Angeles | 497 km | 5.0 ms |
| São Paulo | 10,376 km | 104 ms |
| London | 8,633 km | 86 ms |
| Frankfurt | 9,154 km | 92 ms |
| Johannesburg | 16,938 km | 169 ms |
| Dubai | 13,053 km | 131 ms |
| Mumbai | 13,550 km | 136 ms |
| Singapore | 13,642 km | 136 ms |
| Tokyo | 8,334 km | 83 ms |
| Sydney | 11,960 km | 120 ms |
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.
These figures are geometry. Your own round trip to sjo-ca-us depends on your connection and the route it takes — open the instrument, pick Vultr, 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 Vultr region on the Vultr latency page.