Path visibility
Shows responding hops between the Netest server and the destination.
IP Protocol Tools
Traceroute Tool
Trace a limited public network path and inspect responding hops from the Netest server.
Hop viewReview responding routers along the server-side path.
Secured limitsHop count, wait time, output, and request rate are capped.
Filtered hops expectedAsterisks are normal when routers hide or rate-limit probes.
Working tool
Traceroute Tool
Trace the responding network hops between the Netest server and one public destination.
2
Waiting
Review the routeHop-by-hop server path
Your route results will appear here
The returned output shows responding hops and timeouts between the Netest server and your destination.
1 First responding hop… Intermediate routers✓ Destination or final response
Traceroute Tool: Short intro
Traceroute shows the routers or hops that respond along the path toward a public destination. It helps reveal where latency or packet loss may begin, but hidden hops and filtered probes are normal on modern networks.
Secured limits
Hop count, wait time, output size, and request rate are capped.
Best effort
Some routers intentionally hide, de-prioritize, or rate-limit traceroute replies.
Traceroute Tool: Example input/output
| Input | Typical output | Meaning |
|---|---|---|
| 8.8.8.8 | Hop list with latency values or asterisks | Each line is a responding hop or timeout on the server path. |
| example.com | Resolved IP plus limited trace output | The hostname is resolved before the trace begins. |
Traceroute Tool: Common errors
Asterisks in output
Asterisks usually mean a hop did not reply within the timeout or blocks probe responses.
Command unavailable
The hosting server may not have traceroute installed. The page will show that clearly.
Private destination
Internal and reserved destinations are rejected to avoid probing private networks.
Traceroute Tool: Use cases
- See whether a public destination path leaves the expected provider.
- Find the first hop range where latency or loss appears.
- Compare route behavior before and after DNS, CDN, or ISP changes.
- Support incident notes with a server-side path sample.
Traceroute Tool: FAQ
Why are some hops hidden?
Routers may drop, filter, or rate-limit traceroute responses while still forwarding user traffic.
Is this my local route?
No. The route starts from the Netest server, so your local ISP route can be different.
Can I trace internal hosts?
No. The tool only accepts public destinations and runs with strict hop and timeout limits.