This tool runs on the server.
How it works
Trace Route reveals the path packets take to a destination: each intermediate router they pass through is called a hop. For each hop it shows the device's address and how long it took to respond, so you can see where the delay builds up.
The trace runs from our servers and results appear hop by hop in real time. It is the ideal tool when a site responds slowly or intermittently and you want to know at which segment of the route the problem occurs.
Use cases
- Locate at which point on the route the latency or the break toward a server occurs.
- Distinguish whether a problem is in your provider, an intermediate transit, or the destination.
- Check whether traffic takes an unexpected route or a geographic detour.
- Document the route and latencies for a report to support or the provider.
Frequently asked questions
What is a hop?
Each hop is a router the packet passes through on its way to the destination. The list shows the sequence of these devices, from the one closest to your origin to the one closest to the destination.
Why do some hops appear with asterisks or no response?
Many routers are configured not to respond to trace packets, or they drop that traffic by priority. A hop with no response does not imply a failure: the packet may keep advancing anyway.
A hop shows high latency; is the problem there?
Not always. An isolated spike at an intermediate hop is usually the router prioritizing forwarding over answering you. What matters is whether the high latency persists from that hop onward, including the final destination.
Can the destination be reached even if the trace does not reach it?
Yes. If the destination or its firewall blocks trace traffic, the trace stops before arriving even though the service works. Combine it with a ping to confirm real connectivity.