CONNECTIVITY
Traceroute
Trace the path packets take across the internet and identify where delay or routing changes begin.
39DExternal testRuns from the toolbox server
RUN TEST
Traceroute
HOW IT WORKS
About the Traceroute
Traceroute sends probes with gradually increasing TTL values. Routers that return time-exceeded messages appear as hops. Some networks suppress these replies, so missing hops do not automatically indicate a fault.
How to use this result
- Run the test from this server.Use a public hostname, address, prefix or ASN in the format requested above.
- Compare with another observation point.Run a local command or use a second provider to identify location-specific behaviour.
- Correlate related evidence.Use the related tools below to compare DNS, routes, ports, TLS and application responses.
- Keep the time and context.Routing, DNS caches and reputation data change, so record when the result was collected.
Common interpretation issues
- Asterisks usually mean a router did not answer the probe.
- Different runs may show different paths because of load balancing or route changes.
- The final hop may be hidden even when the destination service is working.
NEED HELP INTERPRETING THE RESULT?
39D supports business networks, cyber security and managed IT.
For ongoing support or a larger infrastructure project, speak to the 39D team.
Frequently asked questions
Can traceroute find the exact fault?
It can show where symptoms begin, but it cannot prove which operator or device caused them.
Why are hostnames not shown?
Numeric output is used to make the test faster and avoid extra reverse-DNS queries.