"We have 500 Mbps fiber. The calls still sound terrible." This is one of the most common complaints in VoIP, and it reveals a fundamental misunderstanding about what makes voice calls work.
Speed tests measure throughput — how many megabits per second your connection can push. VoIP does not need throughput. A single phone call uses about 85 Kbps. Your 500 Mbps connection has roughly 5,000 times more bandwidth than one call needs. Even with 50 simultaneous calls, you would be using less than 1% of your available bandwidth.
The problem is not how fast your connection is. The problem is how consistent it is.
What VoIP actually needs
Voice is a real-time application. Audio packets need to arrive at the other end in order, on time, and without gaps. The codec at the receiving end reconstructs audio from these packets in real time. If a packet arrives late, it is useless — the codec has already moved on. If a packet is lost, there is a gap in the audio. If packets arrive with inconsistent timing, the audio sounds choppy or robotic.
This is fundamentally different from downloading a file or loading a web page. Those applications are tolerant of variable delivery — your browser does not care if a chunk of data arrives 200 milliseconds later than the previous chunk. It just waits and assembles the result. VoIP cannot wait. The conversation is happening now.
The metrics that determine VoIP quality are:
Jitter — the variation in packet arrival times. If packets normally arrive every 20 milliseconds but occasionally arrive at 5 ms or 80 ms intervals, that variation is jitter. High jitter forces the receiving device to buffer more aggressively, adding delay, or it causes audio gaps when packets arrive too late for the jitter buffer.
Packet loss — the percentage of packets that never arrive. Even 1% packet loss is audible as clicks, gaps, or choppy audio. At 3-5%, calls become difficult to follow. VoIP uses UDP, which does not retransmit lost packets.
Latency — the one-way delay from sender to receiver. Under 150 ms is acceptable. Over 200 ms and conversations become awkward — people start talking over each other because they do not hear the other person quickly enough.
None of these are measured by a speed test.
The bufferbloat problem
Bufferbloat is the single most common cause of "fast internet, bad calls" and the least understood.
Your router and modem have buffers — memory that temporarily holds packets when the outbound link is congested. In theory, a small buffer smooths out momentary traffic bursts. In practice, manufacturers ship equipment with enormous buffers because bigger buffers prevent packet loss on speed tests, which makes the product look good in reviews.
Here is what happens: your connection is running near capacity — someone is uploading a video, a cloud backup is running, a large file transfer is in progress. Packets start filling the buffer. Instead of signaling congestion (by dropping packets, which TCP would respond to by slowing down), the oversized buffer absorbs everything. Packets sit in the buffer for 200, 500, sometimes 1,000+ milliseconds before being transmitted.
Your VoIP packets are in that buffer too. They arrive at the other end hundreds of milliseconds late. The jitter buffer on the receiving phone cannot compensate for that much delay. The result: choppy audio, long pauses, talking over each other. The speed test still shows 500 Mbps because the speed test does not care about latency.
How to detect bufferbloat
Run a speed test and watch the latency during the test, not just the final throughput number. Most speed test tools now show "loaded" vs. "unloaded" latency. If your unloaded latency is 10 ms but your loaded latency (during the download or upload test) jumps to 200+ ms, you have bufferbloat.
Better yet, skip the speed test entirely and run a VoIP quality test that measures what actually matters: jitter, packet loss, and latency under conditions that simulate real voice traffic.
How to fix bufferbloat
QoS on your router. Proper QoS configuration prioritizes voice traffic over bulk data. Even when the connection is saturated, VoIP packets get through without waiting in the buffer. See QoS: Telling Your Network What Traffic Matters Most for the setup.
SQM (Smart Queue Management). Modern router firmware (OpenWrt, Ubiquiti, pfSense) supports SQM algorithms like fq_codel or CAKE that actively manage buffer sizes. SQM limits the buffer depth, which caps the worst-case latency at the cost of slightly lower peak throughput. For VoIP, this is an excellent tradeoff.
Limit the bandwidth hogs. Schedule cloud backups, large uploads, and software updates for off-hours. If your connection is never saturated, the buffer never fills, and bufferbloat never manifests. This is a workaround, not a fix, but it buys time while you implement proper QoS.
The 10 Mbps connection that sounds better
It is entirely possible — and common — for a 10 Mbps connection with 5 ms jitter and 0.1% packet loss to produce crystal-clear calls while a 1 Gbps connection with 80 ms jitter and 2% packet loss sounds terrible.
This is why dedicated internet access often sounds better than a faster cable connection. DIA provides symmetrical bandwidth with low latency and an SLA for jitter and packet loss. The speed number is lower, but the quality metrics are better. For voice, quality beats quantity every time.
It is also why the afternoon call quality problem is so common. The connection has plenty of bandwidth at 8 AM when only a few people are online. By 2 PM, with the full team working, the shared cable node is congested, buffers are filling, and jitter spikes. The speed test at 2 PM might still show 400 Mbps, but the latency and jitter tell a different story.
How to test what actually matters
Stop running speed tests to diagnose VoIP problems. Speed tests answer the wrong question.
Run a VoIP quality test instead. It measures jitter, packet loss, latency, and MOS score — the metrics that determine whether your calls will sound good. The results will tell you whether your connection is suitable for voice, regardless of how many megabits per second it can push.
Use the bandwidth calculator to determine how much throughput your call volume actually needs. You will likely find that bandwidth is not your bottleneck. The bottleneck is consistency, and that requires different tools to measure and different solutions to fix.
For a detailed explanation of the metrics that matter, see Latency, Jitter, and Packet Loss: The Details. For the connection types that deliver the best VoIP quality, start with Your ISP Is the Foundation Everything Else Sits On.
Frequently Asked Questions
Why do my VoIP calls sound bad when my internet speed test shows fast speeds?+
Speed tests measure throughput — how much data your connection can move per second. VoIP quality depends on consistency: low jitter, low packet loss, and low latency. A connection can have 500 Mbps of throughput and still have enough jitter or packet loss to make voice calls sound terrible. You need a VoIP quality test, not a speed test.
How much bandwidth does a VoIP call actually need?+
A single VoIP call using G.711 needs about 85-100 Kbps in each direction including overhead. Using Opus or G.729, it is even less. Use our bandwidth calculator to estimate throughput for your call volume. Bandwidth is almost never the bottleneck for VoIP. Even a 10 Mbps connection has more than enough throughput for dozens of simultaneous calls. The problem is almost always quality (jitter, loss, latency), not quantity (bandwidth).
What is bufferbloat and how does it affect VoIP?+
Bufferbloat occurs when your router or modem has oversized network buffers that absorb traffic spikes instead of dropping packets. This prevents the congestion signals that TCP uses to slow down, resulting in massive latency spikes — sometimes hundreds of milliseconds — when the connection is under load. VoIP packets caught in these bloated buffers arrive far too late to be useful, causing choppy audio and long delays.
What are acceptable jitter and packet loss numbers for VoIP?+
For good call quality, aim for jitter under 30 ms, packet loss under 1%, and one-way latency under 150 ms. A MOS score of 4.0 or higher indicates good quality. These numbers matter far more than your download or upload speed.
Share
Want to know when we publish new articles? Sign up for updates