CONNECTIVITY
MTR Network Test
Run an MTR report to compare packet loss and latency at each visible hop.
39DExternal testRuns from the toolbox server
RUN TEST
MTR Network Test
HOW IT WORKS
About the MTR Network Test
MTR sends repeated probes across the route and calculates loss, average delay, best, worst and variation for each responding hop. It is often more useful than a single traceroute when diagnosing intermittent connectivity.
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
- Loss on one intermediate hop may be rate-limiting if later hops remain healthy.
- Persistent loss that continues through later hops is more significant.
- MTR must be installed on the hosting server for this test to run.
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
How many probes are sent?
The public tool uses a short fixed report to reduce load and prevent abuse.
Does hop loss always affect traffic?
No. Routers often deprioritise diagnostic replies while forwarding normal traffic correctly.