Traceroute Online to Follow Every Hop to a Host

When a website crawls or a game server lags, the fault usually hides somewhere between you and the destination: a congested router three networks away, a detour through another continent. Traceroute is the diagnostic that exposes that hidden path, listing every router a packet crosses, hop by hop, with the time each hop takes. This online version runs the trace from a web page, so you can investigate a route without opening a terminal.

How a Traceroute Maps the Path

The trick behind traceroute is the time-to-live (TTL) field every IP packet carries. Each router that forwards a packet decrements the TTL by one, and when the counter hits zero the router discards the packet and sends back an error message naming itself. Traceroute exploits this deliberately: it sends probes with TTL values of 1, 2, 3 and so on, so each probe dies one hop further along the path and each router along the way identifies itself in turn.

The output is a numbered list: hop count, the responding router's hostname or IP address, and usually three latency readings in milliseconds, one per probe. Reading down the list, you watch the packet leave the starting network, cross any intermediate providers, and arrive at the target host.

Features of This Online Traceroute Tool

• Traces the route to any domain name or IP address you enter.
• A Perform Traceroute button starts the trace; Clear wipes the output for a fresh run.
• Lists every responding hop with its latency measurements.
• Runs entirely from the browser page, with nothing to install.
• Complements basic reachability checks when a site is up but slow.

For a quicker yes-or-no on whether a host responds at all, the ping tool answers first, and the DNS lookup confirms the name resolves to the address you expect before you trace anything.

How to Run a Traceroute

1. Enter the domain or IP address you want to investigate.
2. Click Perform Traceroute and wait while the probes run; a full trace can take a little while.
3. Read the hops in order, noting where the latency jumps sharply.
4. Look for rows of asterisks, which mark hops that did not answer.
5. Compare the final hop with the destination you intended to reach.
6. Click Clear before running a trace to a different target.

Reading a Real Trace: Where the Delay Lives

Imagine a trace to a shop's website where hops 1 to 6 all answer in under 15 milliseconds, hop 7 suddenly reads 120 milliseconds, and everything after it stays above 120. The problem is not the website: the slowdown happened at the boundary hop 7 represents, typically a hand-off between two networks or a long physical link, perhaps an undersea cable. Every later hop inherits that delay because each probe must cross the same slow link. That pattern, one sharp step up that never comes back down, is the classic signature of congestion or distance at a single point in the route, and it is the first thing to quote when reporting a problem to a provider.

Reading Traces Without Fooling Yourself

• The trace starts from the tool's network, not your home. An online traceroute runs from the service's servers. It shows the path from that vantage point, which is perfect for checking a route generally, but it cannot reproduce the exact path your own connection takes.
• Asterisks do not automatically mean failure. Many routers are configured to ignore or rate-limit traceroute probes. If later hops still answer, traffic is flowing; the silent hop simply declined to introduce itself.
• Return paths can differ. Packets coming back may travel a different route, so the latencies shown blend the outward journey with whatever path the replies took.
• Latency at one hop is not a verdict. Routers prioritise forwarding real traffic over answering probes, so a busy-looking middle hop with healthy final-hop times is usually innocent. Judge by the destination's numbers.
• Check your own address separately. If you are comparing what the internet sees of your connection, What's My IP shows the public address you appear from.

Traceroute Questions, Explained

What is a hop in a traceroute?

A hop is one router forwarding the packet toward its destination. Each row in the output is one hop, numbered in the order the packet meets them.

Why do some hops show asterisks instead of times?

The router at that step did not reply to the probes, usually because it is configured not to, or a firewall filtered the responses. Traffic may still pass through it perfectly well, as proven when later hops respond.

How many hops is normal?

Anywhere from a handful within a city to around 30 for an intercontinental route. The count itself is not good or bad; total latency and where it accumulates are what matter.

Can a traceroute tell me why a website is down?

It can show where the path stops. If the trace dies at the destination's network, the problem is near the host; if it never leaves the starting network, the problem is at your end of the route. A complete trace with a dead website suggests the server itself, not the path.

Is the route fixed, or can it change?

Routes change constantly as networks rebalance traffic and links fail or recover. Two traces minutes apart can legitimately differ by a hop or two; treat one trace as a snapshot, not a map carved in stone.

Evidence Instead of Guesswork

Traceroute turns "the internet is slow" into a specific addressable fact: this hop, this many milliseconds, this network boundary. Run online, it gives you that evidence from a clean vantage point in seconds, ready to act on or to hand to a provider.