How to Perform a Network Test Using MTR

If you are experiencing network issues with your VPS, server, or IP Transit services, performing a network test with MTR (My Traceroute) can help you gather more detailed insights into the connectivity and identify the exact location of any potential issues. Here's how to run an effective network test using MTR:

1. Install MTR:
   • If MTR is not already installed on your server, you can install it using the following command:
     For Debian/Ubuntu-based systems:

     • apt-get install -y mtr

   • For CentOS/RHEL-based systems:

     • yum install -y mtr

   • For Windows systems:

     • Install WinMTR tool

2. Run MTR Test:
   • To begin the test, run the mtr command followed by the IP address or domain name of the destination server you want to test. For example:
     • mtr google.com
3. Understanding the Output:
   • MTR will show you a series of hops between your server and the destination. Each hop represents a network device (like a router or gateway) that your data passes through.
   • The columns will provide you with the following data for each hop:
     • Host: The IP address or hostname of the network device.
     • Loss: The percentage of lost packets at each hop.
     • Snt: The number of packets sent to that hop.
     • Last: The last measured latency (in ms).
     • Avg: The average latency.
     • Best: The best latency recorded.
     • Worst: The worst latency recorded.
4. Analyzing the Results:
   • If you notice high latency or packet loss in specific hops, this could indicate where the problem is occurring. Generally, packet loss or latency spikes closer to the destination are often caused by external network issues, while issues closer to your server could indicate problems with your local network or hosting provider.
   • If the issue is observed in the first few hops (closer to your server), it's a good idea to check the server's network configuration and contact your hosting provider for assistance.
   • If the problem is later in the trace, it could be related to an issue with an upstream provider or the destination server itself.
5. Contacting Support:
   • If MTR results point to issues that cannot be resolved on your own, please contact our support team. Provide the MTR test output, including the affected hops and any other relevant details, so we can assist you more effectively.
   • Open a support ticket for further assistance.

Running an MTR test provides you with valuable data to identify and troubleshoot network issues more efficiently. If you need help interpreting the results or resolving connectivity problems, our support team is here to assist.