How can I fix intermittent Wi-Fi drops on my home network?

Ai
1

My home Wi-Fi keeps dropping randomly on multiple devices, even though my ISP speed tests look fine and the router seems okay. I’ve tried rebooting, changing channels, and moving the router, but the disconnects still happen, especially during video calls and gaming. I really need a stable connection for work and can’t figure out what’s causing this. Can someone help me troubleshoot and suggest concrete steps or settings to check to stop these intermittent Wi-Fi drops?

2

Had this exact headache at home. ISP tests fine, router looks fine, still random drops on phones, laptops, TV. What fixed it for me was treating it like a bunch of small problems, not one big mystery.

Try these in order.

  1. Check if it is Wi Fi or internet
    • When a drop happens, run:
  • On Windows: ping 192.168.1.1 -t
  • On Mac/Linux: ping 192.168.1.1
    If ping to the router fails, problem is Wi Fi or local network.
    If router ping works but websites die, problem is ISP or modem.
  1. Split 2.4 GHz and 5 GHz
    Log in to router
    • Give 2.4 GHz and 5 GHz different SSIDs, like:
  • MyWifi_24
  • MyWifi_5
    • Connect phones and laptops to 5 GHz if they are close.
    • Use 2.4 for older or far devices.
    A lot of routers try to be smart with “band steering” and they screw up and cause drops.

  1. Turn off fancy features
    Disable these options if you see them:
    • Smart Connect / band steering
    • Airtime fairness
    • QoS or “traffic prioritization”
    • Wi Fi “optimizer” or “AI” modes
    These often break more than they help.

  2. Check for interference
    • Keep router away from:

  • Microwave
  • Baby monitor
  • Cordless phone base
  • Bluetooth speakers stacked on it
    • On 2.4 GHz, use channel 1, 6, or 11 only.
    • On 5 GHz, use channels 36, 40, 44, or 48 first.
    You said you changed channels, but stick to those sets, they behave better.
  1. Reduce “busy” features on devices
    On each device that drops:
    • Turn off “random MAC” / “private address” for your own network SSID.
  • On iPhone: Wi Fi > your network > Private Wi Address off.
  • On Android: Wi Fi > your network > Advanced > MAC type to “Phone MAC” or similar.
    Some routers hate random MACs and drop clients.
  1. Fix DHCP range and reservations
    Router settings:
    • Set DHCP range to something like 192.168.1.50 to 192.168.1.200
    • Give static DHCP reservations to:
  • Smart TV
  • Game console
  • Work PC
    This keeps devices from flipping IPs all the time.

  1. Firmware and modem check
    • Update router firmware to latest stable version.
    • If the router is ISP provided, bridge it and use your own router if possible.
    • Check modem logs for T3 or T4 errors. Those mean ISP side issues even if speedtests look ok.

  2. Test with one extra access point
    If you have a spare router:
    • Put main router by modem.
    • Turn second router into AP mode.
    • Connect it by ethernet to the first.
    • Give it same SSID and password, but different channel.
    If devices stop dropping on the AP, your original router radio is weak or failing.

  3. Quick stress test
    • Start a continuous ping to your router.
    • Stream 4K video on TV.
    • Start a big download on a PC.
    Watch ping.
    If ping times spike to thousands of ms or drop, router is overheating or maxing out.
    Try:
    • Turn off USB features and media servers on the router.
    • Give it better airflow.
    • If it is more than 4 to 5 years old, replace it.

If you post your router model, ISP type, and whether drops happen on ethernet too, you will get more targeted ideas.

3

Sounds like you’ve already done most of the “basic YouTube fixes,” and @kakeru covered a ton of the usual suspects, so I’ll try not to just repeat that list.

Here are some other angles that often get missed:

1. Check if it’s actually a client-side power saving issue

Some devices aggressively put their Wi Fi to sleep and it looks like the network is dropping.

  • On Windows laptops:
    • Device Manager → Network adapters → your Wi Fi card → Power Management → uncheck “Allow the computer to turn off this device to save power.”
    • In Advanced tab, if you see “Power Saving Mode,” set it to “Maximum Performance.”
  • On Android: disable “Wi-Fi power saving” / “Adaptive connectivity” / battery optimizers for apps that seem to drop.
  • On iOS: if it only happens when screen locks, suspect “Wi Fi Assist” or aggressive handoff. Turn off Wi Fi Assist in Cellular settings.

2. Look for roaming / mesh weirdness

