The best of ping and traceroute combined. Continuous network path analysis with per-hop packet loss from 50+ global locations.
Advanced network diagnostics that ping and traceroute alone can't provide
Unlike traceroute, MTR continuously sends probes to measure packet loss at each hop over time.
Get min, avg, max, and standard deviation for latency at each hop. Understand variance in network performance.
Combines route mapping with continuous performance measurement. The most comprehensive network diagnostic tool.
Catch problems that single-shot tools miss. Continuous monitoring reveals intermittent packet loss patterns.
Run MTR from 50+ locations worldwide. Compare network quality from different geographic perspectives.
Set thresholds for packet loss and latency. Get alerted with detailed hop-by-hop data for faster troubleshooting.
The power of ping and traceroute combined
See exactly what percentage of packets are lost at each hop. Pinpoint the problematic network segment.
Track total packets sent and received at each hop over the monitoring period.
Min, avg, max, and standard deviation reveal latency patterns that single measurements miss.
Identify which network provider owns each hop. Present evidence when filing support tickets.
| # | Host | Loss% | Avg | Best | Wrst |
|---|---|---|---|---|---|
| 1 | gateway.local | 0.0% | 1.2 | 0.8 | 2.1 |
| 2 | isp-edge.net | 0.0% | 8.4 | 7.2 | 12.3 |
| 3 | core.isp.net | 0.0% | 15.2 | 12.8 | 22.1 |
| 4 | peering.net | 2.4% | 45.8 | 38.2 | 89.4 |
| 5 | transit.net | 5.1% | 52.3 | 48.1 | 112.5 |
| 6 | dc-edge.net | 0.0% | 54.2 | 51.2 | 58.9 |
| 7 | server.example | 0.0% | 55.1 | 52.4 | 59.2 |
Common questions about MTR monitoring
Use traceroute for a quick snapshot of the network path. Use MTR when you need to diagnose intermittent issues, measure packet loss over time, or understand latency variance. MTR is especially valuable for troubleshooting VoIP, gaming, or real-time application issues.
If only one hop shows packet loss but subsequent hops don't, that router is likely rate-limiting ICMP responses (not a real problem). If packet loss appears at a hop AND continues to the destination, that hop is the problem source. Focus on where persistent loss begins.
For general web traffic, 1-2% loss might be acceptable. For VoIP, video conferencing, or gaming, even 0.5% can cause noticeable quality issues. For business-critical applications, aim for 0% packet loss. We recommend alerting on any loss above 0% for early detection.
Our MTR monitoring runs continuously at configurable intervals. Each test typically sends 10-100 probes over 10-60 seconds to gather meaningful statistics. Historical data is aggregated and stored for trend analysis and alerting.
MTR monitoring from 50+ global locations. Track packet loss and latency at every hop. The ultimate network troubleshooting tool.