How to Read a Traceroute in Under 60 Seconds

Traceroute is one of the simplest and most powerful tools for diagnosing network routing issues. Whether you're running a game server, managing a VPS, or just trying to figure out why your connection to a site is lagging—learning to read a traceroute quickly can save hours of guesswork.

This guide walks you through the basics and shows how to spot problems in seconds.

What Is Traceroute?

Traceroute is a command-line utility that shows the path network traffic takes from your computer to a target server or domain. It lists each "hop" (router) your traffic passes through, along with how long each hop takes to respond.

This is extremely useful when diagnosing issues like:

High ping in games
Website downtime
Routing problems between ISPs
Geographic detours in your traffic flow

Traceroute works by sending packets with gradually increasing time-to-live (TTL) values. Each hop along the way responds, revealing its IP address and response time.

Example Output

traceroute to example.com (93.184.216.34), 30 hops max
 1  192.168.1.1     1.1 ms
 2  10.0.0.1        5.4 ms
 3  isp-gw.local    12.2 ms
 4  core.router     15.8 ms
 5  ???             * * *
 6  destination     18.4 ms

How to Read It Quickly

1. Each Line = One Hop

Every line represents a router between you and the target. The first line is typically your home router or local gateway, and the last is the destination server.

2. Look at the Delays (ms)

Each hop shows how long it took (in milliseconds) for a response. A sudden jump from one hop to the next might indicate congestion or a bottleneck. For example:

10 ms → 12 ms → 14 ms → 300 ms = something is likely wrong at or after that hop.

3. Asterisks = Timeouts

If a hop shows * * *, that router didn’t reply to the traceroute probe. This doesn’t always mean a problem—many ISPs or firewalls block these probes. However, if the trace fails entirely after that hop, it could mean a dead route, firewall, or packet drop.

4. Hostname Clues

Traceroute often includes the hostnames of intermediate routers. These can reveal:

ISP names (e.g. ae-2.r23.lax01.us.bb.gin.ntt.net)
Data center locations (e.g. .lhr1, .fra3, .nyc2)
Transit providers (e.g. level3.net, gtt.net, cogentco.com)

Use this to understand which providers your traffic flows through.

Common Patterns and What They Mean

Symptom	Likely Cause
High latency jump mid-route	Congestion or long-distance hop
Asterisks mid-route but continues	Hop is blocking probes, not broken
Asterisks and stops	Drop/firewall or misconfigured route
Looping IPs repeatedly	Routing loop (bad route setup)
High ping on first/second hop	Local device or ISP issue

If your traceroute shows 5+ hops with high latency (>200ms), you’re likely facing a routing or congestion issue with an upstream ISP or backbone provider.

Tools to Run Traceroute

Windows: tracert example.com (built-in)
Linux/macOS: traceroute example.com
Graphical/Visual:
- WinMTR: Live ICMP + latency + loss tool
- PingPlotter: Clean graphs and visual route analysis
- MTR (Linux): Continuous traceroute tool

When to Run a Traceroute

Use traceroute when:

Players are complaining about lag but your server looks fine
A site is up for others but not for you
You want to verify traffic is using the correct route
You're comparing providers or data center routing

Summary

Traceroute is one of the most underrated networking tools. With just a few lines of output, you can see the full path your traffic takes and pinpoint latency spikes or connectivity issues.

Look for sudden jumps in ping, unexplained timeouts, or reroutes through distant locations. Combine this with MTR or PingPlotter for deeper insight.