I’m having ongoing issues with my Google Wifi router dropping connections and slowing down randomly. I’ve tried rebooting, factory resets, and moving the access points, but the problem keeps coming back. Can anyone explain what might be causing this and walk me through reliable steps to fix or diagnose the problem in more detail
I fought with Google Wifi for months, so here is the stuff that finally made it stable for me. Going a bit checklist style so you can test step by step.
- Put the ISP modem in bridge mode
If your internet box from the provider also does routing or Wi‑Fi, you get double NAT and random weirdness.
• Log in to your ISP router.
• Turn off Wi‑Fi on it.
• Put it in bridge mode or passthrough.
• Let the main Google Wifi puck be the only router.
If bridge mode is not possible, set Google Wifi to “bridge mode” and let the ISP box be the router. You lose some Google Wifi features, but it gets more stable.
- Lock the backhaul and placements
Mesh falls apart if the pucks talk over weak 5 GHz backhaul.
• Distance between pucks: try 20–30 feet, with as few walls as possible.
• Avoid putting a puck near microwaves, cordless phones, baby monitors, bluetooth speakers, metal racks.
• If possible, wire the secondary pucks with Ethernet. That fixes many random drops.
Use the Google Home app
Settings → Wifi → Preferred activities
Turn on “Streaming” and “Gaming” if those matter.
Check “Mesh quality” in the app. If any node shows weak connection, move it or wire it.
- Fix channel congestion and interference
If you live in an apartment, neighbors destroy your Wi‑Fi without meaning to.
Use a wifi analyzer and look at real data. A good one on desktop is NetSpot.
Install it, run a scan, and look for:
• 2.4 GHz: how many networks share the same channel.
• 5 GHz: which channels are crowded.
You can use NetSpot for Wi‑Fi analysis and site surveys to map signal strength room by room. It helps you see where your Google Wifi drops off or overlaps too much. Once you see the congestion, try these:
• In the Google Home app, set 2.4 and 5 GHz to less crowded channels if your firmware allows it. Older Google Wifi is more automatic, so you might have less control, but at least you will know if interference is your problem.
• Move any 2.4 GHz heavy devices away from the pucks.
- Tame the client load
Google Wifi gets flaky if you throw 40+ devices at one node.
• In the app, check “Devices” and see how many sit on each puck.
• Move smart plugs, bulbs and other low‑priority gear closer to a secondary puck.
• For fixed devices, wire them with Ethernet into the nearest puck. That frees radio capacity.
If you have smart home hubs, try to keep them wired, not on Wi‑Fi.
- Turn off useless features on clients
Some phones and laptops hop networks like crazy.
On devices:
• Disable “Smart network switch”, “Wi‑Fi assistant” or similar features that hop between Wi‑Fi and LTE.
• On Windows, turn off power saving on the Wi‑Fi adapter.
• On Mac, forget old networks so they stop jumping.
- Firmware and DNS tweaks
• Ensure Google Wifi firmware is up to date in the Home app.
• Change DNS to 8.8.8.8 / 8.8.4.4 or 1.1.1.1.
Settings → Network & General → Advanced networking → DNS
Sometimes the “slow internet” feeling comes from bad DNS, not from Wi‑Fi.
- Test with a clean scenario
You need to isolate where the fault is.
• Connect a laptop by Ethernet directly to the main puck. Run speedtest.
– If wired speed drops too, your issue is either ISP, modem, or Google Wifi main unit.
• If wired is stable for 2–3 days, but wireless keeps dropping, it is Wi‑Fi radio, interference, or mesh topology.
- Heat and power issues
These pucks overheat in cramped spaces.
• Take the pucks out of cabinets.
• Keep them upright in open air.
• Try a different power brick on one node and see if behavior changes.
- When to suspect a dying unit
If:
• Only one puck keeps going offline in the app.
• Swapping locations makes the issue follow the puck, not the room.
Then the hardware is likely failing. I had to replace one and the random drops stopped.
If you post:
• ISP and modem model
• How many pucks
• How they are wired
• A quick screenshot of a NetSpot scan
People can give more targeted advice. For me, the big wins were bridge mode, wiring the second node, and placing them after looking at NetSpot heatmaps instead of guessing.
1 Like
Had almost this exact headache with Google Wifi and it turned out to be a combo of “Google being too smart” and a couple of dumb defaults.
@Mikeappsreviewer already hit the physical/ISP/mesh side really well, so I’ll skip repeating his checklist and focus on stuff the pucks and clients do in software that quietly wreck stability.
1. Turn off IPv6 in Google Wifi
This one fixed 80% of my random slowdowns.
In the Home app:
Settings → Network & general → Advanced networking → IPv6 → Off
Some ISPs have half-baked IPv6 or weird prefix delegation that makes Google Wifi constantly re-learn routes. Symptoms look exactly like what you describe: “random” slowdowns, short drops, then everything’s fine again.
Test for a few days with IPv6 off.
2. Lock down DHCP range & avoid IP conflicts
If anything else on your network runs DHCP (old router, NAS, Pi, printer with “wifi direct” nonsense), you can get phantom IP conflicts:
- Make sure only Google Wifi is doing DHCP if it’s in router mode.
- In the Home app:
Settings → Network & general → Advanced networking → DHCP IP reservations
Give static leases to “problem” devices (gaming consoles, TVs, work laptops). If your TV or console always drops first, this is a prime suspect.
3. Shorten DHCP lease time temporarily
To flush out odd client behavior:
Settings → Network & general → Advanced networking → DHCP → set lease time to something small (2–4 hours) for testing.
If things get better after leases renew, some device was clinging to an old network config.
4. Disable “Preferred activities” as a test
Slight disagreement with @mikeappsreviewer here: for some people, those QoS-ish toggles actually make performance spiky.
Home app: Settings → Wifi → Preferred activities → turn everything off for a day.
If your speeds suddenly stop swinging wildly, then you know the bandwidth prioritization logic is getting confused by your actual usage pattern.
5. Watch for a single “problem client”
One bad device can drag down the whole 2.4 GHz radio:
- In the Home app, go to Devices.
- Sort by “Most active” and watch during a slowdown.
- If a specific cam, smart TV, or IoT thing always shows huge usage when everything slows, try:
- Powering it off for a day
- Reconnecting it to Wi‑Fi from scratch
- For 2.4 GHz‑only cams, move them slightly or change orientation
I had one cheap camera that, when it lost packets, flooded the network with retries and turned the whole wifi into molasses.
6. Adjust MTU if you use PPPoE or weird ISP gear
If your ISP uses PPPoE or some custom VLAN tagging, the MTU can be wrong and cause stalls:
- Plug a laptop into the main puck via Ethernet.
- Run:
- Windows:
ping -f -l 1472 8.8.8.8 - Mac/Linux:
ping -D -s 1472 8.8.8.8
- Windows:
Reduce the size until it stops fragmenting, then add 28. That’s your real MTU.
Some folks set MTU on the upstream modem/router or on a managed switch in front of Google Wifi and suddenly the random hangs vanish.
7. Test with 5 GHz only (indirectly)
Google Wifi doesn’t give you a simple 2.4 / 5 GHz toggle, which is… “fun”. But you can at least see if 2.4 is the problem:
- Temporarily turn off every 2.4 GHz‑only device you own (plugs, bulbs, cameras).
- Reboot the Google Wifi network.
- Use only devices that support 5 GHz (modern phones, laptops) for a while.
If your network becomes rock solid, your issue is very likely interference or congestion on 2.4, not the router itself.
This is where NetSpot becomes super handy. If you run a quick survey with it, you can literally see where your 2.4 GHz signal overlaps with noisy neighbors, microwaves, etc. A proper Wi‑Fi heatmap from something like visualizing your home Wi‑Fi coverage is miles better than guessing by walking around with a phone.
8. Disable “AP isolation” / guest-style settings on main network
If you use Guest Wi‑Fi, keep it only for actual guests. Some folks accidentally push their own devices there or use cast/stream stuff on the guest side, which is limited and can feel like random drops or “laggy” internet.
Check that your main devices (phones, consoles, PCs) sit on the primary network, not the guest one.
9. Long‑term sanity check: measure, don’t guess
Since you’ve already done factory resets and placement tweaks, try running a week of actual data:
- Use Speedtest or Fast.com on a wired device once in the morning, once at night.
- Note when the slowdowns happen and which devices are active.
- Cross‑check with the “Usage” graph in Google Home → Wifi → Devices.
If the wired tests are always fine but Wi‑Fi is trash at specific times, you’re almost certainly fighting RF interference or crazy client behavior, not a dying puck.
And to make your topic clearer for others who might find this thread later, something like this tends to attract the right eyes:
Having recurring Wi‑Fi drops and slow speeds with Google Wifi mesh, even after multiple reboots, factory resets, and access point relocations. Looking for detailed troubleshooting steps to stabilize a Google Wifi network and stop random disconnects and performance dips.
If you can add:
- ISP name
- Modem model
- Number of pucks
- Screenshot from NetSpot’s scan
you’ll get more laser‑targeted replies instead of “have you tried turning it off and on again” on repeat.
Short version: you have already hit the obvious fixes, and @sognonotturno / @mikeappsreviewer covered the physical setup and software tuning really well. I would now treat this like a “prove it” project and gather evidence to decide if the villain is: ISP, RF environment, Google Wifi hardware, or particular clients.
1. Stop guessing: build a simple test matrix
Run these in order, for at least a day each:
-
ISP sanity check
- Laptop → Ethernet → ISP modem (Google Wifi completely removed).
- Run multiple speedtests during the times you usually see slowdowns.
- If things are flaky here, no amount of Google Wifi tweaking will fix it.
-
Google main puck as a dumb AP
- Put ISP box back in router mode.
- Put Google Wifi in bridge mode, Wi‑Fi on, same SSID/pass.
- If drops vanish, the router/NAT/DHCP logic in Google Wifi is your problem.
- If drops persist, you are probably fighting RF or hardware.
-
Single‑puck scenario
- Use only the main puck, no mesh nodes.
- Put it in the most central spot you can, keep the number of clients low.
- If that is stable, your issue is specifically mesh backhaul or a bad secondary unit.
This is where I slightly disagree with some of the earlier advice: instead of tweaking a live, complex mesh in place, temporarily reduce it to the simplest topology possible and only scale up once it behaves.
2. Look at patterns, not just snapshots
Both previous replies mentioned “problem clients” and congestion. Expand on that by logging:
- Time of each slowdown.
- Active apps (4K streaming, big game downloads, video calls, cloud backup).
- Which room you are in when Wi‑Fi feels bad.
After a few days you can see patterns like “evenings when the TV + console are on” or “only when I walk from office to bedroom.” That points you to client roaming and band steering rather than pure “router sucks.”
3. Roaming & sticky client tuning
Google Wifi can look bad because clients roam poorly:
- On phones and laptops, disable any “aggressive roaming” or “Wi‑Fi optimization” toggles for a while.
- If a particular room is right between two pucks, try:
- Moving one puck closer so that room clearly belongs to a single node.
- Or intentionally creating a bit of “coverage asymmetry” so the handoff is clearer.
- Test by sitting in a “problem” room and running a continuous ping (for example to 8.8.8.8) while walking slowly toward and away from a puck. If you see spikes or drops exactly when switching nodes, the mesh steering is the culprit.
4. RF environment: validate with tools, not intuition
Re: channel interference, both others suggested using a Wi‑Fi analyzer. I would double down on that with an actual survey:
- Use NetSpot on a laptop to build a quick heatmap of:
- Signal strength of each Google Wifi node.
- Overlap with neighbors’ 2.4 and 5 GHz networks.
- Walk the house and let NetSpot record; you will see:
- Dead or weak spots that should not be weak.
- Rooms where your own pucks overlap too much.
- Channels where neighbors are swarming.
Pros of NetSpot:
- Visual, easy to see “problem rooms.”
- Shows both your network and neighbors at once.
- Great for placing pucks and deciding where to wire backhaul.
Cons of NetSpot:
- Best mapping features are on desktop/laptop, not phone.
- Takes a bit of time to walk and build a proper survey.
- Beginners can feel overwhelmed by all the graphs at first.
Once you see the real map, it is much easier to decide whether to move a puck two meters or accept that a certain node should really be wired.
5. Compare configuration philosophies
- @mikeappsreviewer prefers enabling “Preferred activities” and tuning QoS‑ish bits.
- @sognonotturno suggests sometimes turning those off and also disabling IPv6.
I would actually test both philosophies explicitly:
- One week with IPv6 off and Preferred activities off.
- One week with IPv6 off and Preferred activities on (streaming + gaming only).
Note the difference. Automated “smart” behavior can be great in one environment and pathological in another.
6. Decide whether to keep Google Wifi at all
After the tests above you should be able to say clearly:
- “ISP or physical line is unstable”
- “Mesh is fine, routing/DHCP logic is flaky”
- “One puck is clearly defective”
- “RF environment is brutal and any mesh will struggle unless I wire backhaul”
If everything points to “only my Google Wifi behaves badly; ISP, wiring, RF and clients look normal,” then the time cost of endless tweaking might be higher than just moving to a newer mesh system with better radios and more control.
If you post your test matrix results (especially: ISP‑only test, bridge‑mode test, single‑puck test, and a basic NetSpot snapshot), it becomes much easier to say “this is 90% a Google Wifi routing bug” versus “you are living in a 2.4 GHz war zone and need wiring or a different layout.”