Acceptable Packet Loss for VoIP: Testing, Causes & Fixes

The Short Answer

For business VoIP, packet loss should be as close to 0% as possible. As a practical screening target, under 1% is generally a healthy result. Persistent loss in the 1% to 3% range deserves investigation, and sustained loss above that range is increasingly likely to create audible gaps, clipped words, or choppy calls.

There is no single percentage that guarantees a call will sound good or bad. The codec, where the loss occurs, whether packets are lost in bursts, and how the phone platform conceals missing audio all affect what callers actually hear. Twilio notes that cumulative packet loss above 5% is generally noticeably choppy, while some real-time voice systems flag repeated samples at 1% or higher for investigation.

The goal is therefore not to operate just below a maximum. A business phone network should aim for near-zero packet loss with enough stability that busy periods do not create bursts of missing voice traffic.

Not sure whether your connection is losing voice packets?

Run the Tier 1 Telecom VoIP Internet Quality Test, then compare the result with latency, jitter, and loaded-network performance.

Test My VoIP Connection

Key Takeaways

Zero packet loss is the ideal target for real-time voice.
Under 1% is a practical screening target for a healthy VoIP connection.
Persistent 1% to 3% loss should be investigated rather than accepted as normal.
Bursts of consecutive lost packets can sound worse than the same average loss spread over time.
Packet loss commonly creates missing words, clipped syllables, gaps, and choppy audio.
Wi-Fi, congestion, bad cabling, overloaded equipment, and ISP problems can all create packet loss.
Packet loss, jitter, and latency should be evaluated together.
A browser test is a useful screening tool, but actual call records can reveal route-specific problems.

What Is Packet Loss?

VoIP converts speech into a continuous stream of small digital packets. Those packets travel from the phone or application through the local network, across the internet, through the phone platform, and ultimately toward the other caller.

Packet loss occurs when some of those packets never arrive at the destination in time to be used.

For ordinary web browsing, a lost packet can often be retransmitted without the user noticing. Real-time voice is different. The conversation cannot stop and wait for every missing packet to be resent. By the time a replacement arrived, the speaker would already have moved on.

Phone systems and codecs can conceal limited loss by estimating or smoothing over small gaps. That helps, but concealment cannot recreate an unlimited amount of missing speech.

Our broader VoIP Call Quality guide explains how packet loss interacts with jitter, latency, bandwidth, and Quality of Service. This article focuses specifically on packet-loss thresholds, testing, diagnosis, and corrective action.

What Is an Acceptable Packet-Loss Percentage for VoIP?

Packet loss	Practical interpretation	What to do
0%	Ideal	No loss is the target for a well-performing voice path.
Below 1%	Strong target	Usually a healthy screening result, while still reviewing jitter and latency.
1%–3%	Investigate	Look for recurring loss, bursts, congestion, Wi-Fi instability, or provider issues.
Above 3%	Likely impact	Audible degradation becomes increasingly likely and corrective action is warranted.
Above 5%	Severe concern	Twilio notes that loss above 5% is generally noticeably choppy; investigate immediately.

These ranges are practical troubleshooting guides, not universal guarantees. Different codecs and platforms handle loss differently. A short burst of several missing packets can be more disruptive than the same average percentage spread evenly across a long call.

How Does Packet Loss Sound on a VoIP Call?

Missing syllables

Words may sound clipped because one small portion of the audio stream never arrived.

Short gaps

A caller may hear brief silences even though the other person was speaking continuously.

Choppy or broken speech

Repeated missing packets can make a sentence difficult to follow or force callers to repeat information.

Robotic audio

Jitter and packet loss often occur together, producing distorted or unnatural-sounding speech.

Packet loss is not always symmetrical. One person may hear the other perfectly while audio traveling in the opposite direction is degraded. That is why troubleshooting should identify which direction is affected rather than assuming the entire connection is equally impaired.

Why Burst Packet Loss Matters More Than the Average

An average packet-loss percentage does not tell the whole story.

Imagine two ten-minute calls that both report 1% packet loss. On the first call, isolated packets are lost occasionally and the codec conceals most of them. On the second call, the missing packets arrive in concentrated bursts during two important sentences.

The mathematical average may be similar, but the second call can sound much worse.

For that reason, a good troubleshooting process looks for:

Whether loss is continuous or intermittent
Whether several packets disappear in sequence
Whether loss appears only while the network is busy
Whether it affects upload, download, or both directions
Whether actual phone-platform call records show the same pattern

Packet Loss vs. Jitter vs. Latency

These metrics are related, but they describe different network problems.

Packet loss

Voice packets never arrive in time to be used. The result is commonly gaps, clipping, or missing speech.

Jitter

Packet arrival timing varies. Excessive jitter can overflow a jitter buffer and effectively become packet loss. See What Is a Good Jitter Score for VoIP?

Latency

Packets take too long to travel. The audio may remain clear but the conversation feels delayed. See What Is Acceptable Latency for VoIP?

Bandwidth

The connection may not have enough available capacity during busy periods. See What Internet Speed Does VoIP Require?

How Do You Test Packet Loss for VoIP?

Start with a network test from the same connection used by the business phones. Do not rely on a test from a different office, a cellular connection, or a device on another network.

