The short answer
Packet loss happens when one or more packets sent across a network do not reach their intended destination, or arrive too late to be useful. A small amount can be normal on some networks, but sustained or bursty loss can cause calls to break up, games to stutter, streams to buffer, and downloads to slow down or fail.
Loss is a symptom, not one diagnosis. It can originate in a home Wi-Fi link, a cable, router, internet provider, remote server, or any part of the route in between.
Why applications react differently to loss
IP is a best-effort delivery system. It does not promise every packet arrives. Higher-level protocols decide how to respond. TCP detects missing data and retransmits it, which preserves correctness but can increase delay and reduce throughput. UDP does not provide retransmission itself, so a real-time application may skip a missing audio or game packet rather than wait for it.
That is why the same loss can feel different across applications. A file transfer may slow down but eventually finish; a voice call may have a brief gap; a game may show a delayed action. Learn more about these tradeoffs in TCP vs UDP.
Common causes of packet loss
Congestion is a common cause. When a router, Wi-Fi access point, or provider link receives more traffic than it can queue or forward, it may drop packets. Heavy uploads, busy shared networks, or an overloaded network device can all contribute.
Wi-Fi interference and weak signal can cause repeated retransmissions or dropped frames before traffic even leaves your home. Distance, walls, crowded radio channels, and older equipment can matter. Testing briefly with a wired connection is a useful way to separate a wireless problem from a wider internet issue.
Faulty or mismatched equipment can also be responsible. Damaged cables, loose connectors, failing ports, outdated router firmware, or link-speed and duplex problems can produce errors and loss. These issues often affect a local device or interface more consistently than a distant-routing issue would.
Network routing, peering, and remote service load are further possibilities. A particular destination may be congested or have a poor route while other sites work normally. The remote server itself can also be overloaded, so an application failure is not automatically evidence of packet loss on your own connection.
Configuration and filtering can look like loss. A firewall rule, overloaded VPN gateway, incorrect MTU, or blocked control traffic may discard some packets selectively. An MTU problem can especially affect larger transfers while smaller requests appear healthy.
Packet loss is not latency or jitter
Latency is the time a packet takes to travel. Jitter is variation in that delay. Both can hurt real-time traffic without any packet being lost. Conversely, a connection can have low average latency but occasional loss.
Measuring one ping result is not enough to distinguish them. Look for a pattern over time and compare more than one destination. Some routers intentionally de-prioritize or rate-limit diagnostic ICMP traffic, so a ping result alone may not reflect the performance of an application connection.
A safe troubleshooting sequence
Start close to your device and move outward:
- Check whether the issue affects one app, one destination, or all connections.
- Pause large downloads or uploads and retry; this can reveal local congestion.
- Test a wired connection or move closer to the Wi-Fi access point.
- Restart only the equipment you control after noting the symptoms, and check cables and device updates.
- Compare another network, such as a trusted mobile connection, and another destination.
- If the problem persists, collect timestamps, affected services, and test results for the network administrator or ISP.
Avoid changing several variables at once. It is tempting to change DNS, a VPN, Wi-Fi channels, and MTU together, but that makes the actual cause harder to find. A VPN can change the path and may make a routing issue appear different, but it is not a general packet-loss repair tool.
The takeaway
Packet loss occurs when network traffic is dropped or becomes unusable. Congestion, Wi-Fi quality, equipment faults, routing, remote services, and configuration can all be involved. Compare paths and destinations methodically before concluding where the fault lies.
