prefixkit Ask an engineerAsk RU

IP & network

MTR and traceroute analyzer

Paste mtr, traceroute, tracert, WinMTR or MikroTik output: see the network (AS) and country of every hop, which loss is real and which is a router ignoring probes, where delay grows, and whom to complain to.

Parsed in your browser. Network and country come from the open DB-IP data. IP Geolocation by DB-IP

How to capture a proper mtr

# Linux / macOS: 100 probes, with AS numbers
mtr -rwzc 100 example.com
# the same over TCP port 443 (when ICMP is filtered)
mtr -rwzc 100 -T -P 443 example.com
# Windows
tracert -d example.com
# MikroTik
/tool traceroute example.com count=10

How to read loss

The key rule: loss on an intermediate hop means nothing if later hops show none. Backbone routers answer probes last and often skip them. A real problem is loss that appears at some hop and stays until the end; then the network where it starts is to blame.

Delay

A delay increase that holds to the end is distance: Moscow to Frankfurt is about 40 ms, Europe to the US about 80–100 ms. A single slow hop in the middle with normal delay after it is not a problem either.

Run a trace from many countries with our probe traceroute; check your own line with the speed test.