Traceroute Tool - Trace Network Path
Trace the route packets take to reach any destination. See every hop, identify bottlenecks, and diagnose routing problems with our visual traceroute tool.
Rate limit: 10/10 requests remaining (resets in 51s)
Understanding This Tool
What It Does
Trace the network path packets take from your computer to a destination host. Traceroute shows each hop (router) along the way, helping identify where network problems occur.
Understanding the Results
- Hop Number: Sequential number for each router along the path
- Router Hostname/IP: The IP address of each network device
- Response Time: Time to reach each hop (shown three times)
- Timeout: Hops that don't respond to the traceroute probe
- Total Hops: Number of routers between source and destination
Common Use Cases
- Path Analysis: Understand the network route packets take
- Latency Identification: Pinpoint which router is causing slow connections
- Connectivity Issues: Identify where connections fail or time out
- Network Bottlenecks: Find routing inefficiencies causing delays
- ISP Diagnosis: Verify your ISP's routing configuration
Pro Tips & Best Practices
- Unreachable Hops: Timeouts (asterisks) may indicate routers that don't respond to traceroute
- Path Variation: Routes may vary based on network conditions and load balancing
- TTL Mechanism: Traceroute works by sending packets with incrementing TTL values
Frequently Asked Questions
Traceroute maps the complete path that network packets take from your computer to the destination server, showing every router (hop) along the way and the latency at each point.
Each hop is a router or gateway that forwards your packets toward the destination. Typically you'll see your ISP's routers first, then backbone/transit providers, then the destination network.
Asterisks mean that router didn't respond to traceroute probes, often due to firewall rules or ICMP rate limiting. This is common and doesn't indicate a problem if subsequent hops respond.
High latency at one hop can indicate network congestion, routing inefficiency, or geographic distance. If later hops show normal latency, the high hop isn't necessarily problematic.
Typical routes have 10-20 hops. Very short routes (under 8 hops) indicate proximity or direct peering. Long routes (over 25 hops) may indicate inefficient routing or complex network paths.
Yes, traceroute identifies where packets are being dropped or delayed. If traceroute stops at a specific hop, that router or the next link is likely where the connection problem exists.
Frequently Asked Questions
What is traceroute used for?
Traceroute maps the complete path that network packets take from your computer to the destination server, showing every router (hop) along the way and the latency at each point.
What does each hop represent?
Each hop is a router or gateway that forwards your packets toward the destination. Typically you'll see your ISP's routers first, then backbone/transit providers, then the destination network.
Why do some hops show asterisks (***)?
Asterisks mean that router didn't respond to traceroute probes, often due to firewall rules or ICMP rate limiting. This is common and doesn't indicate a problem if subsequent hops respond.
What causes high latency at a specific hop?
High latency at one hop can indicate network congestion, routing inefficiency, or geographic distance. If later hops show normal latency, the high hop isn't necessarily problematic.
How many hops is normal?
Typical routes have 10-20 hops. Very short routes (under 8 hops) indicate proximity or direct peering. Long routes (over 25 hops) may indicate inefficient routing or complex network paths.
Can traceroute help diagnose connectivity problems?
Yes, traceroute identifies where packets are being dropped or delayed. If traceroute stops at a specific hop, that router or the next link is likely where the connection problem exists.
Last reviewed:
How this tool works: This tool runs in your browser and on our server in real time. Depending on the tool, results are computed directly from the input you provide or retrieved from live, authoritative data sources at the moment you run a lookup. We do not sell your data, and your lookups are kept private — any history shown here is stored only on your device.