Packet Loss Test

A packet loss test checks how many requests or packets fail to reach a destination and return. This browser tool uses repeated HTTPS requests, while command-line tools normally use ICMP echo requests.

Zero is the target for gaming, voice calls and video meetings. A single failed request should be retested because short browser samples can be affected by temporary Wi‑Fi interference, routing changes or device activity.

Packet loss can cause online games to rubber-band or ignore inputs, video calls to freeze, voice chat to sound broken, streams to reduce quality and remote desktop sessions to disconnect. File downloads may simply slow down because missing data has to be requested again.

Common causes include weak or congested Wi‑Fi, upload saturation, faulty Ethernet cables, overloaded or ageing routers, powerline adapters, software or firmware problems and congestion within the broadband provider’s network. Compare Wi‑Fi with Ethernet to narrow down where the loss begins.

It can be. High ping adds delay, while packet loss can remove updates completely. That may cause rejected inputs, rubber-banding, missing voice audio or sudden reconnections even when the average ping looks acceptable.

Games, voice calls and live video need data to arrive quickly. A late or missing update may be useless, so loss appears as missing audio, frozen video or rubber-banding. File downloads normally detect missing data and resend it, which usually slows the transfer instead.

Yes. Reliable transfers may resend missing data and reduce their sending rate, lowering effective throughput even when the broadband package’s headline speed has not changed. Real-time applications may show glitches rather than waiting for every missing update.

Run both when possible. A clear Ethernet result with a poor Wi‑Fi result points towards interference, weak signal, roaming or local wireless congestion. Repeated loss over Ethernet is stronger evidence of a router, cable or provider-line issue.

Results vary with Wi‑Fi conditions, household traffic, VPN use, device load, routing and provider congestion. Repeat the test at least twice and compare different times before drawing a conclusion.

Short tests can miss intermittent problems that happen only every few minutes. Repeat the browser test at different times and use a longer command-line ping when the issue is occasional or appears only during busy periods.

A VPN may help when the loss is caused by a poor or congested route and the VPN sends traffic along a different path. It will not repair weak Wi‑Fi, a damaged cable, a faulty router or a broadband-line problem. Test with the VPN disconnected first.

Zero loss is the normal target for a short home broadband test, particularly for gaming and calls. No internet connection can guarantee that a packet will never be lost indefinitely, so repeat the test before treating one failed request as proof of a persistent fault.

Run ping 8.8.8.8 -t in Command Prompt, allow it to run for around 30 seconds, then press Ctrl+C to see the sent, received and lost packet totals.

Test over Ethernet, pause uploads, restart the router, check cables and adapters, improve Wi‑Fi signal and compare daytime with evening results. Contact the provider when repeated wired tests continue to show loss.

This test helps you measure failed requests and identify likely causes. For a deeper explanation of how packet loss works and why it affects gaming, calls and streaming, read the full What Is Packet Loss guide.