What are MTR and WinMTR?
MTR (My Traceroute, and originally called Matt's Traceroute) is a Linux/Unix utility that combines Ping and Traceroute functions into one easy-to-use program. WinMTR is a Windows clone of MTR. MTR is run on a computer to provide detailed hop test data (a series of brief measurements). MTR does not require installation or system admin rights.
How do I run MTR?
- Browse to https://winmtr.en.uptodown.
- Follow instructions to download the compressed file.
- After downloading has completed, extract the folder to the desktop (or other desired location).
- Open the folder and run the program (WinMTR.exe or WinMTR64.exe).
- For Host use the correct 8x8 media server based on the phone location (e.g. West Coast: 126.96.36.199 and East Coast 188.8.131.52)
- Press Start.
- Run test for minimum of 2 minutes and a maximum of 5 minutes. Click Stop.
What does MTR do?
MTR provides test results that are a combination of ping and Traceroute. Where Traceroute makes 3 ping tests to each hop, MTR continuously sends ping requests to each hop until you stop the test. For each hop in the path, MTR displays the:
- Average % of packet loss.
- Total packets sent and received.
- Best, average, worst and last latency test result.
There are options to copy or export the results as plain text or HTML.
How do I interpret MTR results? What do they mean?
Like a normal Traceroute, we are looking for something that replicates down the route list, through to the end. A single hop with high latency isn’t a problem—unless it’s the last one.
If a hop introduces latency, or packet loss, and that continues through the remaining hops, we have identified a problem.
In the screenshot below, we see one hop with 23% packet loss, and one with a worst-case latency of 52ms. Neither of them is a problem since they don’t continue to the next hop in the list.
In another case, we see poor results starting at hop 11, and replicating through to the destination host. If the host was in the US and not Australia, this would be a concern.
One other thing to note is the variation in latency–jitter. There is a small amount of jitter in hop 12 (above), but it does not continue through. Even though we have higher latency in the final six hops, jitter is very good and not a concern.