If you have any extenders, mesh nodes, powerline Wi Fi, or ISP “pods,” they can cause random drops when devices roam badly.

  • Temporarily unplug all extenders / pods.
  • Use only the main router for a day.
  • If drops stop, the fix is usually:
    • Disable “fast roaming” / 802.11r / 802.11k/v on the mesh.
    • Or separate SSIDs for main vs extender so devices don’t try to roam constantly.

I slightly disagree with turning off every “fancy feature” like QoS by default. QoS, if done right, is fine. What does cause issues a lot more is “fast roaming” on cheap mesh systems and some half baked “AI roaming” features.

3. Check for hidden double NAT and multiple DHCP servers

This one bites people a lot and looks like random Wi Fi drops, especially when leases renew.

  • If you have:
    • ISP modem/router combo
    • Plus your own router
      Both might be doing DHCP and NAT.
  • Symptom: devices randomly lose internet, especially after some idle time, while Wi Fi bars still look full.
  • Fix:
    • Put ISP box in bridge mode or
    • Put your router into AP mode.
    • Make sure only one device is handing out IPs.

Also go into your router and look for:

  • “More than one DHCP server detected” warnings.
  • Devices with the same IP address. That can cause weird intermittent cutouts.

4. MTU / fragmentation issues

This is nerdy but real. If you have PPPoE, certain VPNs, or some funky ISP, the default MTU can cause weird half-working behavior.

  • On a wired PC:
    • ping 8.8.8.8 -f -l 1472 (Windows)
      • If it says “Packet needs to be fragmented,” reduce 1472 downward until it stops.
  • Then set your router WAN MTU to that number + 28 (for headers).
    Broken MTU can show as “Wi Fi randomly dying” when in reality large packets are just being dropped.

5. IPv6 shenanigans

Sometimes IPv6 is broken on the ISP or router, and some devices prefer IPv6 first, so they stall.

  • On router: disable IPv6 entirely for a day and see if stability improves.
  • Or at least disable it on one test device and compare.

If drops get way better with IPv6 off, then the “random” issue was dual stack confusion.

6. Test with a cheap USB Wi Fi adapter

If it’s mostly happening on one PC or one type of device, try another NIC before blaming the network more.

  • Plug in a $10 USB Wi Fi dongle.
  • Connect to the same SSID.
  • If that machine suddenly becomes rock solid while other devices are fine too, the onboard Wi Fi card or its drivers are trash.

Even when multiple devices drop, they might all share the same problem driver (e.g., a bunch of Intel Wi Fi 6 cards with a buggy driver version).

7. Look for congestion beyond just channels

You mentioned changing channels, but that’s half the story.

  • Use a Wi Fi analyzer app on your phone.
  • Check:
    • How many other APs overlap on your channel.
    • How loud they are compared to yours (signal strength).
  • If your signal at the trouble spot is below about -70 dBm and there are multiple strong neighbors, it’s not just channel choice, it’s a coverage problem.

In that case, the real fix is:

  • One centrally placed, decent quality Wi Fi 6 router at least, or
  • A proper wired-backhaul mesh, not a random repeater.

8. Check for scheduled tasks or devices nuking the air

Look for patterns:

  • Do drops happen at specific times:
    • When a backup program starts
    • When a cloud sync kicks in
    • When someone streams 4K plus gaming plus downloads

Or:

  • Smart devices doing firmware updates
  • A neighbor’s microwave at dinner time

You can prove this:

  • Run continuous ping to your router and to 8.8.8.8.
  • When it drops, note what’s running and who just turned on what.

If pings spike only when certain traffic loads happen, your router is getting saturated or bufferbloat is insane.

9. Check for CPU or memory exhaustion on the router

If your router has a status page, see:

  • CPU pegged at 90 to 100%
  • RAM almost full

Sometimes one misbehaving device spams multicast/broadcast and kills the router.

Test:

  • Disconnect half your smart devices (IoT bulbs, cams, plugs) for a while.
  • If everything stabilizes, one of them is chatty or buggy.
  • Segment IoT stuff on a guest network or 2.4 GHz only and limit what they can do.

If you want a simple “try this next” order, based on what you already did and what @kakeru suggested:

  1. Temporarily disable IPv6 on router.
  2. Make sure there is no double NAT or second DHCP.
  3. Turn off roaming / mesh nodes or extenders and test only on main router.
  4. Disable Wi Fi power saving on a couple of main devices and test.
  5. Check router CPU/RAM and maybe disconnect half your IoT junk for a day.
  6. If all that still fails, at that point I’d start suspecting the router hardware even if it “seems okay” and replace it with something midrange and modern, not ISP-supplied.

