ForceVPS Network Tools

Online MTR: Packet Loss and Route Quality Analysis

Use ForceVPS Online MTR to perform advanced network diagnostics. Combining the capabilities of Ping and Traceroute, MTR helps identify packet loss, unstable hops, latency issues, and overall route quality to websites, servers, DNS resolvers, and other internet services over IPv4 and IPv6.

Back to diagnostics Open ticket

6 quick targets

4 launch POPs

20 default cycles

MTR request

Run an MTR Test in Real Time

Use MTR to identify network bottlenecks and unstable routes. The test combines Ping and Traceroute to provide detailed diagnostics for websites, servers, and internet services.

Quick resources

MTR target

Launch point

Protocol

MTR parameters

Primary parameters

Report cycles

Report options

The agent response or a transport error will appear in the console on the right.

CLI

Result console

Target forcevps.com

Node Kyiv, Ukraine

Protocol IPv4

$ lg mtr --node kyiv --family ipv4 --report-cycles 20 --show-asn --wide-report forcevps.com Start: live MTR preview HOST: kyiv.forcevps Loss% Snt Last Avg Best Wrst StDev ASN 1.|-- edge-gw.kyiv.forcevps 0.0% 20 0.4 0.4 0.3 0.6 0.1 AS65010 2.|-- core-link.kyiv.forcevps 0.0% 20 2.1 2.2 2.0 2.5 0.1 AS65010 3.|-- forcevps.com 0.0% 20 18.2 18.4 18.1 18.9 0.3 AS21100

FAQ

What is MTR and how does it differ from Ping and Traceroute?

MTR is a comprehensive network diagnostic tool that combines the capabilities of Ping and Traceroute. It repeatedly checks every hop along the route and reports packet loss, average latency, and connection stability to a website, server, or IP address.

How can I run an online MTR test to a domain or IP address?

Enter a domain name or IP address, select a test location, choose IPv4 or IPv6, and set the number of report cycles. The online MTR tool will run a series of checks and show the quality of each section of the network route.

What do Loss%, Snt, Last, Avg, Best, Wrst, and StDev mean in an MTR report?

Loss% is the percentage of lost packets, Snt is the number of requests sent, Last is the latency of the most recent response, and Avg is the average latency. Best and Wrst are the lowest and highest recorded values. StDev shows latency variation: a lower value generally indicates a more stable connection.

How can I identify real packet loss in MTR results?

A genuine problem is usually indicated when packet loss begins at a particular hop and continues through all subsequent hops, including the destination server. If Loss% appears only at one intermediate hop while later hops respond without loss, that router is probably limiting its responses to diagnostic requests.

How many MTR report cycles should I use?

Twenty cycles are usually enough for a quick network check. If the issue is intermittent or you need more accurate packet loss and latency stability data, run a longer test. More cycles provide more reliable statistics but also increase the test duration.

Why should I display ASN and hostnames in an MTR report?

Hostnames make the network route easier to read, while ASN information identifies the autonomous system or network operator responsible for each section. This helps determine whether the problem is within the hosting provider's network, a transit carrier, or the destination service.

Why can IPv4 and IPv6 MTR results be different?

IPv4 and IPv6 may use different routes, network operators, and internet exchange points. As a result, the number of hops, latency, and packet loss to the same domain may differ. Testing IPv4 and IPv6 separately helps identify protocol-specific availability or routing problems.