Test over wired Ethernet first. This removes Wi-Fi interference from the initial baseline.
Run the test while the office is quiet. Record packet-loss indicators, latency, jitter, upload, and download performance.
Repeat the test during a busy period. Backups, cloud synchronization, video meetings, and large uploads can expose congestion that is invisible when the network is idle.
Compare wired and Wi-Fi results. If loss appears only on Wi-Fi, focus on wireless coverage, interference, channel use, and access-point capacity.
Repeat the test. One clean result does not disprove an intermittent problem.
Review actual call-quality records. When the phone platform exposes RTP or call-quality metrics, compare affected calls with the browser-test results.

A browser test is a screening tool

The test server and your VoIP provider may use different network routes. A browser test can identify obvious local-network and internet problems, but a route-specific problem may appear only in actual call records.

What Causes Packet Loss on VoIP Calls?

Network congestion

When too much traffic competes for the same connection, routers and firewalls may drop packets rather than allow queues to grow indefinitely. Upload saturation is especially easy to miss because many business internet plans provide much less upstream capacity than downstream capacity.

Wi-Fi interference or weak coverage

Wireless devices share radio airtime. Interference, weak signals, busy channels, roaming problems, or overloaded access points can force retransmissions and increase loss. Microsoft specifically recommends optimizing Wi-Fi and using QoS or Wi-Fi Multimedia for real-time media where appropriate.

Overloaded routers or firewalls

A connection can have adequate bandwidth while the network appliance processing the traffic is at its limit. Security inspection, VPN processing, traffic shaping, or an aging router can become a bottleneck.

Faulty cabling or switch ports

Bad Ethernet cabling, damaged connectors, duplex problems, or failing switch ports can introduce errors before voice traffic even reaches the internet connection.

Internet-provider problems

Loss can originate beyond the office. Congestion, routing faults, damaged infrastructure, or upstream equipment problems can affect a connection even when the local network is healthy.

Jitter-buffer overflow

Packets that arrive too late can become functionally equivalent to lost packets. Twilio notes that jitter is a common contributor to packet loss, especially on Wi-Fi and congested networks.

Seeing Packet Loss or Choppy Calls?

Tier 1 can help isolate whether the problem is local Wi-Fi, cabling, a switch or firewall, internet congestion, the ISP path, or the phone platform itself. The goal is to identify where packets disappear before replacing equipment or buying more bandwidth blindly.

Get Help With VoIP Call Quality

How Do You Fix Packet Loss for Business VoIP?

Establish a wired baseline. If wired phones are clean while wireless devices experience loss, correct the Wi-Fi problem first.
Check physical errors. Review switch-port counters, cabling, connectors, and link negotiation where possible.
Look for saturation. Determine whether loss appears during backups, uploads, video meetings, camera traffic, or other heavy use.
Review router and firewall capacity. CPU load, security inspection, VPN processing, and outdated hardware can all affect real-time traffic.
Prioritize voice where appropriate. Microsoft recommends QoS to give real-time voice preferential treatment when networks are busy. QoS cannot repair a failing circuit, but it can prevent less-sensitive traffic from crowding out voice.
Compare multiple destinations and times. This helps separate a local-network problem from an ISP or routing problem.
Escalate with evidence. Give the ISP or phone provider timestamps, affected calls, test results, source location, and direction of the audio problem.

When Should You Call the ISP vs. the Phone Provider?

Start with the local network or ISP when...

Multiple real-time applications show loss, wired tests are affected, the problem follows internet usage, or packet loss appears before traffic reaches the phone platform.

Start with the phone provider when...

General internet tests are clean but particular calls, destinations, carriers, or provider routes consistently show degradation.

In practice, the fastest resolution often comes from comparing evidence from both sides instead of assuming one vendor is responsible.

Frequently Asked Questions

Is 1% packet loss acceptable for VoIP?

Packet loss should be as close to zero as possible. Less than 1% is a practical screening target, but burst loss or a sensitive codec can create audible issues even when the average looks modest.

Can Wi-Fi cause packet loss?

Yes. Weak signal, interference, busy channels, roaming behavior, and overloaded access points can all contribute to missing or late voice packets.

Can packet loss cause one-way audio?

Severe loss in one direction can make audio appear missing, although true one-way audio can also be caused by firewall, NAT, routing, or session-establishment problems.

Will more bandwidth fix packet loss?

Only when congestion or saturation is the cause. More bandwidth will not repair bad cabling, Wi-Fi interference, failing equipment, or an upstream routing problem.

Is packet loss worse than jitter?

They are different problems and often occur together. Jitter describes inconsistent arrival timing; excessive jitter can cause packets to arrive too late and effectively become packet loss.

How often should I test?

Test when the network is quiet, during normal peak use, and when users report problems. Repeated measurements are more useful than a single snapshot.

Continue Learning

Technical References

For additional network-quality guidance, see Microsoft’s Quality of Service guidance for Teams and Twilio’s Voice Insights call-quality documentation. Thresholds vary by codec, platform, route, and the pattern of loss, so transport metrics should be interpreted alongside actual caller experience.

Test the Network Before Packet Loss Reaches Your Customers

Use the free Tier 1 Telecom VoIP Internet Quality Test to screen your connection, or have us help investigate recurring call-quality problems and plan a reliable business phone environment.

Run the Free Test Talk to a VoIP Specialist

Tier 1 Telecom: (866) 808-4371