ADAM PULSE Latency vs jitter vs packet loss: what is actually hurting your network?
Your business has a fast internet connection.
The speed test says 500 Mbps.
The circuit is online.
Yet users still experience:
- Frozen Zoom video
- Delayed conversations
- Choppy VoIP
- Remote desktop lag
- Slow cloud applications
- Intermittent pauses
- Failed connections
The problem may have very little to do with bandwidth.
Three other network measurements often have a much greater effect on real time application quality:
Latency
Jitter
Packet loss
Understanding the difference between them can dramatically improve network troubleshooting.
What Is the Difference Between Latency, Jitter, and Packet Loss?
In simple terms:
Latency measures delay.
Jitter measures inconsistency in delay.
Packet loss measures data that never arrives.
All three affect the user experience differently.
| Metric | What It Measures | Typical Symptom | | —- | —- | —- | | Latency | How long packets take to travel | Delay | | Jitter | How much packet timing varies | Choppy or inconsistent performance | | Packet Loss | How many packets never arrive | Freezing, missing audio, retransmissions | | Bandwidth | How much data can be transferred | Capacity limitations |
Understanding which measurement is deteriorating helps determine where to investigate next.
What Is Network Latency?
Latency is the delay between sending network traffic and receiving a response.
It is commonly measured in milliseconds.
For round trip measurements, the timer begins when traffic leaves the source and ends when the response returns.
Cisco defines network latency as the delay experienced as data travels through a network and commonly measures it using round trip time.
What Does High Latency Feel Like?
High latency typically feels like delay.
Examples include:
- Someone speaks on a video call and the response arrives noticeably later
- Remote desktop feels sluggish
- Cloud applications respond slowly
- Web transactions hesitate
- VoIP callers begin talking over one another
The connection can have plenty of bandwidth and still suffer from excessive latency.
What Causes High Latency?
Possible causes include:
- Geographic distance
- Network congestion
- Queuing
- Inefficient routing
- VPN paths
- Firewall processing
- ISP routing
- SD WAN path selection
- Overloaded equipment
- Wireless conditions
- Application architecture
The troubleshooting question should be:
Where is the delay being introduced?
Is All Latency Bad?
No.
Every network has latency.
Traffic takes time to travel through cables, fiber, wireless systems, routers, firewalls, provider networks, and application infrastructure.
Geographic distance alone creates unavoidable delay.
The more useful question is:
Is the current latency normal for this network and application?
That is why baselines matter.
Cisco provides different expected round trip ranges depending on network type and notes that geographic distance can increase RTT.
What Is Network Jitter?
Jitter is variation in packet delay.
Imagine sending packets every few milliseconds.
If they arrive at regular intervals, timing is predictable.
If they arrive irregularly, timing becomes inconsistent.
That variation is jitter.
Cisco describes jitter as variation in delay over time and notes that excessive jitter can significantly degrade voice quality.
What Does High Jitter Feel Like?
Jitter is especially noticeable in real time applications.
Symptoms can include:
- Choppy audio
- Robotic voice
- Video freezing
- Delayed audio
- Inconsistent conversations
- Poor conferencing quality
Unlike an email or file download, real time communications cannot simply wait indefinitely for delayed packets.
Timing matters.
What Causes Jitter?
Common causes include:
- Network congestion
- Queuing
- Changing network paths
- WiFi interference
- Traffic bursts
- WAN instability
- Firewall processing
- SD WAN path changes
- Provider congestion
Any condition that causes packet delivery time to vary significantly can increase jitter.
What Is a Jitter Buffer?
Voice and video applications can use buffering to compensate for variation in packet arrival.
The buffer temporarily holds packets so they can be played in a more consistent sequence.
But buffers involve a tradeoff.
More buffering may help smooth jitter.
Too much buffering can increase overall delay.
Cisco notes that very high jitter can be particularly disruptive because increasing the jitter buffer to compensate also increases conversational delay.
What Is Packet Loss?
Packet loss occurs when packets fail to reach their intended destination.
Packets can be lost because of:
- Congestion
- Buffer exhaustion
- Interface problems
- Hardware failures
- Wireless interference
- ISP problems
- Routing conditions
- Resource constraints
- Configuration problems
Cisco notes that packet drops can reduce throughput, cause retransmissions, and disrupt application reliability.
What Does Packet Loss Feel Like?
Symptoms include:
- Missing audio
- Frozen video
- Stuttering
- Application timeouts
- Slow transfers
- VPN instability
- Failed transactions
- Retransmissions
The effect depends heavily on the application.
A file transfer may simply retransmit missing data.
A live conversation cannot go backward and replay a missing word without affecting the experience.
Which Is Worse: Latency, Jitter, or Packet Loss?
There is no universal answer.
It depends on the application and severity.
A file transfer may tolerate moderate latency but suffer significantly from repeated packet loss.
VoIP and video conferencing can be extremely sensitive to jitter, latency, and loss.
Remote desktop users may notice latency immediately.
Cloud applications may suffer from retransmissions and connection delays.
The important point is:
Do not troubleshoot these measurements independently of the application experience.
How Do Latency, Jitter, and Packet Loss Affect Zoom?
Zoom explicitly monitors network statistics including:
- Latency
- Jitter
- Packet loss
Zoom uses these parameters, along with other factors, when evaluating perceived audio and video quality through Mean Opinion Score.
Zoom administrators can also access latency, jitter, and packet loss statistics for audio, video, and screen sharing.
This is important because it reinforces a central networking principle:
A fast bandwidth test does not automatically mean a Zoom connection is healthy.
How Do Latency, Jitter, and Packet Loss Affect VoIP?
Voice is highly sensitive to network timing.
High latency can create conversational delay.
High jitter can cause inconsistent audio arrival.
Packet loss can make portions of speech disappear.
Cisco specifically identifies delay, jitter, and packet loss as key measurements for voice enabled networks.
How Do These Metrics Affect SD WAN?
SD WAN systems can evaluate path quality when deciding which connection should carry application traffic.
Cisco SD WAN troubleshooting tools expose tunnel statistics for traffic loss, latency, and jitter and provide historical tunnel health views for investigating performance.
This is another reason businesses with multiple WAN connections should monitor more than simple up or down status.
Both circuits can be technically online while one provides dramatically worse application performance.
Can a Network Be Up but Unhealthy?
Absolutely.
Consider:
Circuit availability: Up
Bandwidth: 500 Mbps
Latency: Elevated
Jitter: High
Packet loss: 6 percent
Is the connection online?
Yes.
Is it healthy?
Probably not for many business applications.
This is why:
Uptime Is Not Network Health
Availability is only one part of performance.
A useful monitoring strategy should evaluate the quality of the network connection as well as whether it responds.
How Do You Measure Latency?
Ping is a common starting point.
It can provide round trip timing information between a source and destination.
But one ping measurement is only a snapshot.
Repeated measurements and historical monitoring provide much greater context.
How Do You Measure Jitter?
Jitter requires comparing packet timing over multiple measurements.
Applications and monitoring tools can calculate the variation in delay.
Zoom, for example, exposes jitter statistics in its client and administrative quality data.
How Do You Measure Packet Loss?
Packet loss is generally expressed as a percentage.
For example:
Packets sent: 1,000
Packets received: 980
Packets lost: 20
Packet loss: 2 percent
But the percentage alone does not tell you where the loss occurred.
Use multiple test points to isolate the failure domain.
Why Does My Speed Test Look Good When Zoom Is Bad?
Because a speed test and a Zoom meeting are measuring different aspects of your connection.
A speed test may demonstrate excellent throughput.
Zoom still depends on consistent packet delivery.
If latency spikes, jitter increases, or packets disappear, the real time experience can deteriorate.
Zoom’s own quality measurements reflect this by evaluating latency, jitter, packet loss, and other factors rather than relying solely on bandwidth.
Why Does My VoIP Sound Bad Even with Gigabit Internet?
Gigabit bandwidth does not eliminate:
- Jitter
- Packet loss
- Latency
- Congestion
- WiFi interference
- Firewall issues
- Routing problems
Bandwidth and quality are separate concepts.
More capacity may solve congestion caused by insufficient bandwidth.
It will not fix every network problem.
How Do You Know Which Metric Is Causing the Problem?
Correlate network measurements with the time users experience problems.
For example:
Scenario A
Latency rises dramatically.
Packet loss remains near zero.
Users report noticeable delay.
Investigate latency.
Scenario B
Latency remains reasonable.
Jitter spikes.
VoIP becomes choppy.
Investigate the source of timing variation.
Scenario C
Packet loss increases.
Zoom video begins freezing.
Investigate where packets are being dropped.
The more measurements you correlate, the easier fault isolation becomes.
Why Do Historical Measurements Matter?
Because network problems rarely cooperate with troubleshooting schedules.
An incident might occur at 11:14 AM and disappear by 11:20 AM.
A technician begins testing at 11:35 AM.
Everything looks normal.
Without history, the troubleshooting team knows almost nothing about what happened during those six minutes.
Continuous monitoring changes that.
What Is a Network Performance Baseline?
A baseline describes normal network behavior.
For example:
Typical latency: 22 ms
Typical packet loss: negligible
Typical jitter: low and stable
Normal availability: consistent
Now imagine latency suddenly rises to 190 ms.
That change is meaningful because you know what normal looks like.
Without a baseline, 190 ms is simply a number.
Why Is Trend Monitoring Important?
Individual threshold alerts are useful.
Trends can reveal deterioration before a complete failure.
For example:
Monday: 20 ms average latency
Tuesday: 24 ms
Wednesday: 32 ms
Thursday: 48 ms
Friday: 70 ms
The circuit may still be online.
But something is changing.
Trend visibility allows teams to investigate degradation rather than waiting for a total outage.
What Should Businesses Monitor?
Depending on the environment, important measurements can include:
- Availability
- Latency
- Jitter
- Packet loss
- Gateway availability
- Firewall availability
- WAN circuit status
- SLA performance
- Route behavior
- Application quality
For multi site organizations, these measurements become even more valuable when they can be compared across locations and carriers.
The ADAM Pulse Approach
ADAM Pulse is built around more than:
Is the device up or down?
The more valuable questions are:
How healthy is the connection?
What is normal for this location?
Has latency changed?
Is packet loss occurring?
Is performance deteriorating?
Is the firewall reachable?
Is the gateway reachable?
Is the carrier responding?
Has this happened before?
Does the evidence point toward the ISP, firewall, or local network?
From Network Metrics to Business Impact
IT teams should not collect measurements simply because they can.
Metrics need to answer operational questions.
Latency matters because applications become slow.
Jitter matters because conversations become inconsistent.
Packet loss matters because information disappears.
Historical data matters because intermittent problems vanish before technicians can investigate.
That is where network monitoring becomes network intelligence.
Stop Measuring Only Speed
The question:
How fast is our internet?
is important.
But businesses should also ask:
How reliable is it?
How consistent is it?
How healthy is it throughout the day?
Does it meet the needs of Zoom, VoIP, cloud applications, VPNs, and remote users?
What happened during yesterday's outage?
ADAM Pulse provides managed network monitoring designed to help organizations understand availability, latency, packet loss, SLA performance, and recurring network behavior across their locations and internet circuits.
Bandwidth tells you how much traffic the road can carry.
Latency, jitter, and packet loss tell you how well the journey is actually going.
Learn more about ADAM Pulse and talk with USA Telecom about monitoring the quality of your network, not just whether it is online.
Frequently asked questions
What Is the Difference Between Latency, Jitter, and Packet Loss?
In simple terms: All three affect the user experience differently. Understanding which measurement is deteriorating helps determine where to investigate next.
What Is Network Latency?
Latency is the delay between sending network traffic and receiving a response. It is commonly measured in milliseconds. For round trip measurements, the timer begins when traffic leaves the source and ends when the response returns.
What Does High Latency Feel Like?
High latency typically feels like delay. Examples include: The connection can have plenty of bandwidth and still suffer from excessive latency.
Is All Latency Bad?
No. Every network has latency. Traffic takes time to travel through cables, fiber, wireless systems, routers, firewalls, provider networks, and application infrastructure.
What Is Network Jitter?
Jitter is variation in packet delay. Imagine sending packets every few milliseconds. If they arrive at regular intervals, timing is predictable.
What Does High Jitter Feel Like?
Jitter is especially noticeable in real time applications. Symptoms can include: Unlike an email or file download, real time communications cannot simply wait indefinitely for delayed packets.
What Causes Jitter?
Common causes include: Any condition that causes packet delivery time to vary significantly can increase jitter.
What Is a Jitter Buffer?
Voice and video applications can use buffering to compensate for variation in packet arrival. The buffer temporarily holds packets so they can be played in a more consistent sequence. But buffers involve a tradeoff.
What Is Packet Loss?
Packet loss occurs when packets fail to reach their intended destination. Packets can be lost because of: Cisco notes that packet drops can reduce throughput, cause retransmissions, and disrupt application reliability.
What Does Packet Loss Feel Like?
Symptoms include: The effect depends heavily on the application. A file transfer may simply retransmit missing data.
Sources
- Cisco — Understanding Jitter in Packet Voice Networks. Delay, jitter and packet loss as the determinants of voice quality.
- Cisco — What Is Network Latency? Definition, causes and the distinction between latency and bandwidth.
- Cisco — Troubleshoot Packet Drops. Congestion, buffer exhaustion and interface errors as drop causes, and their effect on throughput and retransmission.
- Zoom — Using the Zoom Dashboard. Administrator access to per-meeting latency, jitter and packet loss.
Network symptoms should be interpreted in context. A single test from a single location at a single moment rarely proves where a fault sits — correlate against history, test from more than one point, and preserve evidence before changing configuration.
USA Telecom Consulting LLC is a Service-Disabled Veteran-Owned Small Business running a 24/7 NOC. We monitor networks, circuits and firewalls for regulated and defense-supply-chain organizations.
Why is my network slow even though the speed test is fast? · Is it the ISP or the firewall? · Ping vs traceroute vs MTR · How to troubleshoot packet loss · What should businesses actually monitor? · Why does Zoom keep freezing? · What causes network jitter? · Troubleshooting high network latency