Network Path Troubleshooting using ping, traceroute, and mtr
Network performance on a Hovixa VPS depends on the path quality between the client and the server. When users report "lag" or connectivity drops, the bottleneck could be your VPS, the user's ISP, or any of the intermediary routers (hops) in between. To solve this, we use a tiered approach: ping for reachability, traceroute for path mapping, and MTR for persistent diagnostic data.
1. Verifying Reachability with ping
The ping utility uses ICMP Echo Request packets to determine if a host is alive and to measure the Round Trip Time (RTT). It is the quickest way to confirm if a server is reachable.
# Send 5 packets to verify latency
ping -c 5 your_vps_ip
Note: If ping fails but your website still loads, your firewall (UFW/iptables) is likely blocking ICMP traffic.
2. Mapping the Route with traceroute
traceroute identifies every router (hop) a packet passes through to reach its destination. It works by incrementally increasing the TTL (Time to Live) of packets. If a packet's TTL reaches zero at a router, that router sends an ICMP "Time Exceeded" message back, revealing its identity.
# Trace the path to your server using TCP (often bypasses ICMP blocks)
traceroute -T -p 80 your_vps_ip
3. Real-Time Diagnostics with MTR (My Traceroute)
mtr combines the functionality of ping and traceroute into a live, constantly updating report. It is the gold standard for identifying packet loss at specific hops. Unlike a static traceroute, MTR reveals intermittent issues that only appear over time.
# Run MTR in report mode for 10 cycles
mtr -rw your_vps_ip
4. Troubleshooting Diagnostic Matrix
| Symptom | Diagnostic Result | Likely Problem |
|---|---|---|
| High Latency (Last Hop) | RTT > 200ms at the final IP | Server-side congestion or distance. |
| Packet Loss (Mid-Path) | Loss at Hop 4, but 0% at Hop 10 | ICMP Rate Limiting at the router (Normal). |
| Consistent Loss (To End) | Loss starts at Hop 5 and continues | Network congestion or faulty cable at Hop 5. |
| No Route to Host | Traceroute stops at your ISP | Local network issue or ISP outage. |
5. Technical Implementation Details
- ICMP Rate Limiting: Many enterprise routers prioritize transit traffic over ICMP. If you see 50% packet loss on a middle hop but 0% at the destination, that hop is simply ignoring your diagnostic packets—this is not a real network issue.
- TCP vs UDP vs ICMP: Standard Linux traceroute uses UDP. Windows
tracertuses ICMP. If one fails, trytraceroute -Tto use TCP port 80/443, which is more likely to pass through firewalls. - Jitter (StDev): In MTR, the StDev (Standard Deviation) column measures "Jitter." High jitter (variance in RTT) is often more detrimental to VoIP and gaming than high constant latency.
Sysadmin Advice: When reporting network issues to Hovixa support, always provide a 100-packet MTR report (`mtr -c 100 -rw your_ip`). This provides the data needed to identify exactly which Tier-1 provider or peering point is causing the bottleneck.
