When evaluating, there are some important points to watch out for. Below we explain these in more detail and show why they are important for the analysis. If you pay attention to these aspects, you can better identify and narrow down the cause of the problem.
If you see packet loss in the results, this indicates possible network problems. A small, temporary packet loss of 1-2% is usually uncritical; higher values indicate more serious issues. Packet loss can cause delays or connection drops. If the loss is evenly distributed across all hops, the problem is likely in your own network or on the server side. If the loss occurs only at a specific hop or area, the problem is likely at that node or the connection to the next. Important: Small losses at the first hops belonging to your local network are not necessarily critical, as these devices often prioritize ICMP requests (like Ping) lower and sometimes discard them.
Latency values (Avg, Best, Worst) give you insight into the speed and stability of the connection. If you see that latency at a specific hop is consistently high, this can indicate network congestion or a slow router. A sudden increase in latency between two hops points to a possible bottleneck. Normally, latency increases gradually on the way to the destination. However, watch out for sudden, sharp spikes, which often signal a problem. Comparing outbound and return paths also helps detect asymmetric issues β i.e., when traffic in one direction has problems.
With a detailed analysis of these factors, you can well determine where the network problem lies β whether in your own network, with the internet provider, or somewhere on the way to the server.
To better understand this, we show you some diagnostic examples. We have compiled various scenarios that illustrate different situations and possible causes. This way, you learn to interpret the data better and diagnose network problems more effectively.
The following diagnostic examples are based on fictional WinMTR/MTR reports. The IP addresses, hostnames, and routes are completely made up and have no relation to real networks or hosts.
Example: Packet Loss on Client Side
Description
Here, packet loss occurs on the client side, visible on both outbound and return paths.
Outbound path (Client β Server)
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.1.1 15.0% 20 1.1 3.4 1.0 10.2 2.8
2. 10.0.0.1 10.0% 20 12.3 15.7 10.5 30.8 5.5
3. 172.16.0.1 0.0% 20 25.1 26.0 24.8 27.2 0.6
4. 203.0.113.5 0.0% 20 35.4 34.5 33.2 36.1 0.9
5. be1234.ccr42.isp.net 0.0% 20 50.6 49.8 49.1 51.5 0.8
6. be5678.ccr21.isp.net 0.0% 20 60.1 59.9 59.5 61.0 0.4
7. 198.51.100.10 0.0% 20 70.2 70.5 70.0 71.3 0.5
8. Destination IP (Server) 0.0% 20 80.2 80.0 79.5 81.2 0.6
Return path (Server β Client)
Host Loss% Snt Last Avg Best Wrst StDev
1. Destination IP (Server) 0.0% 20 80.2 80.0 79.5 81.2 0.6
2. 198.51.100.10 0.0% 20 70.1 70.4 69.8 71.2 0.5
3. be5678.ccr21.isp.net 0.0% 20 60.2 60.0 59.6 60.7 0.4
4. be1234.ccr42.isp.net 0.0% 20 50.1 50.2 49.5 51.0 0.5
5. 203.0.113.5 0.0% 20 35.5 35.0 34.5 36.0 0.4
6. 172.16.0.1 0.0% 20 25.2 26.1 24.9 27.3 0.7
7. 10.0.0.1 10.0% 20 15.8 16.5 15.0 35.2 6.2
8. 192.168.1.1 15.0% 20 2.0 4.0 1.2 12.0 3.8
Evaluation
The evaluation shows packet loss on the client side. Both paths show losses at the first hops (Hop 1 and 2), indicating a problem in the local network or router of the client.
Example: Packet Loss on Server Side
Description
Here, packet loss occurs on the server side, visible on both outbound and return paths.
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.1.1 0.0% 20 1.2 1.3 1.1 2.0 0.3
2. 10.0.0.1 0.0% 20 10.5 11.1 10.0 12.5 0.7
3. 172.16.0.1 0.0% 20 20.2 20.5 19.5 21.0 0.5
4. 203.0.113.5 0.0% 20 30.6 30.3 29.5 31.5 0.6
5. be1234.ccr42.isp.net 0.0% 20 50.2 50.5 49.5 51.0 0.4
6. be5678.ccr21.isp.net 0.0% 20 60.1 60.2 59.5 61.5 0.7
7. 198.51.100.10 10.0% 20 70.5 72.5 70.0 80.0 4.5
8. Destination IP (Server) 15.0% 20 85.3 90.2 85.0 105.0 7.0
Return path (Server β Client)
Host Loss% Snt Last Avg Best Wrst StDev
1. Destination IP (Server) 15.0% 20 85.3 90.2 85.0 105.0 7.0
2. 198.51.100.10 10.0% 20 70.5 72.5 70.0 80.0 4.5
3. be5678.ccr21.isp.net 0.0% 20 60.1 60.2 59.5 61.5 0.7
4. be1234.ccr42.isp.net 0.0% 20 50.2 50.5 49.5 51.0 0.4
5. 203.0.113.5 0.0% 20 30.6 30.3 29.5 31.5 0.6
6. 172.16.0.1 0.0% 20 20.2 20.5 19.5 21.0 0.5
7. 10.0.0.1 0.0% 20 10.5 11.1 10.0 12.5 0.7
8. 192.168.1.1 0.0% 20 1.2 1.3 1.1 2.0 0.3
Evaluation
The evaluation shows packet loss on the server side. Both paths show losses at the last hops (Hop 7 and 8), indicating a problem at the server.
Example: Latency Issues on Client Side
Description
Here, there are high latency times on the client side, visible on both outbound and return paths.
Outbound path (Client β Server)
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.1.1 0.0% 20 150.5 130.5 50.0 200.0 40.0
2. 10.0.0.1 0.0% 20 120.7 115.5 60.0 190.0 30.0
3. 172.16.0.1 0.0% 20 25.2 26.1 24.9 27.3 0.7
4. 203.0.113.5 0.0% 20 35.5 35.0 34.5 36.0 0.4
5. be1234.ccr42.isp.net 0.0% 20 50.1 50.2 49.5 51.0 0.5
6. be5678.ccr21.isp.net 0.0% 20 60.2 60.0 59.6 60.7 0.4
7. 198.51.100.10 0.0% 20 70.2 70.5 70.0 71.3 0.5
8. Destination IP (Server) 0.0% 20 80.2 80.0 79.5 81.2 0.6
Return path (Server β Client)
Host Loss% Snt Last Avg Best Wrst StDev
1. Destination IP (Server) 0.0% 20 80.2 80.0 79.5 81.2 0.6
2. 198.51.100.10 0.0% 20 70.1 70.4 69.8 71.2 0.5
3. be5678.ccr21.isp.net 0.0% 20 60.2 60.0 59.6 60.7 0.4
4. be1234.ccr42.isp.net 0.0% 20 50.1 50.2 49.5 51.0 0.5
5. 203.0.113.5 0.0% 20 35.5 35.0 34.5 36.0 0.4
6. 172.16.0.1 0.0% 20 25.2 26.1 24.9 27.3 0.7
7. 10.0.0.1 0.0% 20 120.7 115.5 60.0 190.0 30.0
8. 192.168.1.1 0.0% 20 150.5 130.5 50.0 200.0 40.0
Evaluation
The evaluation shows high latency on the client side. Both paths show increased latency at the first hops (Hop 1 and 2), indicating a problem at the client.
Example: Latency Issues on Server Side
Description
Here, there are high latency times on the server side, visible on both outbound and return paths.
Outbound path (Client β Server)
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.1.1 0.0% 20 1.2 1.3 1.1 2.0 0.3
2. 10.0.0.1 0.0% 20 10.5 11.1 10.0 12.5 0.7
3. 172.16.0.1 0.0% 20 20.2 20.5 19.5 21.0 0.5
4. 203.0.113.5 0.0% 20 30.6 30.3 29.5 31.5 0.6
5. be1234.ccr42.isp.net 0.0% 20 50.2 50.5 49.5 51.0 0.4
6. be5678.ccr21.isp.net 0.0% 20 60.1 60.2 59.5 61.5 0.7
7. 198.51.100.10 0.0% 20 200.5 210.0 200.0 230.0 10.0
8. Destination IP (Server) 0.0% 20 300.5 320.0 300.0 350.0 15.0
Return path (Server β Client)
Host Loss% Snt Last Avg Best Wrst StDev
1. Destination IP (Server) 0.0% 20 300.5 320.0 300.0 350.0 15.0
2. 198.51.100.10 0.0% 20 200.5 210.0 200.0 230.0 10.0
3. be5678.ccr21.isp.net 0.0% 20 60.1 60.2 59.5 61.5 0.7
4. be1234.ccr42.isp.net 0.0% 20 50.2 50.5 49.5 51.0 0.4
5. 203.0.113.5 0.0% 20 30.6 30.3 29.5 31.5 0.6
6. 172.16.0.1 0.0% 20 20.2 20.5 19.5 21.0 0.5
7. 10.0.0.1 0.0% 20 10.5 11.1 10.0 12.5 0.7
8. 192.168.1.1 0.0% 20 1.2 1.3 1.1 2.0 0.3
Evaluation
The evaluation shows high latency on the server side. Both paths show increased latency at the last hops (Hop 7 and 8), indicating a problem at the server.
Example: Routing Problem (ISP Routing)
Description
Here, the route from Client X to the server works without problems, while Client Y has routing problems with packet loss to the server. This indicates an issue with the internet service provider (ISP).
Outbound path (Client X β Server)
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.1.1 0.0% 20 1.2 1.3 1.1 2.0 0.3
2. 10.0.0.1 0.0% 20 10.5 11.1 10.0 12.5 0.7
3. 172.16.0.1 0.0% 20 20.2 20.5 19.5 21.0 0.5
4. 203.0.113.5 0.0% 20 30.6 30.3 29.5 31.5 0.6
5. be1234.ccr42.isp.net 0.0% 20 50.2 50.5 49.5 51.0 0.4
6. be5678.ccr21.isp.net 0.0% 20 60.1 60.2 59.5 61.5 0.7
7. 198.51.100.10 0.0% 20 70.2 70.5 70.0 71.3 0.5
8. Destination IP (Server) 0.0% 20 80.2 80.0 79.5 81.2 0.6
Outbound path (Client Y β Server)
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.1.1 0.0% 20 1.2 1.3 1.1 2.0 0.3
2. 10.0.0.1 0.0% 20 10.5 11.1 10.0 12.5 0.7
3. 172.16.0.1 0.0% 20 20.2 20.5 19.5 21.0 0.5
4. 203.0.113.5 30.0% 20 30.6 50.3 29.5 95.0 20.5
5. be1234.ccr42.isp.net 25.0% 20 80.2 120.0 70.0 250.0 55.0
6. be5678.ccr21.isp.net 10.0% 20 60.1 60.2 59.5 61.5 0.7
7. 198.51.100.10 0.0% 20 70.2 70.5 70.0 71.3 0.5
8. Destination IP (Server) 0.0% 20 80.2 80.0 79.5 81.2 0.6
Return path (Server β Client X)
Host Loss% Snt Last Avg Best Wrst StDev
1. Destination IP (Server) 0.0% 20 80.2 80.0 79.5 81.2 0.6
2. 198.51.100.10 0.0% 20 70.2 70.5 70.0 71.3 0.5
3. be5678.ccr21.isp.net 0.0% 20 60.1 60.2 59.5 61.5 0.7
4. be1234.ccr42.isp.net 0.0% 20 50.2 50.5 49.5 51.0 0.4
5. 203.0.113.5 0.0% 20 30.6 30.3 29.5 31.5 0.6
6. 172.16.0.1 0.0% 20 20.2 20.5 19.5 21.0 0.5
7. 10.0.0.1 0.0% 20 10.5 11.1 10.0 12.5 0.7
8. 192.168.1.1 0.0% 20 1.2 1.3 1.1 2.0 0.3
Return path (Server β Client Y)
Host Loss% Snt Last Avg Best Wrst StDev
1. Destination IP (Server) 0.0% 20 80.2 80.0 79.5 81.2 0.6
2. 198.51.100.10 0.0% 20 70.2 70.5 70.0 71.3 0.5
3. be5678.ccr21.isp.net 0.0% 20 60.1 60.2 59.5 61.5 0.7
4. be1234.ccr42.isp.net 0.0% 20 50.2 50.5 49.5 51.0 0.4
5. 203.0.113.5 0.0% 20 30.6 30.3 29.5 31.5 0.6
6. 172.16.0.1 0.0% 20 20.2 20.5 19.5 21.0 0.5
7. 10.0.0.1 0.0% 20 10.5 11.1 10.0 12.5 0.7
8. 192.168.1.1 0.0% 20 1.2 1.3 1.1 2.0 0.3
Evaluation
The evaluation shows a routing problem at the ISP. While the route from Client X is stable, Client Y has significant issues with packet loss and high latency.
Example: Packet Loss Only on Outbound Path (Client β Server)
Description
Here, packet loss occurs only on the outbound path (from client to server), while the return path (from server to client) is loss-free. This can indicate a problem in a network segment towards the server, e.g., due to faulty routers, congestion, or poor connection.
Outbound path (Client β Server)
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.1.1 0.0% 20 1.2 1.5 1.1 2.5 0.3
2. 10.0.0.1 0.0% 20 10.5 11.1 10.0 12.5 0.7
3. 172.16.0.1 0.0% 20 20.2 20.5 19.5 21.0 0.5
4. 203.0.113.5 10.0% 20 35.7 35.0 34.5 36.5 0.6
5. be1234.ccr42.isp.net 15.0% 20 50.6 55.5 50.0 70.0 6.0
6. be5678.ccr21.isp.net 10.0% 20 65.1 65.9 65.0 67.0 0.6
7. 198.51.100.10 0.0% 20 75.2 75.5 75.0 76.2 0.4
8. Destination IP (Server) 0.0% 20 85.3 85.0 84.5 86.0 0.5
Return path (Server β Client)
Host Loss% Snt Last Avg Best Wrst StDev
1. Destination IP (Server) 0.0% 20 85.3 85.0 84.5 86.0 0.5
2. 198.51.100.10 0.0% 20 75.2 75.5 75.0 76.2 0.4
3. be5678.ccr21.isp.net 0.0% 20 65.1 65.2 65.0 66.0 0.3
4. be1234.ccr42.isp.net 0.0% 20 50.2 50.5 49.5 51.0 0.5
5. 203.0.113.5 0.0% 20 35.7 35.0 34.5 36.5 0.6
6. 172.16.0.1 0.0% 20 20.2 20.5 19.5 21.0 0.5
7. 10.0.0.1 0.0% 20 10.5 11.1 10.0 12.5 0.7
8. 192.168.1.1 0.0% 20 1.2 1.5 1.1 2.5 0.3
Evaluation
The evaluation shows packet loss only on the outbound path. The losses are visible at hops 4, 5, and 6, indicating a problem on the way from client to server, e.g., congestion or faulty network devices. The return path has no losses; the connection in the other direction is stable.
Example: Packet Loss Only on Return Path (Server β Client)
Description
Here, packet loss occurs only on the return path (from server to client), while the outbound path (from client to server) is loss-free. This can indicate a problem in a network segment on the return path.
Outbound path (Client β Server)
Host Loss% Snt Last Avg Best Wrst StDev
1. 192.168.1.1 0.0% 20 1.2 1.5 1.1 2.5 0.3
2. 10.0.0.1 0.0% 20 10.5 11.1 10.0 12.5 0.7
3. 172.16.0.1 0.0% 20 20.2 20.5 19.5 21.0 0.5
4. 203.0.113.5 0.0% 20 30.6 30.3 29.5 31.5 0.6
5. be1234.ccr42.isp.net 0.0% 20 50.2 50.5 49.5 51.0 0.4
6. be5678.ccr21.isp.net 0.0% 20 65.1 65.2 64.5 66.5 0.5
7. 198.51.100.10 0.0% 20 75.2 75.5 75.0 76.2 0.4
8. Destination IP (Server) 0.0% 20 85.3 85.0 84.5 86.0 0.5
Return path (Server β Client)
Host Loss% Snt Last Avg Best Wrst StDev
1. Destination IP (Server) 0.0% 20 85.3 85.0 84.5 86.0 0.5
2. 198.51.100.10 0.0% 20 75.2 75.5 75.0 76.2 0.4
3. be5678.ccr21.isp.net 0.0% 20 65.1 65.2 64.5 66.5 0.5
4. be1234.ccr42.isp.net 10.0% 20 50.6 51.0 50.0 55.0 1.2
5. 203.0.113.5 15.0% 20 35.7 36.5 34.5 40.0 1.8
6. 172.16.0.1 10.0% 20 20.2 21.5 19.5 25.0 2.5
7. 10.0.0.1 0.0% 20 10.5 11.1 10.0 12.5 0.7
8. 192.168.1.1 0.0% 20 1.2 1.5 1.1 2.5 0.3
Evaluation
The evaluation shows packet loss only on the return path. The losses are visible at hops 4, 5, and 6 of the return path, indicating a problem on the way from server to client.