This guide explains the bounded route trace from the hublist server and why silent hops are not automatic service failures.
Usage
- Open Traceroute and enter a public hostname, IP address, or hub URL in Host Or Address.
- Select Run Traceroute.
- Review hop number, hostname, address, latency samples, and raw hop data alongside Ping Tool or TCP Connect results.
Concrete Example
A trace to hub.example.net may show 15 ms inside the local region, then 90 ms after an international transit hop. That change can explain higher ping time. Several silent intermediate hops do not prove failure if the later hops or TCP service still answer.
Interpretation
Each visible row is a router or network boundary that returned a TTL-expired response. Compare repeated latency samples rather than one outlier. A hostname is reverse-DNS context. The last displayed hop may be the target, an upstream firewall, or only the last device willing to reply.
Troubleshooting
- Only Asterisks: The path may be filtered for traceroute replies; try Ping Tool and TCP Connect.
- Latency Jump: Compare later hops to see whether the increase persists.
- Stops At Provider Edge: Give the trace and time of test to the hosting or transit provider.
- Trace Fails, Hub Works: Treat Protocol Test as stronger evidence of hub reachability.
Icon Reference
| Icon | Label | What It Does |
|---|---|---|
| Run Traceroute | Run Traceroute starts the bounded public route trace. | |
| Complete | Complete marks a finished trace with the returned hop data. | |
| Review Output | Review Output marks a partial or silent route that needs comparison. | |
| Open Help | Open Help opens this guide from the Traceroute panel. |