What Causes Packet Loss? Common Network Faults

A video call freezes just as you need to speak. An online game reports a hit that never registered. A cloud application takes far longer to save than it should. These are familiar symptoms, but what causes packet loss is not always obvious from the device in front of you.

Internet traffic is sent in small units of data called packets. For a page, call, stream or file transfer to work properly, those packets need to arrive at their destination in the right order and within a useful timeframe. When some do not arrive, arrive too late, or cannot be processed, packet loss occurs. A small, occasional loss may go unnoticed. Sustained loss can make a fast connection feel unreliable.

The right fix depends on where the packets are being lost: inside your home or office, on the local connection, or further along the route to the service you are using. That distinction matters. Rebooting a router may help with a local fault, but it will not resolve congestion on a distant server.

Packet loss has several potential causes, and more than one can be present at the same time. The most common are Wi-Fi interference, overloaded equipment, damaged or poorly fitted cabling, network congestion, software or configuration issues, and faults outside the local network.

A useful first question is whether the issue affects one device, every device, or only one activity. If a single laptop drops packets over Wi-Fi while a wired desktop remains stable, the internet connection itself is unlikely to be the root cause. If every device struggles at the same time, investigate the router, fibre termination, local network load or provider connection.

Wi-Fi is convenient, but it uses radio signals that have to travel through walls, floors, furniture and other electronic devices. Distance from the router reduces signal quality. Dense walls, underfloor heating, metal surfaces and kitchen appliances can make the effect more pronounced.

In flats and busy office buildings, neighbouring wireless networks may also compete for the same radio channels. The result is retransmission: a device sends a packet, does not receive confirmation, and sends it again. That can look like packet loss, higher latency or sudden dips in speed.

The 2.4 GHz band generally reaches further but is often more crowded. The 5 GHz band usually offers greater capacity and less interference at shorter range. Newer Wi-Fi standards can improve performance, but they cannot overcome poor router placement or a weak signal at the far end of a building.

Place the router in an open, central position where practical, rather than in a cupboard, behind a television or on the floor. For larger homes and workplaces, a properly planned mesh Wi-Fi system or wired access points are often a better answer than simply buying a more powerful router.

Every router, switch, access point and firewall has a practical limit. When too many devices or high-demand services compete at once, packets may be queued for too long or discarded. This is especially noticeable during video meetings, cloud backups, large uploads, online gaming and high-resolution streaming.

The connection speed shown on a broadband package is only part of the picture. Upload capacity matters for video calls and backups. Router processing power matters when multiple users are active. In a business setting, firewall inspection, VPN traffic and voice services can add further load.

Congestion may occur inside a building or beyond it. A busy local Wi-Fi network can be saturated even when the fibre connection has ample capacity. Conversely, a household or business may have excellent internal networking but use all available upload bandwidth during a backup job.

Traffic prioritisation can help where it is configured carefully. Voice and video packets are highly sensitive to delay, while a software update can tolerate waiting. However, prioritisation is not a substitute for sufficient capacity. If the line or router is regularly at its limit, reducing background traffic or upgrading the relevant equipment and connection is the more durable solution.

Wired connections are usually more stable than Wi-Fi, but they are not immune to faults. A bent cable, damaged connector, loose plug or failing switch port can produce intermittent packet loss that is difficult to spot. A cable may still appear to work while negotiating at a lower speed or generating errors under load.

Start with the simple checks: reseat both ends of the cable, inspect it for visible damage and test with a known-good cable. Move the device to another switch or router port if one is available. In offices, do not overlook patch panels, wall sockets and powerline adapters. Each extra connection is another possible point of failure.

For latency-sensitive devices such as desk phones, conferencing systems, gaming PCs and servers, a direct Ethernet connection is generally the most predictable option. It removes the variability of radio interference and gives you a clearer basis for troubleshooting.

Consumer and business routers run continuously, often handling dozens of connections at once. Over time, an outdated firmware version, memory issue, overheating problem or failing power supply can affect performance. A restart can clear a temporary condition, but repeated packet loss after restarts deserves closer investigation.

Check that router firmware is current and that the device has ventilation. Avoid connecting critical equipment through unreliable extension leads. If the router is many years old, it may struggle with modern connection speeds, newer Wi-Fi standards or a busy home full of smart devices.

The end device can be responsible too. An old network driver, aggressive power-saving setting, VPN client or security application can interrupt traffic. Test another device on the same connection. If packet loss follows one computer but not another, update its network driver and review its local software before changing the network.

Business networks have more moving parts: managed switches, separate staff and guest Wi-Fi networks, cloud telephony, VPNs, firewalls and multiple access points. That flexibility is valuable, but incorrect configuration can create loss or instability.

A duplex mismatch, incorrectly configured VLAN, loop in the network, poor access-point roaming settings or firewall rule that overloads inspection can affect performance. Voice services are particularly revealing because even brief loss can create clipped audio, robotic speech or dropped calls.

These issues should be investigated methodically. Record when the loss occurs, which applications are affected, whether it impacts wired and wireless users, and whether it coincides with backups, scheduled updates or office occupancy. Meaningful evidence helps identify a pattern faster than a general report that “the internet is slow”.

Not all packet loss begins at your router. Packets travel through several networks before reaching a website, game server, cloud platform or remote office. A fault or overloaded route elsewhere can affect a specific destination while general browsing remains normal.

This is why one service can perform badly while another works perfectly. A video platform may select a distant or busy server. A company VPN may route all traffic through headquarters. A game server may be under exceptional load. In these cases, changing local Wi-Fi settings may improve nothing.

There is also an important technical caveat: some network devices deliberately deprioritise or ignore diagnostic test traffic. A test may show apparent packet loss at an intermediate point even though normal traffic continues successfully. The meaningful result is loss that persists to the final destination and matches a real user-facing problem.

Begin by narrowing the scope. Test a device connected directly to the router with Ethernet, then compare it with the same activity over Wi-Fi. If the wired result is stable but Wi-Fi is not, focus on coverage, interference and wireless capacity.

Next, test at different times. Loss only during evenings, peak office hours or large uploads points towards contention or local saturation. Loss that appears randomly across all devices may point to hardware, cabling or a line issue.

For businesses, monitor latency, packet loss and interface errors over time rather than relying on a single speed test. A speed test can show strong throughput during a brief window while calls still suffer from intermittent loss. For households, a simple comparison between a wired laptop and wireless devices is often enough to reveal the direction of the fault.

Keep a short record with the date, time, device type, connection method and affected service. Include screenshots or test results where available. This makes support conversations more efficient and helps separate a local issue from a wider network event.

Start with the least disruptive changes. Restart the router once, update its firmware, check cables and move important devices onto Ethernet. Then improve Wi-Fi placement or add suitable coverage where weak signal is the pattern. Pause large uploads and cloud synchronisation while testing video calls or gaming.

For a workplace, review whether voice traffic, guest Wi-Fi, backups and core business systems are all competing on the same equipment without appropriate capacity or segmentation. The best setup is not necessarily the most complex one. It is the one designed around the number of users, the building layout and the applications that cannot tolerate interruption.

If loss continues across wired devices and multiple services after these checks, contact your provider with your observations. A local operator with control over its infrastructure can assess the connection path, equipment and service data without sending you through a scripted loop. Visual Online’s in-house teams can help customers in Luxembourg work through the evidence until the source of the problem is clear.

Packet loss is not something to accept as the price of being online. Treat it as a signal: check the connection closest to you first, measure the pattern, and make the next change based on what the network is actually telling you.