Looking Glass
natbox runs on three host servers in the EU, on the same provider's network. New servers are placed automatically on the host with room, so test all three. Download speed per customer server is capped at 100 Mbit/s each way, and the test files are capped the same way, so a download here shows roughly what your own server would get on your connection.
Servers and test files
| Host | Location | IPv4 (ping) | IPv6 (ping) | Test downloads |
|---|---|---|---|---|
| Server one | EU | 5.189.155.145 | 2a02:c207:2370:7002::1 | 10 MB · 100 MB |
| Server two | EU | 5.189.142.51 | 2a02:c207:2323:398::1 | 10 MB · 100 MB |
| Server three | EU | 92.242.190.191 | 2a02:c207:2373:7988::1 | 10 MB · 100 MB |
The files are random data, so compression can't make them look faster. Server one's files come over HTTPS from our website, the others over plain HTTP.
How to test
On Linux or macOS:
# round trip and packet loss (20 pings)
ping -c 20 92.242.190.191
# the route, hop by hop, with loss per hop
mtr -rwc 50 92.242.190.191
# download speed (shows the average at the end)
curl -o /dev/null http://s3.natbox.io/100MB.bin
On Windows (Command Prompt):
ping -n 20 92.242.190.191
tracert 92.242.190.191
curl -o NUL http://s3.natbox.io/100MB.bin
Use the IPv6 address with ping -6 (or ping6) to check your IPv6 path; every natbox server has its own routed /80 of IPv6.
What to look for
- Round trip: in our measurements from probes around the world, the median from Europe was 18 ms and the farthest (Sydney) about 293 ms; from China it is about 230–290 ms.
- Packet loss: a few percent is normal on long international routes, especially in the evening. On lossy routes, turn on BBR on your server: in our tests it made downloads 10 to 50 times faster.
- From China: see Using a natbox VPS from China for hourly measurements from China Mobile, Unicom and Telecom.
Try a real server
The test files show the network. To test everything else (CPU, disk, your own software), get a free trial server for a month, or a burner server for 24 hours.