What Is MTR and Why It's Better Than Traceroute

Published March 5, 2026 · 6 min read

If you've ever used traceroute to diagnose a network problem, you've probably run into its biggest limitation: it only gives you a single snapshot. Network conditions change constantly. A traceroute run at 2pm might look fine, but your connection drops every evening at 8pm. MTR solves this by running continuously, building up statistics over time that paint a much clearer picture.

What Is MTR?

MTR stands for My Traceroute. It combines the route-mapping ability of traceroute with the continuous monitoring of ping. Instead of tracing the route once and stopping, MTR keeps sending packets and updating the results in real time.

For each hop along the route, MTR tracks:

• Packet loss percentage — How many packets never came back
• Average latency — The typical round-trip time
• Best and worst RTT — The range of latency you're experiencing
• Standard deviation (jitter) — How much the latency varies
• Packet count — How many probes have been sent to each hop

This makes MTR far more useful for diagnosing real-world network issues than a single traceroute ever could be.

Reading MTR Output

A typical MTR report looks something like this:

In this example, hop 4 stands out immediately: 2% packet loss, highly variable latency (21ms best but 180ms worst), and a large standard deviation. This hop is the problem area — something you'd never catch with a single traceroute if you happened to get a good reading.

Understanding Packet Loss

Packet loss is the most important metric MTR provides. Even small amounts of loss have a significant impact:

• 0% — Ideal. The connection is reliable.
• 1-2% — Noticeable in voice calls and gaming. Video streaming may buffer occasionally.
• 3-5% — Serious degradation. Web pages load slowly, video calls break up.
• 10%+ — The connection is effectively unusable for real-time applications.

Understanding Jitter

Jitter (standard deviation) measures how consistent the latency is. Low jitter means the connection is stable and predictable. High jitter means latency is all over the place.

For web browsing, jitter doesn't matter much. But for real-time applications — video calls, gaming, VoIP — high jitter is devastating. Your voice packets arrive at different intervals, causing choppy audio. Game inputs register at inconsistent times, causing rubberbanding.

A connection with 50ms average latency and 2ms jitter will feel better than one with 30ms average and 20ms jitter.

MTR vs. Traceroute: When to Use Each

Use traceroute when you need a quick check of the path your packets take. It's fast, gives you the route map, and is great for understanding the general network topology between you and a destination.

Use MTR when you need to diagnose a performance problem. If your connection is slow, dropping, or inconsistent, MTR will show you exactly where and how often the problem occurs. Run it for at least 60 seconds — ideally 2-5 minutes — to get reliable statistics.

Reporting to Your ISP

If you're calling your ISP about a connectivity issue, an MTR report is the most useful thing you can provide. It shows:

1. Exactly which hop has the problem
2. Whether it's in your ISP's network or further upstream
3. How much packet loss and latency variation exists
4. That the problem is sustained, not just a momentary blip

Run MTR to a well-known destination like 8.8.8.8 (Google DNS) or 1.1.1.1 (Cloudflare DNS) for a clean baseline. Then run it to the service you're having trouble with. The comparison makes it easy to isolate whether the problem is with the route to a specific destination or with your connection in general.

Using MTR on iPhone with PingKit

PingKit brings MTR to your iPhone — no command line needed. Open the Tools tab, navigate to Testing, and tap MTR.

Enter a hostname or IP address, and PingKit starts probing immediately. You'll see the route build up hop by hop, with statistics updating in real time. Each hop shows packet count, loss percentage, and average latency. Color coding highlights problem areas: green for healthy, yellow for elevated latency, red for packet loss.

You can run MTR over WiFi to diagnose your home network, or over cellular to check your mobile provider's routing. Switch between them to compare — you'll often see very different paths and performance characteristics.

Tips for Better MTR Diagnoses

1. Run for at least 60 seconds. Short runs may miss intermittent problems. For a thorough check, run for 2-5 minutes.
2. Test multiple destinations. If every destination shows packet loss at hop 3, the problem is at hop 3. If only one destination is slow, the problem is further along.
3. Ignore loss at middle hops if the final destination shows 0% loss. Many routers deprioritize ICMP.
4. Compare WiFi vs. cellular. If WiFi shows problems but cellular doesn't, the issue is your ISP or home network.
5. Test at different times of day. Network congestion often follows predictable patterns — fine in the morning, degraded in the evening.