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

What Is MTR?

MTR (my traceroute) is a network diagnostic tool that combines the functionality of ping and traceroute, using ICMP packets by default, which can give more accurate path and loss information than traditional traceroute that uses UDP.

Installation

Windows : Download BestTrace from https://cdn.ipip.net/17mon/besttrace.exe or the portable WinMTR from GitHub (https://github.com/oott123/WinMTR/releases).

Linux :

sudo apt install mtr

sudo yum install mtr

macOS : Install “Best NetTools” from the App Store.

Android : Install TracePing from Google Play or download it directly from https://dwz.cn/KCdNPH4c.

Basic Usage

Run mtr qq.com to see the route and latency to the host.

Output Columns

IP address (first column)

Loss – packet loss percentage

Snt – number of packets sent

Last – latency of the last packet

Avg – average latency

Best – minimum latency

Wrst – maximum latency

StDev – standard deviation (stability)

Important Parameters

-r

or --report: Send a fixed number of ICMP packets (default 10) and output a static report. -c count : Specify the number of packets to send, e.g., mtr -c 100 qq.com. -s size : Set the packet size, e.g., mtr -s 100 qq.com. -n: Display numeric IP addresses only, without DNS resolution.

Analyzing Results

Focus on the Loss% and latency columns ( Last , Avg , Best , Wrst ). High loss on a hop indicates a problem; if subsequent hops show no loss, the issue may be an ICMP rate limit. Large StDev values suggest unstable latency.

When latency spikes between two hops, it often reflects physical distance or congestion. Verify both forward and reverse paths with a bidirectional MTR test.

Resolving Issues

Most routing problems are temporary; contact your ISP with the MTR report if loss persists. For long‑distance or peak‑time congestion, consider using a closer endpoint or alternative routing.