Packet Loss Test Guide (2026): Tools, Methods & Fixes

Packet loss describes lost pieces of data traveling through a network, but failing to reach their destination. Packet loss occurs when network traffic is disrupted by congestion, hardware issues, software bugs, and a number of other factors cause dropped packets during data transmission.

Packet loss sits alongside the trio of two other major network performance complications: latency, and jitter.

What is a packet loss test?

A packet loss test is the process of measuring how many data packets fail to reach their intended destination during transmission across a network, during an event like network congestion.

Performed using tools such as Ping, MTR, or iPerf, packet loss testing calculates the packet loss percentage to assess connection quality, diagnose network congestion, and determine whether your internet connection meets performance requirements.

• Packet loss occurs when data packets fail during data transmission across a network
• A packet loss test measures reliability, latency, and connection quality
• Common tools include Ping, iPerf, MTR, Traceroute, and Wireshark
• 1–2% packet loss begins to impact performance; above 5% is critical
• Manual tools suit ad hoc diagnostics; enterprise environments require continuous monitoring platforms

Find out more: Download our comprehensive guide

What is Network Packet Loss?

Packet loss test tools & methods: Comparison

Choosing the right tool depends on your environment, technical skill level, and whether you need a one-off snapshot or ongoing visibility. The table below compares the most widely used free and open-source methods for measuring network packet loss:

Pricing & budget considerations

For teams working within a constrained budget, the good news is that the most widely used diagnostic tools, including Ping, Traceroute, MTR, and iPerf, are free and available on virtually every operating system. Wireshark is also free and open-source, though it requires significant expertise to interpret results effectively.

Commercial network monitoring tools such as SolarWinds NPM and PRTG start at several hundred dollars per year and scale with the size of your network infrastructure.

Enterprise observability platforms designed for multi-vendor environments carry higher price points but deliver proportionally greater value through automation, SLA tracking, and cross-system analytics.

How to Run a Command-Line Packet Loss Test (Ping & Traceroute)

The Ping test remains the fastest way to perform a basic packet loss test on any device:

• Open a command prompt or terminal
• Windows: ping -n 100 1.1.1.1 | macOS/Linux: ping -c 100 1.1.1.1
• Review the summary — packets sent vs. received reveals your loss percentage
• Use tracert (Windows) or traceroute (macOS/Linux) to identify which specific hop is dropping packets

Expert insight:

"A single ping test tells you something is wrong, but it doesn't tell you where or why. Combining Ping with Traceroute and MTR gives you directional context. But for enterprise environments, where packet loss directly impacts payments and unified communications, you need continuous monitoring with historical data - not a command you run when a user complains." IR tech support team

Technical analysis: How packet loss is measured

When packet loss occurs, the cause is rarely isolated to a single point.

Network packet loss is typically the result of interplay between several factors: congestion at buffer overflow points, physical layer errors on wireless networks or faulty cables, mismatched QoS settings that deprioritise critical traffic, and TCP retransmissions that compound latency under load.

Measuring packet loss accurately means capturing more than a simple lost/received count. The full picture includes network performance metrics such as round-trip latency, jitter, TCP retransmission rates, and MOS scores for voice traffic. Each of these tells a different part of the story.

Packet loss metrics & thresholds

Use the thresholds below as a benchmark when interpreting test results:

These thresholds are especially relevant for real-time applications. Video streaming can tolerate slightly higher loss through buffering strategies, but voice and video calls have no such buffer. In fact, packet loss above 2% is immediately perceptible to users.

Free Options: Capabilities and Limitations

Free command-line tools are powerful for point-in-time diagnosis but fall short for enterprise-grade visibility:

• Ping and Traceroute: Available natively on all platforms. Ideal for first-line troubleshooting
• MTR: Combines both into a continuous, hop-by-hop view. Excellent for ISP or WAN path analysis
• iPerf: Tests maximum throughput and identifies congestion-driven packet loss. Requires both client and server endpoints
• Wireshark: The gold standard for deep TCP/IP inspection. Essential for diagnosing intermittent or application-layer drops

The core limitation of almost all free tools is that they are reactive and manual. They can help you fix packet loss after it has been reported but cannot alert you proactively, track trends over time, or correlate network issues with business outcomes such as failed payment transactions or degraded contact center performance.

How is packet loss related to latency and jitter?

Packet loss, latency, and jitter are the three pillars of internet quality assessment, and they're deeply interconnected.

High latency often signals that routers are buffering packets under congestion; when those buffers overflow, packets are discarded, creating loss.

Jitter is the variation in packet arrival timing, and causes receiving applications to either discard out-of-order packets or wait longer, increasing effective latency.

For VoIP and video calls, this relationship is particularly damaging. A jittery, high-latency connection doesn't just feel slow - it actively generates packet loss at the application layer, even when the underlying network reports moderate figures.

This is why monitoring all three metrics simultaneously, and setting independent thresholds for each, is essential for accurate network health assessment.

