Local route analysis utility
Paste output from Linux traceroute, macOS traceroute or Windows tracert and turn it into a readable route report. The parser extracts hops, RTT samples, hostnames, IPs, timeouts, latency jumps and local-network clues without sending your pasted trace to a remote service.
Traceroute measures responses to TTL-limited probes. One silent router in the middle of a route can still forward real traffic normally.
What a traceroute visualizer is for
Traceroute is one of the quickest ways to inspect the visible path between your device and a remote destination. Instead of asking only whether a host replies, it shows which routers answer along the way and how long each probe takes to receive a response. Raw route output is useful, but it can also be noisy: hostnames wrap, some hops hide behind asterisks, latency appears as several samples per line, and Windows and Unix formats do not look exactly the same. This visualizer turns that output into a report you can scan.
The result is most useful when you are debugging a real symptom. It can help separate a local gateway problem from an ISP handoff, show that latency increases after a long-distance jump, reveal repeated timeouts near the destination, or document a route before and after a network change. It is not a verdict on its own. It is a structured clue that becomes much stronger when you compare it with ping, DNS and service checks.
How to read hops, RTT and timeouts
- A hop is a router or network point that answered a TTL-limited probe.
- RTT samples are round-trip times for individual probes, usually shown in milliseconds.
- The first hop is often a local router, firewall or VPN gateway.
- Private addresses such as 10.x.x.x and 192.168.x.x usually point to local or provider-internal networks.
- Asterisks mean no response was received for that probe, not automatically packet loss for user traffic.
- The final responding hop matters more than a single silent router in the middle.
When a traceroute looks suspicious
Look for patterns rather than one dramatic line. A sudden latency jump that stays high on every later hop can be meaningful. A timeout followed by healthy later hops is often just ICMP filtering or rate limiting. Repeated timeouts at the end may indicate that the destination or its firewall does not answer traceroute probes. If a route fails immediately at hop one or two, local Wi-Fi, VPN, router or ISP access problems deserve attention first.
Traceroute commands on common systems
On Windows, use tracert example.com. On macOS and Linux, use traceroute example.com; some Linux systems need the package installed first. A TCP-based trace can be helpful when ICMP or UDP probes are filtered, but that depends on your tooling and permissions. For a website incident, save the command, the timestamp, the source network and the destination so another administrator can reproduce the context.
Practical troubleshooting workflow
Start with DNS if the hostname resolves to the wrong destination. Run an HTTP ping or status check if the route reaches the service but the web page still fails. Use a port checker if you need to know whether a TCP service is reachable from outside. Repeat traceroute from another network before blaming a hosting provider, especially when the issue only appears from one ISP or one VPN path.
Common questions
Does a timeout mean packet loss?
Not always. Many routers forward traffic but ignore or rate-limit traceroute replies. Consecutive failures at the end of the trace are more concerning than one hidden middle hop.
Why does one hop show a high time but later hops look normal?
The router may answer probes slowly while forwarding packets normally. If later hops remain healthy, do not treat that one response time as proof of congestion.
Can this tool run a live traceroute from my browser?
No. Browsers cannot safely run a real traceroute from your device. This tool analyzes command output you paste, which also keeps the route text local to the page.
What does a traceroute actually show?
The sequence of routers (hops) a packet passes through to reach a destination, with the latency at each hop. It helps locate where delay or loss is introduced along the path.
Why do some hops show stars or timeouts?
Some routers are configured not to reply to traceroute probes, or rate-limit them. A starred hop in the middle is usually harmless as long as later hops respond.
Why does latency jump at one hop then settle?
A single high hop that does not raise the following hops is just that router deprioritising probe replies. A jump that persists to the end is a real latency increase.
