Discover our new Ryzen 9 server here
Site Logo

Navigate Server4You
Dedicated ServerVirtual ServerFeaturesContact

MTR Report for Network Diagnostics

An MTR report (My Traceroute) combines the functionality of ping and traceroute to diagnose network issues such as packet loss and high latency. Our support team may request one to investigate connection problems.

Why do we need an MTR?
A number of factors can affect your connection speed. An MTR report helps us pinpoint exactly where in the connection path a problem might be occurring.

1. Install MTR

First, install the MTR tool if it is not already available on your system.

Linux

Debian / Ubuntu
apt-get update apt-get install mtr
CentOS / AlmaLinux
yum install mtr

Windows

For Windows, we recommend WinMTR, a graphical version of the tool. You can download it for free from SourceForge: Download WinMTR

2. Run the MTR Report

To give our support team enough data to work with, the MTR test must run for at least 1000 packets.

Linux

Run the following command in your terminal. Replace DESTINATION_IP with the IP address you want to test.

Run MTR on Linux
mtr -r -c 1000 DESTINATION_IP

Windows (WinMTR)

1.Launch WinMTR
2.Enter the target IP address in the Host field
3.Click Start
4.Wait until the Sent column reaches 1000
5.Click Stop and then Copy Text to clipboard to capture the report

3. Understanding the MTR Report

The MTR output shows every hop between you and the destination server. The most important columns are Host, Loss% (packet loss), Avg (average latency), and Wrst (worst value).

Bidirectional reports are essential:
The path your data takes to our server is often completely different from the path it takes back to you — this is called asymmetric routing. A problem may only exist on the return path. Without reports in both directions, we cannot get a complete and accurate picture of the connection.
Packet loss rule:
A real network problem generally only exists when significant packet loss persists or increases across multiple consecutive hops — including the final destination.
Latency rule:
Look for a sudden spike in Avg latency that persists to the destination, or a Wrst value significantly higher than the average, indicating intermittent lag.

Examples: Good vs. Problematic

Interpreting Results
No Issue (Mid-path Loss)
Real Issue (Packet Loss)
Real Issue (Latency Spike)

Hop 3 shows 50% packet loss — however, it does not continue to subsequent hops. The final destination (Hop 5) shows 0% loss.

HostLoss%SntAvgWrst
1. your-router.local0.0%10001.25.5
2. your-isp.net0.0%10005.515.2
3. some-backbone.net50.0%100010.220.1
4. another-peer.net0.0%100010.522.0
5. server4you.com0.0%100011.025.0

Conclusion: No issue. The loss at Hop 3 is caused by that router de-prioritizing ping requests. The network is healthy.

4. Submitting the Report to Support

When sending the report to our support team, please make sure to include the following:

✓The MTR report from your client to our server
✓The MTR report from our server back to your client
✓If possible, an MTR report between two of your Server4You servers
✓The date and time when you ran the reports

Experiencing network issues?

Submit your MTR report directly via the ticket system in your PowerPanel — our support team will analyze it promptly.

Open a Support Ticket