Seattle. How long a round trip from your machine to this region takes — and how much of that distance alone demands.
| Cloud | Vultr |
|---|---|
| Region code | wa-us |
| Region name | Seattle |
| Datacentre city | Seattle, US |
| Coordinates | 47.61, -122.33 |
| Published IPv4 prefixes | 14 |
| Probe endpoint | https://wa-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 Seattle 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 | 3,865 km | 39 ms |
| Los Angeles | 1,546 km | 15 ms |
| São Paulo | 10,918 km | 109 ms |
| London | 7,699 km | 77 ms |
| Frankfurt | 8,180 km | 82 ms |
| Johannesburg | 16,504 km | 165 ms |
| Dubai | 11,916 km | 119 ms |
| Mumbai | 12,446 km | 124 ms |
| Singapore | 12,978 km | 130 ms |
| Tokyo | 7,700 km | 77 ms |
| Sydney | 12,470 km | 125 ms |
Within 75 km of Seattle — 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 wa-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.