Master Network Diagnostics with MTR: Install, Run, and Analyze Results

What is MTR?

MTR (my traceroute) combines ping and traceroute into a single network diagnostic program. Unlike the default traceroute that uses UDP, MTR uses ICMP packets, which may be deprioritized by some network nodes, potentially yielding more accurate results.

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:

<code>sudo apt install mtr   # Debian/Ubuntu</code>

<code>sudo yum install mtr   # RedHat/CentOS</code>

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

Android: Download TracePing from the provided link (e.g.,

https://dwz.cn/KCdNPH4c

).

Basic Usage

Run

mtr qq.com

to view the route and connection quality from the local machine to qq.com . The output includes columns such as IP address, loss percentage, sent packets (Snt), last latency (Last), average latency (Avg), best latency (Best), worst latency (Wrst), and standard deviation (StDev).

Important Parameters

-r

or

--report

: Generates a static report by sending a fixed number of ICMP packets (default 10) and then exits.

-c

: Specify the number of packets to send.

-s

: Set the packet size (e.g.,

mtr -s 100 qq.com

sends 100‑byte packets).

-n

: Output only IP addresses without resolving hostnames.

Analyzing MTR Results

The Loss% column shows packet loss at each hop; a non‑zero loss may indicate a problem or an ICMP rate‑limit imposed by the provider. Compare adjacent hops to distinguish between genuine loss and artificial throttling.

Latency columns ( Last , Avg , Best , Wrst ) are measured in milliseconds. The Avg column is usually the most informative, while a high StDev (standard deviation) signals unstable latency at that hop.

Typical analysis steps:

Identify hops with high loss or latency spikes.

Determine whether the issue occurs in the local ISP, intermediate routers, or the destination’s ISP.

Check both forward and reverse paths (run MTR from the remote host back to you) for asymmetric problems.

Resolving Network Issues

Most routing problems are temporary and resolve within 24 hours. If persistent, provide the MTR report to your ISP or the upstream provider, highlighting the problematic hops. For high latency caused by long physical distances or peak‑time congestion, consider using a closer endpoint or alternative routing.