Packet loss causes intermittent connectivity issues, degraded performance, and unreliable connections — this guide covers systematically diagnosing where packet loss is occurring and whether it's within your control to fix.
What Packet Loss Looks Like
Symptoms include intermittent connection drops, degraded VoIP/video call quality, slow or stalling downloads, and generally unreliable network behavior that isn't consistently broken but isn't consistently working either.
Step 1 — Basic Ping Test
ping -c 100 8.8.8.8Review the summary at the end showing packet loss percentage — any sustained loss (even 1-2%) is worth investigating further, though occasional single dropped pings can be normal network noise.
Step 2 — Use MTR for Path-by-Path Analysis
mtr 8.8.8.8Shows loss percentage at each hop along the network path — helps identify whether loss is happening at your own server, somewhere in the middle of the path (outside your control), or at the final destination.
Step 3 — Distinguish Between Local and Remote Issues
If loss appears at the very first hop (your own server/network), it's likely something you can address; if loss appears several hops into the path, it's often outside your direct control (an intermediate network provider's issue).
Step 4 — Test to Multiple Different Destinations
mtr 1.1.1.1
mtr 8.8.8.8
mtr your-actual-important-service.comIf loss is consistent across all destinations, the issue is likely closer to your own server/network; if it's specific to one destination, the issue may be specific to that particular network path.
Step 5 — Check Your VPS's Own Network Interface for Errors
ip -s link show eth0Shows interface-level statistics including errors and dropped packets — a genuine local hardware/driver issue would show up here.
Step 6 — Check for Resource Exhaustion Causing Drops
Severe CPU or network buffer exhaustion can itself cause packet drops that aren't a "network" problem per se — see How to Diagnose and Fix High CPU Usage on a VPS; verify the server itself isn't so overloaded that it's dropping packets due to resource constraints.
Step 7 — Check Firewall/Rate Limiting Configuration
Overly aggressive rate limiting or firewall rules can sometimes present as apparent packet loss — review recent firewall/rate-limit configuration changes if the issue started around the same time as a configuration change.
When It's Genuinely Outside Your Control
If MTR consistently shows loss at hops clearly beyond your server/provider's own network (an intermediate transit provider), there's often limited direct action you can take beyond reporting to your provider, who may be able to investigate routing alternatives or escalate to their own upstream providers.
Contacting Your VPS Provider
Share your specific MTR results when reporting suspected network issues — concrete data showing exactly where loss is occurring helps support investigate far more effectively than a vague "my connection feels unreliable" report.
Common Errors
Loss appears only during specific times of day — may indicate network congestion during peak usage periods on a shared network path; useful pattern information to share with your provider.
Continue Reading
- How to Diagnose and Fix High Network Latency
- How to Troubleshoot Common VoIP Quality Issues (Jitter, Latency, Packet Loss)
- How to Diagnose a Slow VPS: Complete Performance Checklist
Browse more articles in Troubleshooting & FAQ.
