// tool/traceroute-map
Traceroute Map
Visualize each hop between you and a target so routing issues stop looking like folklore.
What this is
Traceroute walks the path between you and a destination, exposing every router (hop) in between with its latency. Use it when a service feels slow but DNS and the endpoint look healthy — the answer is usually somewhere in the middle.
What it covers
- ›Hop-by-hop path view
- ›Latency and loss notes
- ›Private/unknown hop handling
- ›Shareable troubleshooting notes
Operator notes
- $Start with a hostname or public IP you are authorized to test.
- $Compare where latency begins, not just where it ends.
- $Treat asterisks as missing responses, not automatic outages.
status: Live Globalping traceroute is wired with hop extraction and geo context.
Traceroute map
checking limit…
ready
Loading map…
hopnodertt
Run a trace to visualize each hop.
Frequently asked
- What does '* * *' mean in a traceroute?
- The router at that hop didn't reply to the probe — usually because ICMP/UDP responses are rate-limited or filtered, not because the hop is down. As long as later hops respond, traffic is still flowing.
- Why does latency jump at one hop and stay high?
- That's the hop where you're crossing a slow link (often an intercontinental segment or a congested peering point). All downstream hops inherit that latency baseline.
- Is traceroute reliable for finding outages?
- It's a hint, not proof. ICMP can be deprioritized by routers under load, so a missing reply doesn't always mean the path is broken. Combine with end-to-end probes.