Find where packet loss appears
MTR combines traceroute and ping for every hop on the route
What the MTR report shows
MTR probes every hop on the route again and again and collects statistics for each of them.
Loss per hop
Ten rounds of probes show the share of lost packets at every router on the route.
Latency statistics
Last, average, best and worst round-trip time with the standard deviation for every hop.
The whole route
Up to 30 hops from each location, with routers on private networks marked.
Frequently asked questions
Short answers about how the check works and how to read its results.
How do I read an MTR report?
Start with the loss on the last hop. Loss that begins at one hop and continues to the destination points to a problem there. Loss on a single hop that disappears further down the route is usually just a router limiting its replies.
How many probes are sent?
Ten rounds, half a second apart, to every hop up to 30.
What does StDev show?
The standard deviation of the round-trip time, a measure of jitter. High values mean unstable latency.
When should I use MTR instead of ping?
Ping tells you that packets are lost or slow. MTR shows where on the route it happens.
All tools in one place
Check availability, latency and routing of websites, servers and IP addresses from different locations.