Network monitoring software: Proactive packet loss visibility

Continuous monitoring platforms go beyond measuring packet loss. They contextualise it against application performance, historical baselines, and business-critical workflows. The table below compares the leading solutions:

The key differentiator between manual network monitoring tools and enterprise observability platforms is scope.

Tools like SolarWinds and PRTG excel at infrastructure-level polling, but they do not natively understand the downstream impact of network degradation on unified communications, contact centre performance, or payment processing pipelines.

Management & workflow features

Collaboration capabilities

Enterprise monitoring platforms support cross-team visibility, enabling network, UC, and application teams to share a single pane of glass.

Shared dashboards and role-based alert routing ensure that when packet loss occurs, the right team is notified with the right context, without requiring manual ticket escalation.

Integration ecosystems

Modern observability solutions integrate directly with UC platforms (Microsoft Teams, Cisco, Avaya), payment infrastructure, CRM systems, and IT service management tools via API-based data ingestion.

This means a spike in packet loss on a WAN link can be automatically correlated with a surge in payment failures or a drop in contact center call quality, giving operations teams the context they need to prioritize remediation.

Decision framework: Choosing the right packet loss tool

Not every environment needs the same approach. Use the framework below to match your scale and requirements to the appropriate tool or platform:

The decision point between manual and continuous monitoring typically sits at the intersection of scale and business risk.

If packet loss on your network can result in SLA breaches, revenue loss, or customer-facing service degradation, manual tools are insufficient, regardless of network size.

Improve network visibility with IR

IR Collaborate delivers enterprise-grade network observability purpose-built for environments where performance and reliability directly affect revenue. With multi-vendor visibility across UC platforms, contact centre infrastructure, and payment systems, IR moves organisations beyond reactive troubleshooting into proactive, data-driven network performance management.

Expert insight:

"Most organizations discover they have a packet loss problem when a user complains - or worse, when a transaction fails. Real-time observability means you know about degradation the moment it begins, with enough context to act before it becomes a business incident." IR tech team

Download IR's definitive guide to network performance metrics for enterprise teams

Optimizing Your Network: A Complete Guide to Understanding Jitter, Latency and Packet Loss

Frequently Asked Questions

Q. What is an acceptable percentage for packets lost?

A. For most applications, packet loss below 1% is considered acceptable. Loss of 1–2.5% begins to degrade performance for real-time traffic like VoIP and video streaming. Anything above 5% is critical, meaning expect dropped calls, buffering, payment timeouts, and significant degradation across all application types.

Q. How do I run a packet loss test using ping?

A. Open a command prompt and run: ping -n 100 1.1.1.1 (Windows) or ping -c 100 1.1.1.1 (macOS/Linux). At the end of the test, the summary will show packets sent, received, and lost. The difference is your loss percentage. For intermittent issues, increase the count to 500 or 1,000 packets.

Q. What causes packet loss in a network?

A. Common causes include network congestion (too much traffic overwhelming buffers), faulty hardware, wireless interference on Wi-Fi networks, misconfigured QoS settings, outdated firmware, and problems at a specific router hop. Packet loss can also be server-side or caused by ISP-level issues beyond your local network infrastructure.

Q. How does packet loss affect video calls?

A. Video calls are highly sensitive to packet loss because they rely on real-time data transmission with no opportunity to retransmit lost frames. Even 1–2% loss can cause pixelation, frozen screens, and choppy audio. Above 5%, video conferencing typically becomes unusable. VoIP and unified communications platforms are similarly affected.

Q. What tools can measure packet loss in real time?

A. MTR provides continuous hop-by-hop statistics. iPerf can simulate load and measure loss under congestion. For production environments, network monitoring tools such as SolarWinds NPM, PRTG, and IR Collaborate offer real-time dashboards, automated alerts, and historical data, enabling teams to detect and respond to packet loss before it impacts users or SLAs.

Q. How is packet loss related to latency and jitter?

A. Packet loss, latency, and jitter are interconnected network performance metrics. High network congestion increases latency, which can trigger timeout-based retransmissions, effectively causing packet loss. Jitter (variation in packet arrival time) forces buffers to compensate, and when buffers overflow, packets are dropped. Measuring all three together gives a complete picture of connection quality.

Q. Can packet loss occur on a wired connection?

A. Yes. While wireless networks are more prone to interference-related packet loss, wired connections are not immune. Faulty cables, failing switch ports, duplex mismatches, and congested uplinks can all cause data packets to be dropped on Ethernet infrastructure. If packet loss persists after eliminating WiFi as a variable, investigate physical layer and switch-port statistics.

Q. When should I use a monitoring platform instead of manual testing tools?

A. Manual command-line tools like Ping and iPerf are ideal for ad hoc diagnostics. However, if you need to maintain consistent internet quality across a multi-site enterprise, ensure SLA compliance, detect packet loss before users report it, or correlate network issues with application performance (e.g., payments failures, UC disruptions), a continuous monitoring platform is essential.