Skip to content

Wi-Fi Keeps Dropping? How to Fix Unstable Wireless

From channel congestion to bad drivers — diagnose what's actually killing your connection.

Is it Wi-Fi or your internet?

Before you blame the router, find out whether the problem is the wireless link between your device and the router, or the connection between the router and your ISP. They feel identical from the couch — pages stop loading, video freezes — but the fixes are completely different.

The fastest test: plug a laptop directly into the router with an Ethernet cable and use it for an hour. If the wired connection is rock solid while wireless devices keep dropping, the problem is Wi-Fi. If the wired connection drops too, the problem is upstream — your modem, the line, or the ISP itself.

For a real-time view of drops as they happen, open a terminal and run a continuous ping to a reliable target. On Windows use ping 1.1.1.1 -t; on macOS or Linux use ping 1.1.1.1. Leave it running. Every "Request timed out" is a moment your connection dropped. You can also run the Ping tool here for a quick check from this server.

Check signal strength and distance

Wi-Fi signal degrades quickly with distance and walls. Two interior walls or a single thick brick wall can turn a strong signal into a marginal one, and marginal signals drop. Most operating systems show signal as bars, but the real number that matters is RSSI (received signal strength in dBm): better than -60 dBm is excellent, -70 is usable, anything weaker than -75 dBm will be unstable.

Move the device closer to the router and see if the drops stop. If they do, your router placement is the issue. Routers belong in the center of the home, elevated, out in the open — not in a basement cabinet next to the cable jack. If repositioning isn't possible, a mesh node or a single Wi-Fi extender in the dead zone is usually the cheapest fix.

Channel congestion (2.4 vs 5 GHz)

Wi-Fi runs on two main frequency bands. 2.4 GHz travels further and goes through walls better but only has three non-overlapping channels (1, 6, 11) — and every neighbor's router, every Bluetooth speaker, and every microwave is fighting for the same airspace. 5 GHz has many more channels and is far less crowded, but the signal drops off faster with distance.

In a dense apartment building, 2.4 GHz is often unusable during peak hours. Install a Wi-Fi analyzer app (WiFi Analyzer on Android, WiFi Explorer on macOS, inSSIDer on Windows) and look at how many networks are sharing your channel. If you see ten networks all on channel 6, that's your problem. Switch to a less crowded channel in the router admin page, or — better — move your devices to the 5 GHz band entirely if they're within range.

Many routers broadcast both bands under the same SSID and let the client pick. That sounds convenient, but devices often cling to a weak 2.4 GHz signal instead of switching to a strong 5 GHz one. Splitting the SSIDs (e.g. MyWifi and MyWifi-5G) gives you manual control and frequently ends mysterious drops.

Other interference

The 2.4 GHz band is shared with a lot of household devices that are not Wi-Fi. Microwave ovens leak right in the middle of the band — if your Wi-Fi dies for 90 seconds at a time and you've been reheating coffee, that's why. Older cordless phones (DECT 6.0 is fine, anything older is suspect), baby monitors, wireless security cameras, and some Bluetooth devices can all clobber 2.4 GHz.

5 GHz is much cleaner but not immune — some weather radar bands force routers to switch channels (DFS events), which can cause a brief disconnect. If your drops cluster around a specific time of day or coincide with using a specific appliance, you've probably found your culprit.

Router firmware and restarts

Routers are small Linux computers, and like any computer they get into bad states after weeks or months of uptime. Memory leaks, lookup tables that fill up, processes that crash silently. The "have you tried turning it off and on again" joke exists because it genuinely fixes a startling percentage of router problems.

Unplug the router for 30 seconds, plug it back in, and wait two minutes for it to fully boot. If your drops stop for a few days and then come back, the router is unstable — check for a firmware update in the admin page (usually at 192.168.0.1 or 192.168.1.1). Most consumer routers have shipped multiple firmware updates that specifically address Wi-Fi stability bugs, and many never auto-install them.

If your router is more than five years old and the manufacturer has stopped issuing firmware updates, it is genuinely time to replace it. Wi-Fi standards have moved on (Wi-Fi 6 / 6E / 7) and older hardware handles modern device density poorly.

Wi-Fi drivers and power management

If only one device on your network keeps dropping while everything else stays connected, the problem is on that device — usually the Wi-Fi adapter driver or a power-saving setting that aggressively cuts the radio.

On Windows, open Device Manager, expand Network Adapters, right-click your Wi-Fi adapter, choose Properties, and go to the Power Management tab. Uncheck "Allow the computer to turn off this device to save power." This single setting causes a huge fraction of Windows laptop Wi-Fi drops. While you're in there, check the Driver tab and update to the latest version from the laptop manufacturer's site (not Windows Update — manufacturer drivers are usually newer for Wi-Fi).

On macOS, drops are less common but the worst offender is auto-join behavior — your Mac sees a weaker known network and switches mid-stream. Go to System Settings → Wi-Fi, click Details on your network, and review "Auto-Join" plus the "Ask to join networks" option to stop opportunistic switching.

On Linux, power saving on the wireless chip is the usual culprit. Run iwconfig wlan0 power off (replace wlan0 with your interface name) to disable it for the current session. To make it permanent, edit your network manager config or add a systemd unit — exact path depends on distribution.

Tip: keep a ping running while you test
Before changing any setting, start ping 1.1.1.1 -t (Windows) or ping 1.1.1.1 (macOS/Linux) in a terminal window you can see. After each change, watch for 10 minutes. If timeouts stop, you found it. If they continue, undo the change before trying the next one — otherwise you'll fix three things at once and never know which one mattered.

DHCP and IP conflicts

When your device joins the network, the router hands it an IP address via DHCP with a lease time (often 24 hours). When the lease expires, the device renews it. If the renewal fails — busy router, glitched DHCP server, a duplicate static IP somewhere on the network — the device briefly loses its address and the connection drops. This looks like a Wi-Fi disconnect but the radio link is fine.

To force a fresh DHCP lease on Windows, open Command Prompt as administrator and run ipconfig /release && ipconfig /renew. On Linux, sudo dhclient -r && sudo dhclient. On macOS, you can use System Settings → Network → Details → TCP/IP → "Renew DHCP Lease."

If the drops happen roughly every 24 hours, that's a renewal failure — shorten the lease time in the router (try 4 hours) so problems surface faster and you can catch them, or fix the root cause: usually a device on the network with a manually-set static IP that collides with the DHCP pool.

When to call the ISP

If the wired test at the start of this article showed drops even on Ethernet — or if your continuous ping shows packet loss in bursts that affect every device at once — the problem is upstream of your router. That means the modem, the line into your home, or something at the ISP. No amount of router tweaking will fix it.

Before you call, gather evidence. Capture a few minutes of ping 1.1.1.1 -t showing the timeouts with timestamps. Note the exact times drops happen and whether they cluster (every evening, every Saturday morning, etc.). Check modem lights against the modem's manual — a flashing or off "online" light points directly at the line. Run a traceroute to see where packets stop.

When you call support, skip "my internet is bad" and lead with the specifics: "I have intermittent packet loss to 1.1.1.1, 4 to 8 percent over the last 24 hours, consistent on a wired connection directly to the modem, occurring mostly between 7 and 11 PM." This gets you past the script-reading first tier and into the hands of someone who can actually open a line ticket.


Related: Ping tool · Why is my internet slow? · Network diagnostics guide