About this tool
Run an online MTR report that combines traceroute and continuous ping to expose packet loss and latency spikes on every hop of the path.
- Enter the host you want a sustained path-quality report for.
- Select the probe region closest to the affected users.
- Watch Loss% and Avg columns per hop; the first hop showing sustained loss usually marks the fault boundary.
Frequently asked questions
- When should I use MTR instead of traceroute?
- Use MTR when a problem is intermittent. It sends packets continuously along the path and accumulates statistics, so brief loss bursts and latency spikes show up in the Loss% and Best/Worst columns instead of hiding in one snapshot.
- How do I read MTR output?
- Each row is one hop. Look for the first hop where sustained loss appears and stays through the remaining hops: that hop marks where the network path degrades. If loss appears mid-path but disappears later, the router may just be rate-limiting ICMP.
- Is MTR hard on the target network?
- An MTR report sends roughly one packet per second per hop, similar to a slow continuous ping. It is safe for diagnostics but should not be used for load testing.