Trace hop-by-hop paths with protocol and TTL controls.
Review each hop response time and ASN in a single table.
This page maps the visible network path from the probing system to the target. The UI remains intact, but the added explanation makes clear that traceroute is an observation of one path from one source at one point in time.
Enter a host or IP address, then choose the view options that fit your troubleshooting goal. The result is most useful when you already know the destination is relevant and you want to understand path behavior rather than just endpoint status.
The tool sends probes with incrementing hop limits and records which intermediate devices respond. Because routers can filter or rate limit these probes, the path may contain gaps even when end to end connectivity works.
Run traceroute to a known public host and review the hop list for large jumps in latency, path changes, or missing replies. Asterisks or gaps do not automatically prove an outage. They can simply indicate filtered or rate limited intermediate devices.
Use traceroute when latency changes suddenly, a region becomes unreachable, or you need evidence about which part of a path may be changing.
Traceroute, ping, and open port tests can all be affected by firewalls, routing policy, NAT, and rate limits. The output is an informational view of the path from one probe source, not a universal map of every route.
It shows the hop by hop path that packets appear to take from the probing system toward the target, along with timing for each visible step.
Routers can filter, rate limit, or deprioritize traceroute style probes, so a missing reply does not always indicate a broken path.
Yes. Routing policy, load balancing, congestion, and upstream changes can all alter the observed path or hop timings.
No. It helps explain path behavior, but application issues can exist even when traceroute completes normally.
It is useful for diagnosing path changes, latency spikes, regional reachability issues, and transit troubleshooting.
The output is informational and depends on firewalls, NAT, routing policy, and rate limits between the probe source and the destination.
Confirm basic reachability and latency before mapping the full path.
Check service exposure after you understand the path.
Add routing visibility context to observed path changes.