Traceroute (MTR)
See every router between our server and a destination, with packet loss and latency per hop (MTR report) – find where a connection slows down or breaks.
When a site is slow or unreachable, a traceroute shows the path the traffic takes – every router between our server and the destination – and where delay or loss begins. This tool runs MTR, which probes each hop several times and reports loss and average, best and worst latency, so intermittent problems show up as well as hard failures.
How to use it
- Enter the hostname or IP address that has the problem.
- Choose 5 probes per hop (or 10 for an intermittent fault) and press Trace. It takes 10–20 seconds.
- Read from the top: hops 1–3 are our hosting network, the middle is transit providers, the last hops are the destination’s network.
How to read loss and latency
- Loss on one middle hop only – normal. Routers rate-limit replies to probes while still forwarding traffic.
- Loss that starts at a hop and continues to the end – a real problem at or just after that hop.
- A jump in latency that stays – distance (for example an undersea cable), not a fault.
- “No reply” hops – routers that don’t answer probes at all. Harmless if later hops answer.
Reporting a problem to your ISP
Run MTR from your own network too (mtr -rwc 50 example.com on Linux, or WinMTR on Windows) and send both reports. ISPs act much faster on an MTR that shows where the loss starts.
Frequently asked questions
A middle hop shows 100 % loss – is it broken?
Usually not. Many routers don’t answer traceroute probes, or answer them slowly, while still forwarding traffic. Only loss that starts at a hop and continues to the final destination points to a real problem.
Why do latencies jump between countries?
Undersea cables and long distances add delay – for example Australia to the US west coast adds about 150 ms. A jump that stays for all later hops is distance, not a fault.
What is the difference between traceroute and MTR?
Traceroute sends a few probes once. MTR repeats them and reports loss and average, best and worst latency for each hop, which makes intermittent problems visible.
More tools
All tools →Ping Test
Ping any website or public IP from our server: reply times, packet loss, jitter and TTL for each packet – check whether a host is up and how healthy the path is.
Open tool Network troubleshootingOpen Port Checker
Check from the internet whether ports are open, closed or filtered on a server or router – port forwarding, firewalls, mail, RDP, SSH and VPN in one test.
Open tool Network troubleshootingWebsite Down? HTTP Status & Speed Checker
Is a website down for everyone or just you? See the HTTP status, every redirect, DNS/connect/TLS/first-byte timings and the security and caching headers.
Open tool