Understanding Packet Loss
Packet loss occurs when data packets fail to reach destination.
Diagnose Packet Loss
# Basic test
ping -c 100 YOUR_SERVER_IP | grep -E "loss|avg"
# Detailed path analysis
mtr --report YOUR_SERVER_IP
# Continuous monitoring
iperf3 -c YOUR_SERVER_IP
Interpret mtr Output
Loss at intermediate hops may not indicate problem if final hop shows 0% loss.
Real problem: Loss > 5% at final destination.
Fix 1: Check Server Resource Saturation
High CPU/memory can cause packet drops:
# Interface errors
netstat -i
ifconfig | grep errors
# CPU usage affecting network processing
top
mpstat -P ALL 1
Fix 2: Check Network Interface
# Check for CRC errors
ethtool -S eth0 | grep -i error
# Or
ip -s link show
Contact Hostxpeed if hardware errors present.
Fix 3: Adjust Network Buffers
# Increase buffer sizes
sudo sysctl -w net.core.rmem_max=26214400
sudo sysctl -w net.core.wmem_max=26214400
sudo sysctl -w net.ipv4.tcp_rmem="4096 87380 26214400"
sudo sysctl -w net.ipv4.tcp_wmem="4096 65536 26214400"
Fix 4: Reduce MTU
Packet fragmentation can cause loss:
# Test optimal MTU
ping -M do -s 1472 YOUR_SERVER_IP
# Reduce if needed (e.g., to 1400)
sudo ip link set dev eth0 mtu 1400
Fix 5: Check for DDoS or Traffic Spike
# Monitor traffic
sudo iftop
sudo nethogs
sudo tcpdump -i eth0 -c 1000
Fix 6: Contact ISP/Provider
If loss occurs consistently at a specific hop outside your control, contact your ISP or Hostxpeed to escalate to upstream providers.