RamNode logo
    Sign UpLogin
    Back to Legacy KVM Documentation

    What is MTR?

    Understanding and using the MTR network diagnostic tool

    On This Page

    MTR is a network diagnostic tool which combines ping and traceroute to provide comprehensive network path analysis.

    How MTR Works

    When a computer connects to another computer over the internet, the network traffic is sent through a series of routers, or "hops", between the source and destination. MTR identifies each of these hops and gauges latency and packet loss against each one, including the destination.

    This information allows us to figure out exactly where a network problem lies - whether it's your local connection, an intermediate router, or the destination server.

    Why We Request MTR

    When investigating network problems, we request MTR results because they provide:

    • Complete Route Information: See every hop between source and destination
    • Packet Loss Data: Identify which hops are dropping packets
    • Latency Measurements: Pinpoint where delays are occurring
    • Continuous Monitoring: Statistics over time, not just a single test

    MTR vs Traceroute

    Unlike traceroute which runs once and exits, MTR continuously monitors the connection, providing statistics about packet loss and latency at each hop over time. This makes it much more useful for diagnosing intermittent issues.

    Installing MTR

    Windows

    1. Download WinMTR from SourceForge
    2. Extract the archive
    3. Run the executable as Administrator

    Linux

    Install MTR
    # Debian/Ubuntu
sudo apt-get install mtr-tiny

# CentOS/RHEL
sudo yum install mtr

# Fedora
sudo dnf install mtr

    macOS

    brew install mtr

    Running MTR

    Windows (WinMTR)

    1. Open WinMTR
    2. Enter the destination hostname or IP in the "Host" field
    3. Click "Start"
    4. Let it run for at least 100 packets or a few minutes
    5. Click "Stop"
    6. Click "Copy Text to clipboard" or export results

    Linux/macOS

    # Basic MTR command
sudo mtr your-vps-ip.com

# Run for 100 packets and generate report
sudo mtr -r -c 100 your-vps-ip.com

# Report mode with better formatting
sudo mtr -r -w -c 100 your-vps-ip.com

    Understanding MTR Results

    MTR displays several columns of information:

    • Host: The hostname or IP of each hop
    • Loss%: Percentage of packets lost at this hop
    • Snt: Number of packets sent
    • Last: Latency of the last packet
    • Avg: Average latency
    • Best: Best (lowest) latency
    • Wrst: Worst (highest) latency
    • StDev: Standard deviation (consistency)

    Interpreting Packet Loss

    • 0% Loss: Normal, no issues
    • Loss at final hop only: Usually indicates destination server issues
    • Loss at intermediate hop: Often rate limiting, not actual packet loss (if later hops are fine)
    • Loss increasing at each hop: Indicates a problem at the hop where loss starts

    Important: Rate Limiting

    Many routers rate-limit ICMP responses for MTR/ping but forward regular traffic normally. If you see packet loss at an intermediate hop but 0% at the destination, the intermediate hop is likely just rate-limiting diagnostic traffic.

    Best Practices for Support Tickets

    When submitting MTR results to support:

    1. Run Both Directions:
      • From your computer to your VPS
      • From your VPS to your computer
    2. Let it Run: At least 100 packets or a few minutes
    3. During the Problem: Capture MTR when issues are occurring
    4. Include Timestamps: Note when the test was run
    5. Enable ICMP: If testing from your home, ensure ICMP ping is enabled on your router

    Common Network Issues MTR Reveals

    High Latency at Specific Hop

    If latency suddenly jumps at a specific hop and remains high, that hop or the link before it is likely congested.

    Packet Loss Starting at Specific Point

    Loss that begins at a hop and continues to the destination indicates a problem at that hop.

    Routing Issues

    Unexpected routes (e.g., traffic routing through multiple countries) can indicate BGP routing problems.

    Destination Unreachable

    If MTR cannot reach the destination at all, it may indicate firewall blocks, server downtime, or routing black holes.

    Alternative Tools

    Related network diagnostic tools:

    • Ping: Simple latency and packet loss test
    • Traceroute: Shows the route but doesn't provide statistics
    • Looking Glass: Test from our network to destinations (see our Looking Glass guide)

    If you're experiencing network issues, run MTR tests and open a support ticket with the results. Include:

    • MTR from your location to your VPS
    • MTR from your VPS to your location
    • Description of the problem
    • When the issues occur
    • Whether the problem is persistent or intermittent