Looking glass
Choose the location closest to your users
Pick where your users are and see how far each of our 10 data centers is from them. Then ask for a test IP in the one you like and measure it yourself.
Closest location: London (~5 ms)
Figures marked measured are medians of real measurements (WonderNetwork, September 2026). The others are estimated: fibre at about two-thirds of the speed of light, 1.25 × the straight-line distance, plus 5 ms for equipment and local routing — typically within ±5 ms of reality. Ask for a test IP to measure your own route.
Request a test IPLatency from your users to each location
Test before you buy
Measure the real route from your network
Ask for a test IP in any location: we send a ping and traceroute target and a link to a 1 GB test file, usually within the hour, valid for seven days.
AmsterdamAMS · request a test IP
FrankfurtFRA · request a test IP
HelsinkiHEL · request a test IP
BucharestBUH · request a test IP
StockholmSTO · request a test IP
LondonLON · request a test IP
New YorkNYC · request a test IP
MiamiMIA · request a test IP
Los AngelesLAX · request a test IP
SingaporeSIN · request a test IP
What to run once you have it
# Latency and loss, hop by hop
$ mtr -rwzc 100 <test-ip>
# Throughput from your side
$ curl -o /dev/null -w '%{speed_download}\n' http://<test-ip>/1GB.binReading the results
- Latency close to the estimate above means a direct route; much higher usually means traffic detours through another city.
- Loss should be 0% on the last hop. Loss on intermediate hops only is usually ICMP rate limiting, not a problem.
- Throughput from a single connection is limited by your own line and by distance; parallel downloads show what the port can do.