Distance on a map does not equal network distance. Before you commit to a location, spend five minutes measuring the actual latency from where your users are.
1. Get a test IP
Open a support ticket and tell us which location you are considering — we will provide a test IP you can ping. For some popular locations we also publish test IPs directly on the location pages of our website.
2. Ping it
From your computer (or better, from where your users actually are):
ping -c 10 TEST_IP
On Windows: ping -n 10 TEST_IP. Look at the average time and packet loss. Rough guide: under 50 ms feels instant, 50–150 ms is fine for most workloads, above 200 ms is noticeable for interactive use.
3. Check the route with mtr or traceroute
mtr --report TEST_IP
(Windows: tracert TEST_IP.) This shows every hop between you and the server. Loss at the final hop or sustained high latency mid-route matters; loss at a single middle hop that disappears afterwards is usually just an ICMP-deprioritising router and is harmless.
4. Test at different times
Routes can be congested during local peak hours. If the location matters to you, ping once in the morning and once in the evening before deciding.
5. Your safety net
VPS orders come with a 7-day money-back guarantee — if the real-world performance does not match your tests, open a ticket within 7 days for a full refund.
