How to Use MTR
MTR (My Traceroute) combines traceroute and ping: it shows the route packets take to the server along with the latency and packet loss at each hop. Support technicians use this tool to analyze connection problems.
When Do You Need MTR?
- The connection to the server feels laggy / delayed.
- You often get disconnected or timeouts.
- There is packet loss (actions feel unresponsive).
Destination Addresses
Use one of the following addresses when running MTR:
1.1.1.1(Cloudflare DNS)8.8.8.8(Google DNS)- The server IP provided by the technician (example:
103.42.xx.xx)
Choose Your Platform
How to Read the MTR Results
- Loss% → The percentage of packet loss at that hop.
- Snt → The number of packets sent.
- Last → The last latency (ms).
- Avg → Average latency.
- Best → Lowest latency.
- Wrst → Highest latency.
- StDev → Latency variation/jitter.
Note: If packet loss only appears at an intermediate hop but disappears at the last hop, that's usually normal (a router refusing ICMP for itself). What you need to pay attention to is packet loss at the last hop (the destination).