Skip to content
EnterraHost
Products
Tools
Hosting Email Support Client Area Find a domain
Easy utilities

Traceroute

A deep-path analysis tool that maps every network hop between the source and the target. It helps to pinpoint the likely location of a bottleneck or a failure within the global internet infrastructure.

Three probes per hop, from the region you choose. Public domains and addresses only.

Email me this result

The same result, sent to your inbox.

We use the address to send this result. It is not stored after the message goes out, and nothing is added to a list unless you tick the box.

Need somewhere to put the site? Hosting from $4.95 a month, with free DNS on every domain you own.

Reading a trace

Three things to look for.

The full walkthrough is in how to read a traceroute output, including what the location column means and what a trace cannot tell you.

Where the jump happens

Read down the times. A hop that is a few milliseconds slower than the one before it is normal. A hop that adds 150 ms in one step is the link worth asking about.

Whether it is steady

The three probes per hop show consistency. Tight numbers mean a stable link. Numbers that swing mean congestion, and congestion is what makes a connection feel unreliable.

Whose network it is

Each hop is labeled with the network that announces it. That turns a complaint into a specific question aimed at the right operator rather than at nobody in particular.

Common confusion

Things that look like faults and are not.

Silent hops

Routers routinely refuse to answer probes aimed at themselves while forwarding your traffic without complaint. A blank hop in the middle of an otherwise working trace is not a fault.

A trace that ends at a CDN

If the target is behind a CDN, the trace finishes at the edge nearest you and never reaches the origin. That is the design working correctly, not the trace failing.

Next

Once you know where it stops.

If the path looks clean and the delay is still there, the network is not the problem. The next thing to check is the server itself and the certificate it presents.

Questions

Questions about reading a trace.

Can I get the result by email?
Yes. Run the check, then press the paper plane beside the result and give it an address. The message carries the same figures the page shows, any table the result produced, and on the map tools the diagram itself as an attached vector file. Nothing is stored unless you tick the box asking to hear about new tools and trials, and if you do, the message carries a link that removes you again.
What is the difference between ping and traceroute?
Ping tells you how long the whole round trip took. Traceroute tells you where that time went. It sends packets with a rising time to live, so each one expires at a different hop and that hop reports itself, building a map of the path.
Why do some hops show stars or no reply?
Because many routers are configured not to answer probes addressed to themselves while still forwarding traffic perfectly well. A silent hop in the middle of a working trace is normal and is not a fault. Silence at every hop after a certain point tells you more.
Why does the same hop show three different times?
Traceroute sends three probes per hop so you can see consistency. If the three numbers are close the hop is stable. If they swing widely, that link is congested, and that variation is what makes calls break up even when the average looks acceptable.
Why does the route change between runs?
Because the internet is not a single path. Routers balance traffic across links, so a run five minutes later can legitimately take a different route. Small differences between runs are normal, and a route that changes every single time usually means load balancing rather than a fault.
A hop has a private address in the middle. Is that a problem?
No. Carriers use private addressing inside their own networks, so seeing 10.x or 192.168.x addresses mid path is expected. It only looks odd because you cannot see the public addressing around it.
Where does a traceroute stop being useful?
At a CDN. A large site is served from an edge near you, so the trace ends at that edge and tells you nothing about the origin server. That is normal and correct, and it is why the last few hops of a trace to a CDN can differ completely between two visitors.