See per hop latency and packet loss continuously from the command line. 14.04.2026 | reading time: 2 min Want to know where packets slow down between you and a server Query mtr and get a live, per hop view that combines traceroute path discovery with ping style statistics. Quick session you can run now Reproduce this at your terminal to see mtr in action then read the output example shown below Run: ```\nmtr -rwzbc100 example.com\n``` Example report snapshot shows the columns you will read and their meaning \n```\nHOST: myhost Loss% Snt Last Avg Best Wrst StDev\n 1.|-- 192.168.1.1 0.0% 100 0.5 0.6 0.2 5.6 0.8\n 2.|-- 10.0.0.1 0.0% 100 10.1 12.3 9.8 30.2 5.0\n 3.|-- 203.0.113.45 2.0% 100 25.0 24.8 20.1 60.2 8.4\n``` Options that change the game Use report mode with count to script checks for automation for example `-r -c 100` will run a 100 probe batch; add `-n` to skip DNS lookups for faster results and `-u` to use UDP when ICMP is filtered; combine `-w` and `-z` to adjust display width and hide intermediate jitter to focus on loss and average latency. Where mtr shines in troubleshooting Run mtr from both ends of a connection to narrow down where loss or latency is introduced and correlate per hop loss with application complaints; remember some routers deprioritize or drop ICMP which can show apparent loss without breaking TCP so cross check with a TCP based probe or `tcpdump` when in doubt. Next steps and study paths Practice interpreting live reports and automating periodic runs to collect baselines and anomalies then expand to related tools and packet captures to validate findings and prepare for certifications such as CompTIA Linux+ or LPIC-1 using intensive exam preparation at bitsandbytes.academy. Join Bits & Bytes Academy First class LINUX exam preparation. network troubleshooting utilities
