Master MTR: Install, Run, and Analyze Network Paths Across Platforms

Common tools like ping, tracert, and nslookup check host connectivity, but Linux offers a more powerful utility called mtr (My Traceroute) that combines ping and traceroute into one network diagnostic program.

Installation

Windows : Download the BestTrace tool from https://cdn.ipip.net/17mon/besttrace.exe or get the portable MTR client from the GitHub releases page https://github.com/oott123/WinMTR/releases.

Linux : Install via package manager.

# Debian/Ubuntu
apt install mtr
# RedHat/CentOS
yum install mtr

macOS : Search for “Best NetTools” in the App Store and install.

Android : Download TracePing from Google Play (or via https://dwz.cn/KCdNPH4c if Play Store is inaccessible).

Basic Usage

Run mtr qq.com to view the route and connection quality to qq.com :

mtr qq.com

The output columns include:

IP address

Loss (packet loss rate)

Snt (sent packets)

Last (latency of the last packet)

Avg (average latency)

Best (minimum latency)

Wrst (maximum latency)

StDev (standard deviation, indicating stability)

-r or --report : Generates a static report by sending 10 ICMP packets; without it, mtr runs continuously.

-s or --packetsize : Sets the ping packet size, e.g., mtr -s 100 qq.com sends 100‑byte packets.

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

-n : Disables hostname resolution, showing only IP addresses.

MTR Result Analysis

Focus on loss and latency columns. The Loss% column shows packet loss per hop, while Avg, Last, Best, and Wrst display round‑trip times in milliseconds. A high standard deviation (StDev) indicates inconsistent latency, suggesting the average may not reflect true performance.

When loss appears at a hop but subsequent hops show none, the loss is likely due to ICMP rate limiting rather than a real problem. Consistent loss across multiple hops points to an actual network issue.

Latency spikes often occur between specific hops, possibly due to geographic distance, misconfigured routers, or congestion. However, high latency does not always mean a faulty router; it may stem from the return path, requiring a bidirectional MTR test.

Resolving Issues

Most routing problems are temporary and resolved by ISPs within 24 hours. If persistent, provide the MTR report to the ISP or service provider for investigation. For chronic issues caused by long physical distances or peak‑time congestion, consider accessing a closer node or CDN.