Free Online Traceroute — Trace Network Path to Any Host
Trace the network route from our server to any destination. See every hop (router), IP address, hostname, and latency along the path. Our free online traceroute tool helps you diagnose routing issues, identify bottlenecks, and understand how your traffic reaches its destination.
Online traceroute, trace route to IP, network path trace, tracert online, hop by hop trace, routing diagnostic tool, trace network route, identify network bottleneck.
Traceroute & Network Path Analyzer
Enter a hostname or IP address to trace the network path and see each hop along the route.
See every router between you and the target
Identify where delays occur in the path
See IP addresses and reverse DNS for each hop
Pinpoint where network problems occur
What Is Traceroute and How Does It Work?
Traceroute (called "tracert" on Windows) is a network diagnostic tool that reveals the path packets take from one point on the internet to another. It works by sending packets with incrementally increasing TTL (Time To Live) values. Each router along the path decrements the TTL by one; when it reaches zero, the router sends back an ICMP "Time Exceeded" message. By starting with TTL=1 and increasing it, traceroute discovers each hop in sequence — building a complete map of the network path.
For each hop, traceroute records the router's IP address, hostname (via reverse DNS when available), and the round-trip time. This information helps you understand the routing topology and identify where delays or failures occur in the network path.
Understanding Traceroute Results
Each line in a traceroute result represents one hop (router). You'll see the hop number, the router's IP address and hostname, and the round-trip time in milliseconds. Asterisks (*) mean the router didn't respond — this is common because many routers are configured to not respond to traceroute probes for security or performance reasons. A non-responding hop doesn't necessarily indicate a problem.
Look for sudden latency increases — if latency jumps from 30ms to 200ms at a specific hop, that's where a bottleneck exists. Consistent high latency from a certain hop onward suggests congestion at that point in the network. Timeouts at the last hop may mean the destination blocks traceroute but is still accessible for normal traffic.
When to Use Traceroute
Use traceroute when a connection is slow or unreliable — it shows whether the problem is near you (first few hops), in the middle of the internet backbone, or near the destination. Network administrators use it to diagnose routing issues, peering problems, or congested links. It's especially useful when combined with ping: if ping shows high latency, traceroute reveals exactly where the delay occurs.
Online Traceroute vs Local Traceroute
Our online traceroute runs from our server, showing the path from our network to the target. For troubleshooting your own connection issues, you may also want to run traceroute locally from your computer (use "traceroute" on Mac/Linux or "tracert" on Windows in the terminal). Comparing results from both can help isolate whether a problem is on your end, your ISP's network, or further along the path.
For simple latency checks, use our ping test. For IP geolocation and network details, try IP address lookup. To check if specific ports are accessible, use our port checker. See also What is my IP, DNS lookup, and VPN detection.
Privacy, Accuracy & Security
Privacy: We don’t store the hosts you trace. Accuracy: Path is from our server; your route may differ. Security: HTTPS only. Free, no signup.
Frequently Asked Questions About Traceroute
What do asterisks (*) mean in traceroute?
Asterisks indicate that the router at that hop didn't respond to the traceroute probe within the timeout period. This is very common — many routers are configured to ignore traceroute packets for security or performance reasons. It doesn't necessarily mean there's a problem.
How many hops is normal for a traceroute?
Most traceroutes complete in 10-20 hops. Routes to servers on the same continent typically take 10-15 hops, while intercontinental routes may take 15-25 hops. If a traceroute reaches 30 hops without completing, the destination may be unreachable or blocking traceroute.
Why is latency high at one specific hop?
A single hop with high latency can indicate: network congestion at that router, the router deprioritizing ICMP responses while handling high traffic, or a physical distance jump (e.g., an undersea cable crossing). If subsequent hops return to normal latency, the high-latency hop is likely just deprioritizing traceroute responses and isn't a real bottleneck.
What's the difference between traceroute and ping?
Ping tests the overall latency and packet loss to a single destination. Traceroute shows every router along the path to the destination with per-hop latency. Use ping for a quick connectivity check; use traceroute when you need to identify where in the network a problem occurs.