Plan your network tests before ordering.
Use latency, routing and throughput tests to assess a connection from your own network. The targets shown here are documentation examples. Ask support for a working endpoint for the selected location before running the commands.
Amsterdam, Netherlands
Catalogue location · documentation example
No measured latency result is published here.
Bucharest, Romania
Catalogue location · documentation example
No measured latency result is published here.
Reykjavík, Iceland
Catalogue location · documentation example
No measured latency result is published here.
Sofia, Bulgaria
Catalogue location · documentation example
No measured latency result is published here.
Chișinău, Moldova
Catalogue location · documentation example
No measured latency result is published here.
Panama City, Panama
Catalogue location · documentation example
No measured latency result is published here.
Victoria, Seychelles
Catalogue location · documentation example
No measured latency result is published here.
Kansas City, United States
Catalogue location · documentation example
No measured latency result is published here.
Four tests that tell you something.
These are command examples. Replace the sample address or TEST_HOST with the working target supplied for your service. Results depend on the route, endpoint and time of the test.
Latency and jitter
ping -c 50 198.51.100.10
Fifty packets, not four. Read the mdev figure at the end — jitter matters more than mean latency for anything interactive, and a low mean with high jitter is worse than a slightly higher stable path.
Route quality
mtr --report --report-cycles 50 198.51.100.10
Shows loss at every hop. Loss at an intermediate hop with none at the destination is usually ICMP rate-limiting, not a real problem. Loss that persists to the final hop is real.
Throughput
curl -o /dev/null -w "%{speed_download}\n" https://TEST_HOST/1000MB.testA single stream is limited by your own TCP window and by any congested hop in between. Run it three times at different hours before drawing conclusions.
Multi-stream throughput
aria2c -x8 -s8 -d /tmp https://TEST_HOST/1000MB.test
Eight parallel streams. Compare this with a single-stream result. A difference can reflect per-connection limits, routing, congestion or endpoint behaviour; it does not identify one cause on its own.
Prefer to test from inside the network?
Nano in Amsterdam costs $8.26 for 3 months prepaid, with one server, free Linux and no paid add-ons. Review the acceptable-use rules before benchmarking. The published 7-day refund policy covers an eligible first VPS term, subject to network fees and stated exclusions. Read the refund terms before ordering.
Choose your server and see the total.
Choose your location, resources and term. Pay in crypto after reviewing the total; payment is verified automatically before your VPS is prepared.
Minimum 3-month VPS term · No ID upload in checkout · 7-day refund policy with exclusions