Congestion, Latency, Jitter, Packet Loss, and Application Performance Clues
Key Takeaways
- Performance troubleshooting separates bandwidth limits, latency, jitter, packet loss, server delay, and application behavior.
- Congestion appears as queue growth, drops, retransmissions, rising latency, and degraded voice or video quality.
- Latency is delay, jitter is variation in delay, and packet loss is missing traffic that may trigger retransmission or quality loss.
- Application symptoms can come from DNS, TLS, authentication, database delay, server CPU, storage, or dependency failures.
- Baselines and comparison tests help distinguish normal load from new performance problems.
Performance Troubleshooting
Slow is not one problem. A slow application may be caused by congested WAN bandwidth, packet loss on Wi-Fi, high latency to a cloud region, DNS delay, TLS negotiation problems, overloaded servers, database locks, storage latency, or an authentication dependency. Network+ expects you to use clues instead of guessing.
Key Performance Terms
| Term | Meaning | Common impact |
|---|---|---|
| Bandwidth | Maximum theoretical or provisioned capacity | Large transfers and aggregate load |
| Throughput | Actual delivered data rate | User-perceived transfer speed |
| Latency | Time for traffic to travel and be processed | Interactive apps feel delayed |
| Jitter | Variation in latency | Voice and video become choppy |
| Packet loss | Packets do not arrive | TCP retransmits, UDP quality drops |
| Congestion | Demand exceeds available forwarding capacity | Queues, drops, delay, and retransmits |
High bandwidth does not guarantee low latency. A satellite or distant cloud path can have plenty of bandwidth and still feel delayed for interactive sessions.
Congestion and Packet Loss Clues
| Evidence | Interpretation |
|---|---|
| Interface output discards rise during peak hours | Egress congestion or queue drops |
| TCP retransmissions increase | Packet loss, errors, or congestion affecting TCP |
| Voice has choppy audio | Jitter, loss, Wi-Fi retries, or QoS issue |
| Video quality drops during backups | Competing traffic and insufficient QoS or capacity |
| Ping latency rises only under load | Queue buildup or buffer pressure |
| Errors and CRC counters rise | Physical issue, not just congestion |
Congestion is often time-based. Compare busy periods to quiet periods. A circuit that works at 7 a.m. and fails at 10 a.m. may be oversubscribed or missing QoS for critical applications.
Latency and Jitter
Latency affects round-trip conversations such as remote desktop, database calls, voice signaling, and chatty applications. Jitter affects real-time streams because packets arrive at uneven intervals. Buffering can hide some jitter, but too much buffering adds delay.
| Application type | Sensitive to |
|---|---|
| Voice over IP | Jitter, packet loss, latency, QoS marking |
| Video meetings | Bandwidth, jitter, loss, Wi-Fi quality |
| Remote desktop | Latency, packet loss, server load |
| File transfer | Throughput, loss, window scaling, congestion |
| Database application | Latency, server processing, query behavior |
Application Performance Clues
Not every slow report is caused by the network path. The network may deliver packets quickly while the application waits on authentication, database queries, third-party APIs, storage, or server CPU.
| Symptom | Possible non-network cause |
|---|---|
| Page stalls before connecting | DNS or TCP/TLS setup delay |
| Login slow but pages fast after login | Identity provider, MFA, or directory delay |
| One report is slow for everyone | Database query, lock, or application code |
| Uploads slow only from one office | WAN congestion, firewall inspection, or ISP path |
| App slow from all locations | Server, cloud service, or shared backend dependency |
Use packet captures and timing carefully. A fast TCP handshake followed by a long server response time points higher in the stack. Retransmissions and duplicate acknowledgments point back toward loss or congestion.
Baselines and Comparisons
Performance troubleshooting is stronger when you know normal. Baselines include interface utilization, error rates, latency to major sites, DNS response time, wireless retry rate, CPU and memory on network devices, firewall session counts, and application response time.
| Comparison | Why it helps |
|---|---|
| Affected versus unaffected user | Narrows client, VLAN, AP, or access switch |
| Wired versus wireless | Separates RF from application or WAN |
| Same app by IP versus name | Separates DNS from transport and application |
| Peak versus off-peak | Identifies congestion patterns |
| Local app versus cloud app | Separates LAN and WAN/cloud paths |
Exam Focus
For N10-009, latency is delay, jitter is delay variation, packet loss is missing packets, and congestion is capacity pressure that can cause delay and drops. Application clues matter: if the network path is clean but server response time is high, avoid blaming cabling or VLANs.
Voice calls become choppy during peak usage, and monitoring shows variable delay but little change in average bandwidth. Which metric best describes the voice problem?
A packet capture shows a quick TCP handshake to a web application, followed by a long delay before the server sends the HTTP response. What does this most strongly suggest?
Which evidence can indicate congestion or loss? Select three.
Select all that apply