Traceroute

Trace the network path from our server to any IP address or domain. See each hop, measure latency, and identify routing issues or network bottlenecks.

How Traceroute Works

Traceroute is a network diagnostic tool that shows the path packets take from a source to a destination. It works by sending packets with incrementally increasing Time-To-Live (TTL) values.

Understanding the Results

• Hop number: The sequential step in the route (1 = first router, 2 = second, etc.).
• IP Address: The IP of the router at that hop.
• Hostname: The reverse DNS name of the router (if available).
• Latency: The round-trip time (RTT) in milliseconds. Lower is better.
• * * *: Indicates the router at that hop did not respond (timeout).

How does this tool work?

This tool performs a traceroute from our server to the target IP or domain you specify. It sends packets with incrementally increasing TTL (Time-To-Live) values, recording each router that responds along the path. The result shows each hop's IP address, hostname, and latency.

Note that this traceroute is performed from our server's location, not from your local machine. The path and latency you see will differ from a local traceroute due to different network paths and distances.

Why should you use traceroute?

• Network diagnostics: Identify where network connectivity issues occur between two points.
• Performance analysis: Find which hop in the route is causing high latency.
• Routing verification: See if traffic is taking the expected path through the network.
• Outage investigation: Determine if a connectivity problem is local, regional, or at the destination.

How to interpret the results

1. Low, consistent latency: Healthy network path — packets are traveling efficiently.
2. Sudden latency spike: Possible congestion, overloaded router, or long-distance hop.
3. Timeouts (* * *): The router at that hop is not responding to traceroute probes. This is common and doesn't always indicate a problem.
4. Final hop unreachable: The destination may be down, blocking ICMP, or behind a firewall.

Common Issues Detected

• High latency spikes: A sudden increase in latency at a specific hop may indicate congestion or a routing issue.
• Timeouts (* * *): Routers may be configured to not respond to traceroute packets. This is normal and doesn't always indicate a problem.
• Routing loops: If the same IP appears at multiple hops, there may be a routing loop.
• Asymmetric routing: The return path may differ from the forward path, which is normal but can complicate troubleshooting.

Limitations

This traceroute is performed from our server, not from your local machine. The path and latency will differ from what you'd see locally. For a local traceroute, use your operating system's built-in tools (tracert on Windows, traceroute on macOS/Linux).