Traceroute
Trace the network path to any host and discover all the routers along the way.
About Traceroute
Traceroute is a network diagnostic tool that shows the path packets take from our server to a destination host. It reveals:
- Network Path - Every router (hop) between the source and destination
- Latency per Hop - The round-trip time to each router
- Network Issues - Where packets are being delayed or lost
Note: Some routers don't respond to traceroute probes and will show as * (timeout). This is normal and doesn't indicate a problem.
What is Traceroute?
Traceroute maps the complete network path that data packets take from our server to a destination host. It reveals every router (hop) along the way, showing the IP address and round-trip latency at each step. This makes it invaluable for identifying exactly where network problems occur -- whether it's a slow hop at your ISP, a congested peering point, or an unreachable destination.
Our traceroute tool sends packets with incrementally increasing TTL (Time to Live) values. Each router along the path decrements the TTL by one, and when it reaches zero, the router sends back a "time exceeded" message. By recording these responses, we build a complete map of the network path with timing data for each hop.
How to Read Traceroute Results
- Hop number - Each line represents one router in the path, numbered sequentially
- IP address - The address of the router at that hop
- Latency (ms) - The round-trip time to reach that specific hop
- * (asterisk) - The router didn't respond, which may indicate a firewall blocking ICMP packets (not necessarily a problem)
- Sudden latency jumps - A large increase between hops suggests congestion or a geographic distance change
Frequently Asked Questions
What does * (asterisk) mean in traceroute?
An asterisk means the router at that hop did not respond to the traceroute probe within the timeout period. This is often normal -- many routers are configured to drop or deprioritize ICMP packets for security reasons. If subsequent hops respond normally, it's not a concern.
How is traceroute different from ping?
Ping only tells you the total round-trip time to a destination and whether it's reachable. Traceroute shows you every hop along the path, so you can see exactly where delays or failures occur. Use ping for a quick connectivity check, and traceroute when you need to diagnose where a problem is happening.
Why does my traceroute stop or time out?
Traceroute may stop if a firewall blocks the probes, if there's a routing loop, or if the maximum hop count is reached. Some destinations intentionally block traceroute. If it stops at a specific hop, the issue is likely between that hop and the next one.