Understanding VoIP Packet Loss: What It Means for Call Quality

What is packet loss?

When you make a VoIP call, your voice is broken into small data packets that travel across the internet to the other person. Packet loss occurs when some of those packets never arrive. The result: gaps in audio, robotic-sounding speech, or words that simply disappear mid-sentence.

Even a small amount of packet loss can degrade a conversation. At 1% loss, most listeners will notice subtle artifacts. At 3-5%, calls become difficult. Above 5%, communication breaks down entirely.

Why packets get lost

Packet loss has several common causes, and understanding which one is affecting your network is the first step toward fixing it.

Network congestion

The most frequent culprit. When too many devices or applications compete for bandwidth, routers start dropping packets they cannot handle. This is especially common on shared office networks during peak hours, or on home connections where a video stream is competing with your phone system.

Faulty hardware

Aging switches, damaged cables, or overheating routers can all introduce packet loss. If the problem is consistent regardless of time of day or network load, hardware is a likely suspect.

Wireless interference

Wi-Fi introduces an entire layer of potential loss. Microwave ovens, Bluetooth devices, neighboring access points on the same channel. All of these can cause packet drops on wireless connections. For VoIP, a wired connection is always preferable.

ISP issues

Sometimes the problem is upstream. Poor peering between ISPs, oversubscribed links, or routing inefficiencies can all cause packet loss between your network and your VoIP provider. These issues are harder to diagnose because they happen outside your network boundary.

Misconfigured QoS

Quality of Service (QoS) settings prioritize certain types of traffic. When misconfigured, voice packets may be treated as low priority and dropped first during congestion. Properly configured QoS should give voice traffic the highest priority on your local network.

How to measure packet loss

Basic network tools like ping can give you a rough indication of packet loss, but they do not tell the full story for voice traffic. VoIP packets use UDP rather than TCP, which means lost packets are not retransmitted. They are simply gone. A ping test using ICMP may show different results than what your actual voice traffic experiences.

For accurate measurement, you need a test that simulates real voice traffic patterns: small packets sent at regular intervals, using UDP, with results measured over a meaningful time period. Our VoIP quality test does exactly this. Single-point-in-time tests can miss intermittent issues that only appear during peak usage.

What "acceptable" looks like

Industry standards from the ITU-T suggest these quality thresholds for voice traffic:

• Below 1%: Imperceptible to most listeners. This is the target.
• 1-2.5%: Noticeable artifacts on careful listening. Usable but degraded.
• 2.5-5%: Clearly impaired. Frequent audio gaps and distortion.
• Above 5%: Unusable for professional communication.

These numbers assume modern codecs with some built-in loss concealment. Older codecs or poorly implemented jitter buffers will show degradation at even lower loss rates.

What you can do

If you have identified packet loss as your quality problem, here are the practical steps:

On your network: Implement QoS to prioritize voice traffic. Move VoIP endpoints to wired connections. Segment voice traffic onto a dedicated VLAN. Replace aging network hardware.

With your ISP: Share test results that show packet loss occurring beyond your network boundary. Traceroute data showing where loss begins gives your ISP something actionable to investigate.

With your VoIP provider: Ask about codec options. Some codecs like Opus handle loss better than others through built-in redundancy and interpolation. Ask whether your provider supports packet loss concealment (PLC) algorithms.

The blame game

Here is the reality most VoIP users face: when call quality suffers, the ISP blames the VoIP provider, and the VoIP provider blames the ISP. Without independent test data showing exactly where the problem occurs, you are stuck in the middle with no leverage.

This is the problem VoIP Test was built to solve. Independent, data-driven analysis that shows you, and your providers, exactly where the breakdown happens.

Want to understand how packet loss interacts with latency and jitter? See Latency, Jitter, and Packet Loss: The Details. For the full picture of how data moves across networks, start with Packets: How Data Actually Moves in our VoIP From the Ground Up series.