Online Traceroute Tool
A traceroute shows the path network traffic takes from one computer to another, hop by hop, with the time each router took to answer. This free online tool runs a traceroute from our server to a domain or public IP address, up to 20 hops and 15 seconds, and lists each hop with its address and round-trip times.
Traceroute Tool
Domain and Server
About this tool
When a website is slow or unreachable, the cause is sometimes the site and sometimes the road to it. A traceroute lists the routers between two machines. It sends packets with a growing time-to-live, and each router that drops one reports back, which reveals the path and how long each stage takes. A sudden jump in time or a row of timeouts near the end points to where trouble may start.
This tool runs the traceroute from our server, not from your computer, so it shows the path from our network to the target. Enter a domain name or a public IP address. The tool resolves the name, traces to the first IPv4 address, stops after 20 hops or 15 seconds, and prints one row per hop with the router address and up to three round-trip times. Hops inside our own private network are hidden.
Read the result with care. Many routers deliver traffic but refuse to answer traceroute probes, so a row of asterisks in the middle is normal if later hops respond. A long time on one hop that disappears on the next is usually a slow reply from that router, not a slow path. A trace that ends in timeouts may only mean the final server ignores probes. If the program is not available on the server, the tool says so.
Frequently asked questions
What do the asterisks in a traceroute mean?
An asterisk means no reply came back for that probe within the wait time. Routers and firewalls often ignore or rate-limit probe packets while still passing normal traffic. If later hops respond, the asterisks are harmless. If every hop after a point is silent, traffic may be blocked from there.
Why is the traceroute from my own computer different?
The path depends on where the trace starts. This tool traces from our server, so the first hops belong to our network. For the route your visitors take, run tracert on Windows or traceroute on macOS and Linux from your own device. Compare both to see where they diverge.
How do I find the slow hop?
Look for the first hop where times jump and stay high on every later hop. That is where delay is added. A high time on one hop only, with normal times afterwards, is usually the router answering probes slowly and is not a real problem on the path.
Why is the maximum 20 hops?
Most internet paths need fewer than 20 hops, and the cap keeps each trace short so the free tool is fair to everyone. Hard limits of 20 hops and 15 seconds also protect the target from probe traffic. If a trace has not finished by then, the partial result is shown.