How to Run a Traceroute for Gaming
Answer
Traceroute is how you localise where a latency or loss problem appears on the network. Use WinMTR on Windows or mtr on macOS/Linux — one-shot tracert is not enough. Read loss and RTT at the final hop first; middle-hop noise is usually cosmetic.
5 min readReviewed Jul 2026TTML Editorial
Windows / macOS / LinuxFree toolingEvidence-based
Disclosure: We may earn a commission if you purchase through links on this page. This never affects our reviews.
Mental model
What each hop is telling you
Traceroute — hop-by-hop
Every hop is a router. Each RTT is a round-trip to that router, not a segment of the total path. The number that matters most is loss and RTT at the destination — everything before is context for where a problem originates.
Commands
The right command for your OS
- Windows: install WinMTR and run against the game server IP. For a quick one-shot, use tracert <target>.
- macOS: brew install mtr, then sudo mtr -rwc 300 <target> for a 300-cycle report.
- Linux: apt install mtr-tiny, then sudo mtr -rwc 300 <target>.
- Any OS: pathping <target> (Windows) or a continuous ping while WinMTR/mtr is running as a cross-check.
- Always wire in first — Wi-Fi noise pollutes traceroute results.
Reading the output
Common patterns and what they mean
| Symptom | Likely cause | How to test | Possible fix |
|---|---|---|---|
| First hop shows loss | Your router or ethernet link is dropping — a local problem | Swap cable / port; retest | Replace cable or router; escalate if ISP-supplied gateway is faulty |
| Loss on middle hops that clears on the final hop | Router rate-limiting ICMP — cosmetic, not real | Ignore if final-hop loss is zero | None needed |
| Sustained loss at a specific ISP hop that carries through to destination | Congestion or fault on that ISP link | Reproduce at multiple times of day | Report to ISP with the trace attached; peak-hour cases are the specific fit for a route optimiser |
| Sudden RTT jump between two hops that persists downstream | Sub-optimal routing decision at that transit boundary | Compare peak vs off-peak | Only a booster or ISP re-peering fixes this — you cannot |
FAQs
Common traceroute questions
- What is a traceroute and why do I need one for gaming?
- A traceroute lists every router your packets pass through between your device and the destination, showing round-trip time and loss at each hop. It tells you where a network problem lives — inside your house, on your ISP, at a transit provider, or on the game's edge.
- Why does traceroute show high ping on middle hops?
- Because ICMP replies from middle routers are deprioritised. A high middle-hop RTT that is not accompanied by loss and doesn't propagate to the final hop is almost always cosmetic. Only trust loss and RTT growth that persist to the destination.
- What is the best traceroute tool on Windows?
- WinMTR is the standard for gaming diagnostics — it combines traceroute and ping into a continuous rolling report. tracert.exe is fine for a one-shot check.
- How long should I run a traceroute?
- For an intermittent problem, five to fifteen minutes of continuous WinMTR / mtr output at the time the problem happens. A single-shot tracert is useful for topology but not for reliability data.
Learning path