Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

VPS & Linux

VPS packet loss: how to test it and locate the failing path

Published August 2026 · 2 min read · Updated 2026-09-05

Packet loss matters when traffic that should arrive does not, but diagnostic tools can overstate it. The useful investigation proves loss end to end, identifies whether it is inbound or outbound, and correlates it with interface errors, congestion, firewall behavior, or a specific route.

Prove loss at the destination

Run repeated probes long enough to avoid declaring a problem from two packets. If an intermediate hop appears to drop packets but the final destination does not, the hop may simply rate-limit diagnostic replies.

Test the protocol that users actually depend on when practical. ICMP, TCP, and UDP can encounter different policy and queueing.

Inspect guest and interface counters

Check RX/TX drops, errors, overruns, retransmissions, socket pressure, and firewall counters. A saturated application receive queue or host firewall can create local loss symptoms without a provider-network fault.

Look at CPU and softirq pressure during the same interval on busy systems. Network processing can suffer when the guest itself is starved.

Compare directions and networks

A path can be asymmetric. Test from the VPS to the client-side network or a nearby probe as well as toward the VPS. Compare another ISP or region to determine whether the problem follows one route.

Keep timestamps in UTC so provider and application logs can be aligned accurately.

Escalate with continuity evidence

A useful provider report includes source/destination, duration, packet count, final-hop loss, route continuity, interface counters, and whether application retransmissions increased. Avoid conclusions based solely on one MTR screenshot.

  • Use final-hop loss as the primary signal.
  • Check retransmissions and interface counters.
  • Compare both directions where possible.
  • Retain exact timestamps for escalation.

Next step

Test packet loss from more than one vantage point, compare hops and application symptoms, and avoid treating every ICMP anomaly as an outage.

Explore DotMoose VPS hosting

Keep reading

Related guides.

HTTP 500, 502 and 503 errors explained for website owners

Learn what HTTP 500, 502 and 503 errors usually indicate, which layer to investigate, what evidence to collect, and when restarting a service is not the real fix.

Read the guide

Linux file permissions: ownership, modes, groups and ACLs explained

Understand Unix ownership and rwx modes, then use groups and ACLs where needed so services can access files without opening them to every user.

Read the guide

Moving a DreamHost VPS to Canadian hosting

Inventory the server, copy it safely, test it, and cut DNS over with a rollback plan.

Read the guide

More vps & linux guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move