Traceroute

Trace the network path and measure hop-by-hop latency to any destination

Network Traceroute
Enter a hostname or IP address to trace the network path. This tool helps diagnose network routing issues and identify bottlenecks that ping alone cannot detect.

About Traceroute

Traceroute is a network diagnostic tool that displays the path packets take from a source host to a destination host. It works by sending packets with incrementally increasing TTL (Time To Live) values. Each router decrements the TTL by 1 when forwarding packets, and when TTL reaches 0, the router returns a "time exceeded" message.

Primary Uses:

  • Diagnose network connectivity issues
  • Identify bottlenecks in network paths
  • Analyze sources of network latency
  • Verify network routing configuration
  • Monitor network performance changes

Difference from Ping:

  • Ping only tests end-to-end connectivity
  • Traceroute shows the complete network path
  • Traceroute can pinpoint where problems occur
  • Traceroute provides latency info for each hop

Command Format & Usage:

Windows: tracert [options] destination
Linux/Mac: traceroute [options] destination
Common Options:
  • -h max_hops - Maximum number of hops
  • -w timeout - Wait timeout per reply
  • -q queries - Number of queries per hop
Examples:
  • tracert google.com
  • traceroute -h 15 8.8.8.8
  • tracert -w 3000 cloudflare.com

How to Read Results:

Hop Number: Sequential router number in the path
Response Time: Round-trip time to reach that hop
* Symbol: Indicates no response (possibly blocked by firewall)

Usage Considerations

Limitations:

  • Some routers may not respond to traceroute requests
  • Firewalls may block ICMP or UDP packets
  • Load balancing can cause inconsistent paths
  • Network congestion affects measurement accuracy

Best Practices:

  • Run multiple tests for more accurate results
  • Test at different times of day
  • Combine with ping tests for comprehensive analysis
  • Pay attention to hops with unusually high latency