GoIPScan

Fast, private, accurate IP lookup

GoIPScan Tools Visual Traceroute

πŸ—ΊοΈ Visual Traceroute

Run traceroute, tracert, or mtr on your device and paste the output below to see an interactive hop-by-hop latency chart. Everything runs in your browser β€” nothing is sent to our servers.

πŸ“‹ Paste Output
How to Run Traceroute

Run traceroute on your device, copy the full output, then paste it in the Visualise tab

macOS / Linux
Windows
MTR (advanced)
traceroute google.com

Open Terminal (Applications β†’ Utilities β†’ Terminal). Replace google.com with any hostname or IP. Select all output and copy.

tracert google.com

Open Command Prompt (Win+R β†’ cmd β†’ Enter). Windows uses tracert, not traceroute. Right-click the title bar β†’ Select All β†’ Enter to copy.

mtr --report google.com

MTR combines ping + traceroute and shows packet loss per hop. Install: brew install mtr (macOS) or sudo apt install mtr (Linux). Use --report for copyable text output.

πŸ“ˆ Latency per Hop

πŸ›€οΈ Hop Details

#IP / HostnameLoss %AvgBestWorstLatency

🌐 What is a traceroute?

Traceroute maps the path packets take to a destination, showing every router (hop) they pass through and how long each leg takes.

⭐ * * * means timeout

Asterisks mean that router didn't respond. Very common and harmless β€” many routers silently drop traceroute probes for security reasons.

πŸ“ Runs from your device

Unlike online traceroute tools, this visualiser uses output from your own machine β€” so you see the real path from your network.

⏱️ High latency spikes

A spike at one hop doesn't always mean a bottleneck β€” routers often deprioritise traceroute probes. Look at the overall trend instead.

How to Read a Traceroute

Each line represents one hop β€” one router your packets passed through on the way to the destination. The numbers are round-trip times (ms) for probes sent to that hop.

What the latency tells you

Low latency on early hops is normal β€” these are nearby routers. A sudden large jump (e.g. 20ms to 150ms) usually marks a transatlantic or transpacific link. If latency stays high from a certain hop onwards, that's where the bottleneck is.

Packet loss

Loss% shows what percentage of probes didn't get a response at that hop. Loss early in the route that recovers later is usually just a router deprioritising ICMP β€” not a real problem. Consistent loss from a hop onwards indicates a genuine issue.

traceroute vs tracert vs mtr

traceroute is Unix/Linux/macOS. tracert is Windows. mtr sends multiple probes and shows packet loss percentages per hop β€” more useful for diagnosing intermittent issues.

More network tools

Port Checker Network Scan β†’