When a website loads slowly or a connection fails, traceroute is your best friend for diagnosis. This powerful network diagnostic tool reveals the path your data takes across the internet, showing every hop between you and your destination.

What is Traceroute?

Traceroute (or tracert on Windows) is a network diagnostic command that maps the path packets take from your computer to a destination server. It shows:

  • Each router (hop) along the path
  • Response times at each hop
  • Where packet loss or delays occur
  • The geographic route your data takes

Think of it as a GPS for your internet traffic - it shows every stop along the way to your destination.

How Traceroute Works

Traceroute uses a clever technique involving TTL (Time To Live) values:

  1. First probe: Sends a packet with TTL=1. The first router decrements TTL to 0 and returns an ICMP "Time Exceeded" message
  2. Second probe: Sends a packet with TTL=2. It passes the first router, then the second router returns the message
  3. Continues: This process repeats until reaching the destination or max hops

Technical Note

Traceroute typically sends 3 probes per hop by default, which is why you see 3 timing values for each line in the output.

Reading Traceroute Results

A typical traceroute output looks like this:

1   1.2 ms    0.9 ms    1.1 ms   192.168.1.1
2   12.3 ms   11.8 ms   12.1 ms  10.0.0.1
3   25.4 ms   24.9 ms   25.2 ms  isp-router.example.com
4   45.6 ms   44.8 ms   45.1 ms  core-router.backbone.net
5   *         *         *        Request timed out
6   78.2 ms   77.5 ms   78.0 ms  destination.com

Understanding Each Column

  • Hop number: The sequence position in the route
  • Three times: Round-trip times for three separate probes
  • Address/hostname: The router's IP or DNS name

What the Symbols Mean

  • * (asterisk): No response received (timeout)
  • !H: Host unreachable
  • !N: Network unreachable
  • !P: Protocol unreachable

Diagnosing Common Issues

High Latency at a Specific Hop

If you see a sudden jump in response times:

  • Could indicate congestion at that router
  • May be a geographic distance (crossing oceans)
  • Possibly a slow or overloaded router

Timeouts (* * *)

Asterisks don't always mean a problem:

  • Many routers are configured not to respond to traceroute probes
  • Firewall rules may block ICMP responses
  • Only concerning if accompanied by packet loss to the destination

Important

A single hop showing high latency doesn't necessarily mean that's where the problem is. Compare the latency to the next hop - if it returns to normal, the router may simply deprioritize ICMP responses.

Loops and Inconsistent Paths

If you see the same IP appearing multiple times or paths that seem to go backward:

  • Could indicate a routing loop
  • May be load balancing across multiple paths
  • Asymmetric routing (different paths in each direction)

Using Our Traceroute Tool

Our Traceroute tool provides visual network path analysis:

  1. Enter the hostname or IP address you want to trace
  2. Click "Trace Route" to start the analysis
  3. View results with latency indicators and hop information
  4. Identify problem areas highlighted in the results

Advanced Usage

Comparing Routes Over Time

Run traceroutes at different times to identify:

  • Changes in routing paths
  • Time-of-day congestion patterns
  • ISP routing changes

Traceroute vs MTR

MTR (My Traceroute) combines ping and traceroute, providing continuous statistics. Use MTR when you need:

  • Packet loss percentages per hop
  • Average latency over time
  • Jitter measurements

Troubleshooting Tips

When to Use Traceroute

  • Website is slow to load
  • Connection drops intermittently
  • Need to identify which network segment has issues
  • Verifying the path taken by your traffic

Interpreting ISP Hostnames

Router names often contain useful information:

  • City codes: lax (Los Angeles), nyc (New York), lon (London)
  • Router types: core, edge, agg (aggregation)
  • Interface speeds: ge (Gigabit), te (10 Gigabit)

Conclusion

Traceroute is an essential tool for understanding network connectivity. Whether you're troubleshooting slow connections or planning network infrastructure, knowing how to interpret traceroute results helps you quickly identify and resolve issues.

Try our Traceroute tool to analyze your network paths and diagnose connectivity problems.