MTR online
Find recurring packet loss and delay along a route, hop by hop, from our server or from other countries. Free, no sign-up.
MTR
Best for: Finding recurring loss or delay along a route, hop by hop.
More options
Runs from our server, over IPv4.
Results appear here after you press Run MTR.
What it does
MTR combines ping and traceroute. It sends repeated probes along the path and shows loss and delay for each hop, so you see patterns that a single traceroute misses.
Network providers often ask for one when you report a slow or unstable connection.
How to read the result
- Loss %
- The share of probes a hop did not answer. Only loss that carries through to the last hop affects traffic.
- Average and worst
- Typical delay at that hop and its slowest reply. A large gap between them suggests the delay is not steady.
- Last hop
- The destination itself. Start reading here: if it shows no loss, loss at earlier hops is usually harmless.
Common questions
Why does a hop show loss when the destination has none?
That router limits how often it answers probes, but it still forwards traffic. This is normal and does not affect your connection.
How do I read an MTR report?
Start at the last hop. If it has loss, go backwards to the first hop where the loss begins and carries on to the end. That is where to look.
Can I send this to my provider?
Yes. Switch the result to Text and press Copy to paste it into a support ticket.
What is the difference between MTR and traceroute?
Traceroute shows the path once. MTR repeats the probes and adds loss and delay statistics per hop.
Related tools
Check it around the clock.
These tools check once. PingOmni Monitor checks your sites, certificates, domains and servers around the clock, as often as every 30 seconds, and tells you the moment one fails. Free for 30 monitors, with no card.