FAQs

Why do some hops show *?
Routers may not respond to probes, or firewalls block diagnostics. Subsequent responsive hops are normal.
How many packets should I send?
10–20 for quick checks; 50–100 for intermittent issues. More packets increase accuracy but take longer.
What indicates a network issue?
Consistent packet loss/latency rising at or beyond a specific hop typically signals congestion or faults.

MTR Traceroute Tool

Path Analysis Latency Packet Loss
Anish Nath
MTR Configuration
Target Host
Enter hostname or public IP address
Quick Presets
Advanced Options
Metrics Guide
Loss % Packet loss rate
Last Most recent RTT
Avg Average latency
Best Minimum latency
Worst Maximum latency
StDev Jitter/variation
MTR Results

MTR results will appear here

Enter a target and click Start MTR Trace
-
Hops
-
Avg ms
-
Loss %
-
Jitter
# IP Address Loss Last Avg Best Worst StDev
CLI Commands
Basic MTR (Linux)
$ mtr -r -c 10 google.com
MTR with TCP mode
$ mtr -r -T -P 443 google.com
Windows tracert
C:\> tracert google.com
Related Network Tools
Ping Tool

Test ICMP connectivity
Curl Tool

HTTP/HTTPS connectivity
Port Scanner

Scan open ports
DNS Lookup

Query DNS records
WHOIS Lookup

Domain registration info
Subnet Calculator

Calculate IP subnets

Support This Free Tool

Every coffee helps keep the servers running. Every book sale funds the next tool I'm dreaming up. You're not just supporting a site — you're helping me build what developers actually need.

500K+ users
200+ tools
100% private
☕ One-time support Buy me a coffee 📚 Learn & support 9-Book Bundle - $9 Stay updated Follow @anish2good
Privacy Guarantee: Private keys you enter or generate are never stored on our servers. All tools are served over HTTPS.
Understanding MTR & Network Diagnostics
What is MTR?

MTR (My TraceRoute) is a powerful network diagnostic tool that combines the functionality of traceroute and ping. It continuously probes each hop along the network path, providing real-time statistics on packet loss, latency, and jitter - making it invaluable for diagnosing intermittent network issues.

How MTR Works
StepProcessResult
1Send packets with TTL=1First router responds
2Increment TTL for each hopDiscover next router
3Send multiple packets per hopCalculate statistics
4Continue until destinationComplete path map
Good Results
  • 0% packet loss throughout
  • Consistent latency increases
  • Low jitter (<5ms)
  • All hops responding
Problem Indicators
  • >5% loss at final destination
  • Sudden latency spikes
  • High jitter (>20ms)
  • Loss increases toward destination
Interpreting Results

Note: Packet loss at intermediate hops doesn't always indicate a problem. Many routers rate-limit ICMP responses. Focus on the final destination's statistics and look for patterns where loss begins and continues to the destination.

Quick Access