Master Network Diagnostics with MTR: Installation, Commands, and Result Analysis

MTR (My Traceroute) combines ping and traceroute into a single network diagnostic program, offering deeper insight into connectivity than the standard tools.

Installation Methods

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

Linux: sudo apt install mtr (Debian/Ubuntu) or sudo yum install mtr (RedHat/CentOS).

macOS: install Best NetTools from the App Store.

Android: download TracePing from Google Play or via the direct link https://dwz.cn/KCdNPH4c.

Basic Usage

Run mtr qq.com to display the real‑time route and latency from the local host to the target.

Output Columns Explained

IP address (first column)

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)

Key Parameters

-r or --report : generate a static report after sending a fixed number of ICMP packets (default 10). Without this flag, MTR runs continuously.

-s or --packetsize : set the size of each ping packet, e.g., mtr -s 100 qq.com. A negative value makes the size random.

-c : specify the number of packets to send, e.g., mtr -c 100 qq.com.

-n : suppress hostname resolution, showing only IP addresses, e.g., mtr -n qq.com.

MTR Result Analysis

The report provides loss percentages, packet counts, and latency statistics for each hop. Pay special attention to the Loss% and Avg columns; high loss or unusually high average latency often indicate a problem.

Standard deviation (StDev) shows latency variability. A large StDev suggests inconsistent performance at that hop, which may mask the true average latency.

Network Loss

If a hop shows a loss percentage while subsequent hops do not, the loss is likely due to ICMP rate limiting by that router rather than a real fault. Conversely, consecutive hops with loss indicate a genuine issue.

Network Latency

Latency typically increases with hop count due to physical distance and link quality. Sudden spikes (e.g., from hop 11 to 12) may point to a congested or misconfigured router.

Resolving Issues Based on MTR

Most routing problems are transient and resolve within 24 hours. If persistent loss or latency is observed, share the MTR report with your ISP or upstream provider, indicating the problematic hops.

When loss appears only on the return path, perform a reverse MTR test to capture the reverse route.

Short‑term spikes caused by ICMP rate limiting or temporary congestion are usually harmless; application‑level retries can compensate for occasional packet loss.

Source: cloud.tencent.com