How to Check VPS Network Quality: Ping, Traceroute, MTR, and BGP

Contents
When choosing a virtual server, network quality plays an important role. It largely impacts website speed, APIs, VPNs, remote connections, and other services.
A VPS may have powerful hardware but still show poor performance, high latency, data loss, etc. Thankfully, you can check most of these conditions using a few standard networking tools such as ping, traceroute, MTR, and BGP analysis.
Check Latency With Ping
The simplest way to test a VPS connection and how fast it is is with ping:
ping your-vps-ip
Ping sends data to the VPS and measures the round-trip time (RTT). You’ll receive similar responses:
64 bytes from 203.0.113.10: icmp_seq=1 ttl=54 time=12.4 ms
64 bytes from 203.0.113.10: icmp_seq=2 ttl=54 time=12.1 ms
The lower the time, usually the better. However, the acceptable value depends on the physical distance between the VPS and the user who receives the data. More importantly, check whether the results are stable: fluctuations can be indicative of congestion or an unstable route.
Ping can also show data loss. If some data fails to reach the VPS, we recommend further investigating it through MTR.
Inspect Navigation With Traceroute
Ping tells you how long data has to travel to reach the VPS, but not which networks it’s passing through. You can use the traceroute command for that:
traceroute your-vps-ip
On Windows, use:
tracert your-vps-ip
Traceroute shows the routers between your computer and the VPS, and helps identify unexpected routing paths, transit network, or latency points.
Use MTR for More Detailed Testing
MTR combines ping and traceroute and is especially efficient at identifying persistent data loss and latency problems.
Run the following command:
mtr -rwzc 100 your-vps-ip
The report will show latency and data loss at each hop. When reviewing MTR results, check whether packet loss continues all the way to the destination; in transit, routers may drop packets due to limits or traffic deprioritization.
Test From Different Locations
A single test only shows the route between your current network and the VPS. Users in other countries or on different ISPs may take different routes.
If possible, we recommend testing the VPS from several locations, especially the regions where most of your target audience is located. It can show where latency and data loss occur.
It can also be helpful to repeat tests at different times of day to factor in network congestion.
What Does BGP Do?
BGP, or Border Gateway Protocol, is used by systems to exchange information about which IP networks they can reach.
Data centers, for example, use BGP with multiple providers to improve redundancy and control how traffic comes to and leaves their networks. If a data center has more than one ISP, routing policies allow traffic to go through another provider, aka another available path.
Information from BGP can also help explain traceroute results. By checking the VPS IP address, you can identify systems involved in a route and many other details.
How To Comprehensively Test Your VPS
For a quick evaluation of your VPS, we recommend using tests in this order:
- Ping for checking latency and the presence of data loss.
- Traceroute for identifying the paths of your traffic.
- MTR for investigating persistent latency or data loss.
- Testing from different locations to see different routes used.
- BGP for understanding the details of network connectivity.
You should look for stable latency, minimal data loss, and predictable routes.







