Short answer: on Linux and macOS run mtr -rwzbc 100 <host>. On Windows use the built-in pathping or WinMTR. To see the path from the internet instead of from your own network, use the free HardcoreDebug online MTR.
Linux
sudo apt install mtr-tiny # Debian / Ubuntu
sudo dnf install mtr # RHEL / Fedora
mtr -rwzbc 100 example.com # ICMP report
sudo mtr -rwzbc 100 -T -P 443 example.com # TCP 443
sudo mtr -rwzbc 100 -u example.com # UDPThe flags: -r report mode, -w wide output, -z show AS numbers, -b show both IPs and hostnames, -c 100 run 100 cycles.
macOS
brew install mtr
sudo mtr -rwzbc 100 example.comWindows
pathping -q 100 example.com
tracert example.compathping first traces the route, then sends the probes (100 per hop with -q 100). Expect it to take several minutes. WinMTR gives a live MTR view and can export the results.
How to read an MTR report
| Column | Meaning |
|---|---|
| Loss% | Share of probes with no reply from that hop. |
| Snt | Probes sent. |
| Last / Avg / Best / Wrst | Round-trip time in ms: most recent, average, lowest and highest. |
| StDev | Jitter. High values mean unstable latency. |
- Real loss starts at one hop and continues to every later hop, including the destination.
- Fake loss appears at one hop only. That router is just slow to answer probes.
- The last line matters most. If the destination looks good, the path is healthy.
Vendor-specific guides
- Zscaler MTR test
- Palo Alto MTR and traceroute
- FortiGate MTR and traceroute
- Check Point MTR and traceroute
- Cisco and Juniper MTR
Frequently asked questions
What is the MTR equivalent on Windows?
Windows has pathping built in, which traces the route and then measures loss per hop. WinMTR is a popular free graphical MTR for Windows.
How do I run MTR over TCP?
On Linux and macOS use mtr -T -P 443 <host> (it needs root). TCP mode is useful when firewalls drop ICMP or UDP probes.
What is a good MTR result?
0% loss at the final hop and steady latency. Loss or high latency at a middle hop that does not continue to the end is normal and caused by router rate limiting.
How many cycles should I run?
At least 100 for a support case (-c 100). Fewer cycles make a single dropped probe look like several percent of loss.