Round-trip time from your browser to every Vultr region — 32 of them, 11 in North America, 9 in Europe, 6 in Asia, 2 in Oceania, 2 in South America, 1 in Africa, 1 in the Middle East — each against the speed-of-light floor its distance sets, so a slow region is visibly far rather than badly routed.
Vultr publishes a ping host for every location, but a browser cannot send it an ICMP echo. So the host is asked for the first byte of the 100 MB file it serves — a one-byte range request — and not another byte of that file is ever downloaded.
A single-byte Range request: CORS-safelisted so it needs no preflight, returns 206 with Access-Control-Allow-Origin. These are small single machines, never CDNs, so the probe never touches more than one byte of the file.
The first request of a sweep is discarded — it pays for DNS, TCP and TLS — so every sample after it is essentially one round trip, and the reported figure is the fastest of them.
| Region | City | Country | IPv4 prefixes |
|---|---|---|---|
| jnb-za | Johannesburg | ZA | 1 |
| blr-in | Bangalore | IN | 3 |
| del-in | Delhi | IN | 1 |
| bom-in | Mumbai | IN | 1 |
| osk-jp | Osaka | JP | 2 |
| sgp | Singapore | SG | 17 |
| hnd-jp | Tokyo | JP | 42 |
| ams-nl | Amsterdam | NL | 31 |
| fra-de | Frankfurt | DE | 26 |
| lon-gb | London | GB | 23 |
| mad-es | Madrid | ES | 5 |
| man-uk | Manchester | GB | 2 |
| mxp-it | Milan | IT | 2 |
| par-fr | Paris | FR | 18 |
| sto-se | Stockholm | SE | 2 |
| waw-pl | Warsaw | PL | 2 |
| tlv-il | Tel Aviv | IL | 2 |
| ga-us | Atlanta | US | 21 |
| il-us | Chicago | US | 38 |
| tx-us | Dallas | US | 28 |
| hon-hi-us | Honolulu | US | 2 |
| lax-ca-us | Los Angeles | US | 26 |
| mex-mx | Mexico City | MX | 2 |
| fl-us | Miami | US | 21 |
| nj-us | Newark | US | 59 |
| sjo-ca-us | Santa Clara | US | 11 |
| wa-us | Seattle | US | 14 |
| tor-ca | Toronto | CA | 4 |
| mel-au | Melbourne | AU | 2 |
| syd-au | Sydney | AU | 18 |
| scl-cl | Santiago | CL | 1 |
| sao-br | Sao Paulo | BR | 2 |
Prefix counts come from Vultr’s own published feed. Each region links to its distance, its physical floor and the endpoint used to time it.
Open the instrument, select Vultr, choose regions and run a sweep. Nothing is pre-selected and nothing runs until you press the button.