Routing & Path
MTR Test: Traceroute with Real-Time Packet Loss and Latency
MTR (My Traceroute) combines the functions of ping and traceroute into a single powerful diagnostic tool. It continuously probes every router hop between you and the destination, reporting both latency and packet loss at each step so you can pinpoint exactly where network problems originate.
Launch in Mission ControlWhat It Measures
MTR measures the round-trip latency and packet loss percentage at every router hop along the path from your location to the target server. This reveals whether problems exist on your local network, your ISP's network, or at the destination.
How It Works
- Sends probes using increasing TTL values to reveal each hop
- Runs multiple rounds of probes to each hop for statistical accuracy
- Records average latency, best latency, worst latency, and packet loss per hop
- Displays results as a table showing the complete network path
Why It Matters
When your connection to a specific site is slow, MTR tells you exactly which hop is causing the problem. Problems early in the path (hops 1 to 3) are usually on your local network or ISP. Problems later in the path indicate issues with transit providers or the destination's network.
Understanding Your Results
Latency should increase gradually at each hop as distance grows. Any hop showing packet loss above 1% may be a problem, though some intermediate routers deprioritize ICMP probes. Packet loss only matters if it persists at that hop and all subsequent hops.
Ready to test?
Run MTR Test Now →Frequently Asked Questions
What is the difference between MTR and traceroute?
Standard traceroute sends a fixed number of probes and shows a single snapshot. MTR continuously sends probes and accumulates statistics over time, providing much more accurate packet loss percentages and revealing intermittent issues that traceroute misses.
Why do some hops show 100% packet loss?
Many core routers are configured to drop ICMP probes (the packets MTR uses) to reduce load or for security reasons. If only an intermediate hop shows packet loss but subsequent hops respond normally, the packet loss is a false positive from probe filtering, not a real network issue.
How do I interpret MTR results when sharing with my ISP?
When reporting issues, focus on where sustained packet loss begins. If hops 1 through 3 are clean and packet loss starts at hop 4 or 5, this points to a mid-ISP problem. Note the ASN and hostname of the problematic hop to help your ISP identify the affected router.
Can MTR diagnose WiFi problems?
Yes. The first hop in MTR is your router (typically 192.168.x.x). High latency or packet loss to your own router indicates a WiFi or local network issue rather than an ISP problem. This immediately tells you whether troubleshooting should focus on your home network or your ISP.
Related Tools
59+ Network Tools in One Dashboard
Mission Control gives you a complete terminal-style network diagnostics suite. Free, instant, no installation required.
Open Mission Control →