Definition

What Is Packet Loss? Causes, Effects on Calls and Fixes

Robotic voices, frozen video and words that drop out mid-sentence usually come down to packet loss. Here's what causes it, how to measure it and how calling apps recover.

Packet loss vs jitter

Packet loss

Jitter

What happens

Packets never arrive

Packets arrive, but with uneven timing

Measured as

Percentage of packets lost

Milliseconds of delay variation

How a call sounds

Gaps, clipped words, robotic voice

Choppy audio, small stutters

How video looks

Freezes, blocky patches, smearing

Uneven motion, occasional stalls

Main fixes

FEC, retransmission (NACK), concealment (PLC)

A jitter buffer that waits before playing

Acceptable for calls

Under 1% (Microsoft Teams target, client to edge)

Under 30 ms (same source)

How they connect

Late packets get discarded and count as lost

Severe jitter turns into packet loss

What is packet loss?

Everything you send over the internet is split into packets. Each one travels on its own through routers, switches and radio links. Usually they all arrive. When some don't, that's packet loss.

It's expressed as a percentage: if 1,000 packets are sent and 990 arrive, loss is 1 percent. The pattern matters as much as the number. Random single losses are easy to hide. Burst loss, where several packets in a row go missing, is much harder, because there's nothing nearby to rebuild them from.

How much damage loss does depends on the transport. TCP notices the gap and resends, so web pages and chat messages still arrive complete, just later. Real-time media usually runs over UDP, where a lost packet stays lost unless the app does something about it.

What causes packet loss?

  • Congestion. When a router's queue fills up, it drops new packets. This is the most common cause, and it gets worse when someone on the same connection starts a big upload.

  • Wi-Fi interference. Walls, distance, microwaves and crowded channels corrupt frames. Wi-Fi retries some of them, but not all.

  • Weak mobile signal. Moving between cell towers or into a dead spot causes bursts of loss.

  • Faulty hardware or cables. A failing network card, port or cable drops packets steadily.

  • VPNs and firewalls. Extra hops, small packet size limits and overloaded VPN gateways all add loss.

How packet loss affects calls, and how apps recover

On a voice call, each packet holds about 20 ms of sound. Lose one and you hear a tiny gap. Lose several and words drop out or the voice turns metallic. On video, a lost packet corrupts part of a frame, and because later frames build on earlier ones, the damage spreads as blocks or smears until the next keyframe arrives. Real-time apps use three main tools to cope.

Forward error correction (FEC)

The sender adds redundant data so the receiver can rebuild a missing packet without asking. Opus, the standard WebRTC audio codec, has built-in FEC that carries a low-bitrate copy of the previous frame. For video, WebRTC can use FEC schemes such as ULPFEC and FlexFEC (RFC 8854). FEC costs bandwidth all the time, even when nothing is lost.

Retransmission (NACK)

The receiver sends a negative acknowledgement listing missing packets, and the sender resends them (RFC 4585). It's efficient but only works when the round trip is short enough for the copy to arrive before it's needed. For video, a receiver can also ask for a fresh keyframe with a Picture Loss Indication.

Packet loss concealment (PLC)

When a packet can't be recovered, the audio decoder fills the gap with a best guess based on the sound around it. Good PLC makes a single lost 20 ms packet almost inaudible, but it can't hide long bursts.

Most calling apps also respond to sustained loss by lowering the bitrate, on the assumption that congestion is the cause.

How to test and measure packet loss

  • Ping: ping -c 100 example.com reports the percentage of replies that never came back. It's a quick check, but some routers give ping a low priority, so it can overstate loss.

  • Traceroute tools: mtr (or pathping on Windows) shows loss hop by hop, which helps you find where it starts. Loss at one hop that disappears at later hops is usually just that router ignoring pings.

  • WebRTC stats: in a browser call, getStats() returns packetsLost and packetsReceived for each incoming stream. Compare them over a time window to get a live loss percentage.

  • RTCP reports: RTP receivers send the fraction of packets lost back to the sender every few seconds (RFC 3550). That's how a sender knows to adapt.

For calls, aim for under 1 percent. Microsoft's Teams target is under 1 percent from the user's device and under 0.1 percent from the corporate network edge, measured over 15-second windows.

Rule of thumb: under 1 percent loss is fine for calls if it's spread out. Bursts of loss hurt more than the average suggests.

Fixes and pitfalls

  • Go wired or use 5 GHz. Moving off a busy 2.4 GHz Wi-Fi channel fixes a large share of loss on home and office calls.

  • Prioritize real-time traffic. QoS rules on routers let voice packets skip ahead of downloads.

  • Keep calls off the VPN. Split tunnelling sends call traffic directly to the media servers.

  • Don't hide loss with TCP. Forcing media over TCP stops loss but replaces it with delay, because every gap holds up the packets behind it.

  • More FEC isn't always better. Extra redundancy adds traffic, which can make congestion and loss worse on a link that's already full.

Packet loss in CometChat calls

If you're adding voice or video calls to your app, the media stack deals with lost packets for you. What you control is the network path your users' calls take.

Calls that adjust to the network

CometChat Calls is built on WebRTC, with Opus as the preferred audio codec and VP8, VP9 or H.264 for video. The docs list adaptive bitrate, automatic quality adjustment based on network conditions and automatic reconnection when the network drops. Group calls run through an SFU, so each person uploads one stream. Call recording happens on CometChat's media servers, so a participant's packet loss doesn't damage the recording. Media prefers UDP and falls back to TCP on port 443 through TURN.

See calling features · Start building free

Frequently asked questions

What is an acceptable packet loss percentage?

For voice and video calls, under 1 percent is acceptable and under 0.1 percent is excellent. Gaming and calls start to degrade noticeably above 2 to 3 percent, especially when loss comes in bursts.

How do I check for packet loss?

Run a long ping, such as 100 packets, and read the loss percentage. Use mtr or pathping to see which hop the loss starts at. During a WebRTC call, read packetsLost from getStats().

Can packet loss be fixed?

Usually. Switch to a wired connection or less crowded Wi-Fi, stop large uploads during calls, replace faulty cables or routers, and keep call traffic off VPNs. Loss outside your network needs your ISP.

Is packet loss caused by my internet provider?

Sometimes. If loss shows up on every hop past your router in mtr, it's likely the ISP. If it starts at your router or Wi-Fi, the problem is local.

Does packet loss affect chat messages?

Not the content. Chat usually runs over TCP-based connections such as WebSockets, which resend lost packets. Heavy loss makes messages arrive later, but they arrive complete.

Related terms