Intermittent drops are often death-by-1000-cuts, not one big obvious bug. The trick is to temporarily simplify the network, prove it’s stable in a barebones setup, then add stuff back until the problem reappears.

4

Couple of angles that @cacadordeestrelas and @kakeru did not lean on much:

  1. Treat 2.4 GHz IoT as “untrusted noise”

A ton of random drops come from a zoo of smart bulbs, plugs, cheap cameras, etc. Instead of just shoving them on 2.4 GHz and hoping for the best:

  • Create a guest SSID just for IoT on 2.4 GHz only.
  • Turn off “allow guests to see each other” so their chatter stays contained.
  • Keep your phones / laptops on a separate main SSID.

If your main devices suddenly become stable, you did not have a Wi Fi problem, you had a broadcast storm from junk hardware.

  1. Stop chasing channels, fix coverage

You already moved the router and changed channels. At this point, I would stop tweaking the same slider.

If signal where drops happen is below about −65 dBm and you have walls, floors, or mirrors in the way, no software setting is going to be magic. Wired backhaul + extra AP is the grown up fix.

  • Run one cheap flat Ethernet cable to the worst room.
  • Add a dedicated access point there in AP mode, channel separated from the main one.

Avoid “Wi Fi extenders” that repeat wirelessly. They often make drop issues worse by halving throughput and increasing latency.

  1. Be careful with turning off all “fancy features”

Both replies suggested killing Smart Connect / AI features, which I agree with, but I slightly disagree on turning off QoS by default.

If your upload is small (typical cable/DSL) and someone is doing big cloud backups, you can get fake “Wi Fi drops” that are just bufferbloat. Good QoS or SQM on the router can fix that:

  • Set QoS upload/download to about 80–90% of real speed.
  • Prioritize interactive traffic (video calls, gaming) over bulk uploads.

If your current box has only a toy “gaming mode,” it might be time to replace it with a router that has real QoS or SQM support. This is where a product specifically described as a high performance Wi Fi router with strong QoS features like ‘’ would fit, since it is typically designed to handle many clients and high traffic without choking.

Pros of ‘’:

  • Usually better CPU and RAM than ISP routers
  • Often supports proper QoS/SQM
  • Better firmware update support than bottom tier hardware

Cons of ‘’:

  • Costs more than “free” ISP box
  • Needs a bit of setup time
  • Overkill if you only have a tiny apartment and 3 devices
  1. Check lease time and “micro-outages”

Everyone talked about DHCP, but not lease duration. If your router has a very short DHCP lease (like 30 minutes or 1 hour), you can see tiny blips that feel like random drops.

  • Set DHCP lease time to at least 12 or 24 hours.
  • After that, reboot router and reconnect devices once.

Also, micro power flickers can reboot the modem/router so fast you never notice, but Wi Fi will “drop”:

  • Put modem + router on a basic UPS.
  • If things suddenly stabilize, your issue was flaky power, not packets.
  1. Log everything while it is breaking

Instead of just trying settings and guessing, collect a bit of evidence:

  • On one wired device and one wireless device, run continuous ping to:
    • Router IP
    • Public IP like 8.8.8.8
  • At the same time, enable logging on router:
    • Syslog if it supports it, to a PC
    • Or at least “connection” and “wireless” logs

When a “drop” occurs, check if:

  • Wireless client disassociated / reauthenticated
  • WAN link flapped
  • DHCP renew happened right at that time

That will tell you if the enemy is RF, routing, or ISP.

  1. Version control your changes

With this many knobs to turn, it is easy to fix it once and then “unfix” it later.

Do it like this:

  • Day 1: Only split 2.4/5 GHz and separate IoT SSID. Record result.
  • Day 2: Change only DHCP lease and disable IPv6. Record result.
  • Day 3: Enable or tune QoS. Record result.

If you change 8 things at once, you will never know which one stopped (or reintroduced) the problem.

Between what @cacadordeestrelas covered (power saving, roaming, double NAT, MTU, IPv6, congestion, CPU/RAM) and @kakeru’s full checklist (pings, band splits, channel sanity, firmware, AP test, stress test), you already have almost the complete playbook.

I would personally focus next on:

  1. Segregating noisy IoT into their own 2.4 GHz guest SSID.
  2. Extending with wired AP instead of more tweaks to a single box.
  3. Using a better router like ‘’ if your current one is old, overheats under load, or lacks proper QoS.

If, after isolating IoT, confirming no double NAT, and doing a wired AP, you still see random drops across many different client types, the remaining suspect is plain hardware flakiness in the main router or modem. At that point replacement is usually cheaper than the time spent debugging.