Master Network Troubleshooting with MTR: Install, Use, and Analyze Results

Common tools like ping, tracert, and nslookup check host connectivity, but the Linux tool mtr (my traceroute) combines ping and traceroute for richer network diagnostics.

Unlike traceroute, which defaults to UDP packets, mtr uses ICMP packets, which may be deprioritized by some network nodes, potentially yielding lower‑than‑actual performance data.

Installation

Windows: download BestTrace or the portable WinMTR from GitHub ( GitHub releases ).

Linux: install via package manager.

<code># Debian/Ubuntu
sudo apt install mtr
# RedHat/CentOS
sudo yum install mtr</code>

macOS: search for "Best NetTools" in the App Store and install.

Android: download TracePing from Google Play or directly from this link .

Usage

Run the following command to view the route and connection quality from the local machine to

qq.com

:

<code>mtr qq.com</code>

Output Parameters

First column: IP address of each hop.

Loss: packet loss percentage.

Snt: number of packets sent.

Last: latency of the most recent packet.

Avg: average latency.

Best: minimum latency.

Wrst: maximum latency.

StDev: standard deviation (stability) of latency.

Parameter Explanation

-r or --report : generate a static report (default sends 10 ICMP packets). Without this flag, mtr runs continuously.

-c or --report-cycles : specify the number of packets to send (default 10).

-s or --packetsize : set the size of each ping packet.

<code>mtr -s 100 qq.com</code>

-n : output only IP addresses, suppress hostname resolution.

<code>mtr -n qq.com</code>

MTR Result Analysis

The Loss% column shows packet loss per hop; the Snt column records how many packets were sent. The Last , Avg , Best , and Wrst columns display round‑trip times in milliseconds. The StDev column indicates latency variance—high values suggest unstable paths.

Network Packet Loss

If a hop shows a loss percentage, it may indicate a problem at that node or a deliberate ICMP rate limit. Comparing the next hop helps differentiate between the two. Example screenshots illustrate human‑imposed limits versus genuine loss.

Network Latency

Latency columns (Last, Avg, Best, Wrst) reveal round‑trip times; spikes often occur between specific hops due to distance, routing issues, or congestion. The following image shows a latency jump between hops 11 and 12.

Resolving Issues Based on MTR

Most routing problems are temporary and resolve within 24 hours. If persistent, provide your ISP with the MTR report and relevant data; without concrete metrics, they cannot troubleshoot effectively. In many cases, high latency stems from long physical distances or peak‑time congestion, especially across continents, and the best mitigation is to connect to a nearer node.