Honolulu. How long a round trip from your machine to this region takes — and how much of that distance alone demands.
| Cloud | Vultr |
|---|---|
| Region code | hon-hi-us |
| Region name | Honolulu |
| Datacentre city | Honolulu, US |
| Coordinates | 21.31, -157.86 |
| Published IPv4 prefixes | 2 |
| Probe endpoint | https://hon-hi-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 Honolulu 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 | 7,982 km | 80 ms |
| Los Angeles | 4,120 km | 41 ms |
| São Paulo | 13,013 km | 130 ms |
| London | 11,632 km | 116 ms |
| Frankfurt | 11,964 km | 120 ms |
| Johannesburg | 19,204 km | 192 ms |
| Dubai | 13,727 km | 137 ms |
| Mumbai | 12,899 km | 129 ms |
| Singapore | 10,814 km | 108 ms |
| Tokyo | 6,209 km | 62 ms |
| Sydney | 8,166 km | 82 ms |
The closest regions to Honolulu on any cloud, with the distance between them and the floor that distance sets.
These figures are geometry. Your own round trip to hon-hi-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.