Online MTR test
Runs ping and traceroute together: every hop on the route is measured many times, with the packet loss and the latency jitter of that hop. For the intermittent problems that a single traceroute never shows.
Need another tool?
Pick one of the 25 belowOutput
What the online MTR test measures
An online MTR test combines ping and traceroute: it discovers the path to the destination and then measures every hop on it repeatedly, reporting for each the packet loss, the packets sent and the last, average, best and worst round-trip times with their standard deviation. Here it runs in report mode with five rounds, up to twenty hops, addresses as numbers, from the IPVIEW origin nearest you: inside Iran for visitors there and Germany otherwise. The result says which.
Five rounds is enough to see a path that is dropping or wobbling and not enough to prove one that is marginal; a run can take ten seconds or more to a far host, and the tool shares a budget of six runs a minute with the Full report, Reachability, Ping, Traceroute and Port check. The result is the raw report from the mtr command, the form network operators are used to reading and quoting.
How to read the result
Read the Loss% column from the bottom up. Loss at the destination, or loss that begins at a hop and continues through every hop after it, is real. Loss at a single middle hop with clean hops after it is that router rate-limiting its own replies and harms nothing. A hop at 100% while later hops answer is a router that does not reply at all, the asterisk of a traceroute.
Then the times. Avg against Best shows the queueing on the path; a Wrst far above Avg and a large StDev mean jitter, which breaks calls before it troubles pages. A jump in Avg that stays for every later hop locates the slow link. Each time is a round trip, so the return path, not shown, is half of every number. Five rounds is a small sample: 20% loss is one packet.
When it is useful
A connection to a server drops for a few seconds every so often and a single Traceroute never catches it. MTR holds the path under observation for five rounds and shows where the loss starts, the one thing a provider can act on. Run it from inside Iran and from Germany, by visiting from each side, to see whether the trouble is on the international segment.
A video call or a game stutters while downloads are fine: the StDev and Wrst columns show the jitter and which hop introduces it. For a quick check that the host answers, Ping is enough; for the route alone, Traceroute; WHOIS on a hop's address names whose network it is.
Common questions
What is MTR?
A tool that runs traceroute and ping together: it finds every hop on the path and then sends packets to each repeatedly, so loss and latency are seen per hop rather than only at the destination. The name stands for My Traceroute.
Why does one hop show packet loss when the destination shows none?
The router at that hop limits how fast it answers about itself while forwarding traffic normally. Loss is real only when it continues through every hop after the one where it begins, or appears at the destination.
MTR or ping?
Ping sends four packets to the destination only and says whether it is up and how far. MTR measures every hop five times and says where loss or jitter begins. Use ping first; use MTR when ping shows loss or the problem is intermittent.
Is the MTR test run from inside Iran?
For visitors inside Iran, yes, from the IPVIEW server there; for visitors elsewhere, from Germany. The vantage point is written under the result and carried with a shared link.
Limits. The DNS, WHOIS and SSL tools allow up to 20 requests a minute per IP address. Ping, traceroute and MTR send real packets to their target, so they allow 6 a minute.
The port check runs only against your own IP address. That is deliberate: the question people actually have, "is this port reachable from outside?", is answered by it, while this server cannot be used to scan anyone else's network.
Private and reserved addresses. These are refused by the tools that really connect to their target: the SSL check, ping, traceroute, MTR and the port check. The DNS tools have no such limit, because they only ask a nameserver a question and never connect to the address itself.