path tools
MTR Tool
MTR combines traceroute-style hop discovery with repeated probes. TraceRoo uses it to show where latency or loss appears across a path from the TraceRoo server to a target host.
What To Look For
- Loss that starts at one hop and continues through every later hop.
- Latency jumps that remain high after the hop where they begin.
- Intermittent final-hop loss that can affect applications and calls.
- Single-hop loss that disappears later, which is often ICMP rate limiting.
When To Use It
Use MTR for reachability issues, slow websites, VoIP path complaints, VPN path changes, or when ping works but the user experience still feels unstable.
Limitations
The result is from the TraceRoo server, not from the visitor's local network. For local access issues, compare this result with a user-side MTR or traceroute.
How To Read Results
- Loss at one middle hop can be harmless if later hops and the final target do not show the same loss.
- Loss that begins at a hop and continues to the destination is more likely to affect traffic.
- A latency jump matters most when it stays high for later hops, not when only one router replies slowly.
- The final hop is usually the most important line for application impact.
- Hostnames in the path can hint at carriers, exchanges, or regions, but routing names are not always accurate.
How To Use MTR Tool
- Enter a public hostname or IP address that represents the affected service.
- Choose enough cycles to see a pattern instead of a single noisy probe.
- Start reading at the final hop, then work upward for loss or latency that continues.
- Compare with Ping or Traceroute when you need a simpler reachability or route-shape check.
Troubleshooting Flow
Example Result
Hop 4: 35% loss
Hop 5: 0% loss
Final hop: 0% loss, 18 ms average
- Loss on one middle hop that disappears later is usually probe rate limiting.
- Final-hop loss matters more for application impact.
- A latency jump matters when it stays high on following hops.
Hop 7: 8% loss
Hop 8: 9% loss
Final hop: 9% loss, 88 ms average
- Loss that begins at one hop and continues to the final hop is worth escalating.
- Repeat the test to avoid chasing a one-time burst.
- For VoIP, compare with RTP Health results from an affected call.
What Good And Bad Results Look Like
- Final-hop loss is low or zero.
- Latency is stable after the route reaches the destination network.
- Any noisy middle hop does not carry forward.
- Loss starts at one hop and continues to the final hop.
- Latency jumps and stays high for later hops.
- Multiple runs show the same degraded destination behavior.
Common Mistakes
- Blaming a middle hop that shows loss while later hops are clean.
- Ignoring the final destination line.
- Running one short test and treating it as a long-term path pattern.
Practical Troubleshooting Workflow
- Read the final hop first.
- Look for loss or latency that continues downstream.
- Compare with Ping for a simpler destination-only view.
- Repeat the check later if the issue is intermittent.
FAQ
Why does one MTR hop show loss but later hops are fine?
That usually means the router is rate limiting or deprioritizing probe replies. Loss is more concerning when it starts at one hop and continues through the final destination.
Is MTR the same as traceroute?
MTR is similar to traceroute, but it repeats probes over time. That makes it better for spotting intermittent latency and packet loss patterns.
Does this test run from my computer?
No. TraceRoo runs the MTR-style check from the TraceRoo server. For local ISP or Wi-Fi issues, compare it with a test from the user's network too.