region·latency

Vultr latency test

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 — and how much of each is distance rather than the network.

How Vultr is probed

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.

Every Vultr region

RegionCityCountryIPv4 prefixes
jnb-zaJohannesburgZA1
blr-inBangaloreIN3
del-inDelhiIN1
bom-inMumbaiIN1
osk-jpOsakaJP2
sgpSingaporeSG17
hnd-jpTokyoJP42
ams-nlAmsterdamNL31
fra-deFrankfurtDE26
lon-gbLondonGB23
mad-esMadridES5
man-ukManchesterGB2
mxp-itMilanIT2
par-frParisFR18
sto-seStockholmSE2
waw-plWarsawPL2
tlv-ilTel AvivIL2
ga-usAtlantaUS21
il-usChicagoUS38
tx-usDallasUS28
hon-hi-usHonoluluUS2
lax-ca-usLos AngelesUS26
mex-mxMexico CityMX2
fl-usMiamiUS21
nj-usNewarkUS59
sjo-ca-usSanta ClaraUS11
wa-usSeattleUS14
tor-caTorontoCA4
mel-auMelbourneAU2
syd-auSydneyAU18
scl-clSantiagoCL1
sao-brSao PauloBR2

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.

Measure it yourself

Open the instrument, select Vultr, choose regions and run a sweep. Nothing is pre-selected and nothing runs until you press the button.