My Google Nest Wifi was working fine, but recently devices keep dropping and speeds are much slower than before. I’ve restarted the router and checked cables, but nothing seems to fix it. What else can I try to stabilize my Google Nest Wifi network and improve performance?
First thing I would do is figure out if the problem is WiFi only or the internet link itself.
-
Check wired vs wireless
• Plug a laptop or PC straight into the Nest router LAN port with an ethernet cable.
• Run speedtest.net a few times.
– If wired speeds look normal but WiFi is slow or drops, the Nest wireless side is the issue.
– If wired is also slow, look at the modem or your ISP. -
Check your ISP and modem
• Reboot the modem, wait 2 to 3 minutes, then reboot Nest.
• Log in to your ISP account and see if they show errors, signal issues, or outages.
• If your modem is old, ask for a line test. Noise on the line causes random drops and weird speed swings. -
Check placement and interference
This breaks a lot of Nest setups over time as homes change.
• Keep Nest units in open air, not inside cabinets or behind TVs.
• Keep them a few feet away from microwaves, cordless phone bases, baby monitors, and big metal objects.
• If you moved furniture or added a big appliance, try shifting the router a few feet. -
Channel and band settings in Google Home app
• Open Google Home, go to WiFi, then Network performance.
• See if it reports “congestion” or “weak connection” to points.
• Turn off the “Prefer 5 GHz” option only if some old devices struggle, otherwise keep them on 5 GHz for better throughput and less interference.
• If you have “guest network” active and never use it, turn it off to reduce overhead. -
Check mesh point placement
If you use extra Nest points:
• Each point needs a strong signal to the main router. Avoid placing a point at the very edge of coverage. Place it halfway between the dead spot and the router.
• In the Google Home app, open each point and check “Connection strength”. If it shows weak, move it closer to the router or run ethernet backhaul if possible.
• Avoid placing a point near thick walls, fireplaces, or concrete. -
Look for bandwidth hogs
• In Google Home, go to Devices and sort by usage.
• See if something is chewing bandwidth, like a cloud backup, torrent, or a game console downloading patches.
• Pause or schedule heavy tasks at night. -
Check for double NAT or extra routers
If your ISP gave you a modem router combo, you might have two routers:
• If the ISP box also broadcasts WiFi, either turn off its WiFi or put it in bridge mode so Nest is the only router.
• Double NAT often causes random disconnects, VPN issues, and lag. -
Turn off QoS or priority tricks
• If you set “preferred activities” or prioritized devices for gaming or calls, try turning that off.
• Sometimes QoS logic mis-detects traffic and chokes the rest. -
Update firmware and do a clean reset
• In Google Home, check for updates on the Nest wifi. Updates should install overnight but they glitch sometimes.
• If problems started after a power outage or firmware update and nothing fixes it, do a factory reset.
– Hold the reset button until the light flashes, then set it up again from scratch in the app.
– Recreate the same SSID and password so devices reconnect without reconfig.
• Test speeds after reset before turning on extras like guest wifi or parental controls. -
Scan your WiFi environment
If you live in an apartment or dense neighborhood, neighbor WiFi often crushes performance.
• Use a WiFi analyzer to see crowded channels and signal strength in each room.
• A good tool for this is NetSpot WiFi analysis and optimization. It builds a coverage map, shows weak spots, and shows which channels are packed.
• After scanning, move your Nest units or change channel settings if possible through your ISP router or additional access points. -
Test with fewer devices
• Temporarily disconnect smart plugs, bulbs, cameras and leave only a few main devices.
• Run speed tests and see if stability improves.
If things look better with fewer devices, Nest is hitting its device management limits. Splitting IoT gear onto a secondary cheap access point helps. -
When Nest itself starts failing
If all the above checks out, and speeds are still worse than before with drops:
• Test with a different router if you can borrow one.
• If a cheap router runs stable in the same spot with same modem and wiring, your Nest hardware might be failing. Heat and age do that.
Short version action list:
- Test wired speed direct to Nest.
- Reboot modem and Nest, check ISP line quality.
- Move Nest units, avoid interference, check mesh signal in app.
- Scan WiFi with NetSpot and adjust placement or channels.
- Factory reset Nest and reconfigure if issues persist.
- If still bad, compare with another router to see if Nest is the weak link.
If Nest was solid before and suddenly went flaky, I usually look at “what changed without me touching anything”: firmware auto‑updates, new devices, and RF noise. @voyageurdubois already covered the obvious stuff, so I’ll hit a few other angles that bite people with Nest specifically.
1. Check Nest’s built‑in “Advanced networking” stuff
In the Google Home app:
Wi‑Fi → Settings → Advanced networking.
Try toggling these, one at a time, and live with each change for a day:
- IPv6: Turn it OFF and see if stability improves. IPv6 glitches on some ISPs cause random drops.
- UPnP: If you don’t need it for consoles or P2P, disable it. I’ve seen buggy devices spam UPnP and choke the router.
- DNS:
- If you’re using custom DNS (like 1.1.1.1 or 8.8.8.8), switch back to ISP’s default.
- If you’re on ISP DNS now, try manual: 8.8.8.8 and 1.1.1.1.
Sometimes slow DNS looks like “slow WiFi.”
2. Look at what’s actually dropping
Instead of just “things drop,” check patterns:
- Is it only 2.4 GHz stuff (smart plugs, bulbs, old phones)?
- Is it only 5 GHz devices like newer laptops and phones?
- Is it only one room or the whole house at once?
If only your 2.4 GHz IoT stuff flakes out, Nest’s band steering can be a jerk:
- Temporarily turn off or unplug every 5 GHz‑only device you can.
- Reboot Nest, then reconnect some 2.4 GHz IoT devices and see if they stay online.
If they stabilize when the network is “quieter,” Nest is hitting limits on how many low‑power devices it can juggle.
In that case, a very practical fix is:
- Get a cheap separate 2.4 GHz AP, give it a different SSID like
Home-IoT, move all smart junk there, and leave Nest for phones / PCs / streaming.
This sounds overkill, but Nest sometimes just sucks with large IoT swarms.
3. Check for specific client bugs
On each device that’s dropping:
- Forget the WiFi network.
- Reboot the device.
- Rejoin using the same SSID and password.
On Windows: update the WiFi driver from the adapter or laptop maker, not just Windows Update.
On Android: check if battery saver or “WiFi power saving” is on; some brands get really aggressive and cause drops that look like router issues.
You might find it’s actually a couple of misbehaving clients that trigger issues for everyone.
4. Pay attention to heat and power quality
Nest units can get toasty. If they are:
- Sitting flat on a hot shelf
- Stacked on top of something warm
- Near a sunny window or radiator
Move the main router so it’s upright, ventilated, and not baking. Overheating can cause slowdowns and random reboots without obvious signs.
Also check the power situation:
- If they are plugged into an old power strip with other heavy loads (heaters, big speakers, etc.), try a direct wall outlet.
- If you had a brief power blip recently, low‑quality adapters can start misbehaving. If you have a spare USB‑C power brick with matching specs, try that temporarily on the main Nest.
5. Do a staged factory reset, not just “nuke and pray”
I slightly disagree with the “reset then rebuild everything at once” approach. I’d do it in layers to see where it breaks:
- Factory reset main Nest only, set it up with:
- Same SSID & password as before
- No guest network
- No parental controls, no family WiFi, no preferred activities
- Test with only 3–4 main devices (one laptop, one phone, one streamer).
- If it’s stable, add Nest points back one by one, testing in between.
- Only after everything is stable, re‑enable any fancy features (guest, parental controls, traffic priority).
If it falls apart only after you add a specific point or feature, you’ve found your culprit.
6. Do a real WiFi survey instead of guessing
You can eyeball channel congestion, but a proper survey is a lot more honest than our gut feelings.
Grab something like NetSpot on a laptop or Mac and walk around:
- It will map signal strength of each Nest unit room by room.
- You’ll see where neighboring routers overlap and crush your channels.
- You can literally see dead spots and over‑saturated areas rather than guessing.
A nice starting point is checking out boosting your WiFi speed and coverage to visualize how your Nest Wifi actually behaves in your home.
If the heatmap shows giant orange/red blobs of neighbor WiFi sitting on top of yours, that explains random slowdowns during evenings.
Even though @voyageurdubois mentioned scanning, actually doing a full survey with NetSpot is usually the moment people go “ohhh that’s why everything sucks in the bedroom.”
7. Watch for periodic events
Ask yourself: are the drops tied to something:
- Microwave running
- Bluetooth headphones in heavy use
- Baby monitor or camera turning on
- EV charger, treadmill, or some high‑draw device starting up
Keep a quick log for a day: time of drops vs what’s happening in the house. It sometimes reveals a pattern you would never think of. I had a client whose WiFi tanked every evening because a neighbor’s old microwave obliterated 2.4 GHz through the wall.
8. When to suspect the Nest itself
If, after all that:
- Wired speed to the Nest is fine
- ISP line is clean
- RF environment is workable (per NetSpot)
- Fresh reset with minimal devices still drops randomly
then yeah, the Nest hardware may just be on its way out. These units run hot and are on 24/7; radio performance can degrade over time.
If you can borrow any other router for a day and test in the same exact spot with the same modem and one or two devices, that’s the cleanest A/B test. If the cheap loaner is stable and fast, the Nest is probably the bottleneck now.
SEO‑friendly summary of what you’re basically dealing with:
Troubleshooting unstable Google Nest Wifi often means digging deeper than a quick reboot. You need to test advanced networking options, isolate buggy devices, watch for overheating and power problems, perform a clean, staged factory reset, and use real WiFi surveying tools like NetSpot to see wireless interference and dead zones. Once you know whether the problem is your ISP, radio congestion, or failing hardware, you can decide if better placement, reduced IoT load, or replacing the Nest system is the right move to stabilize your home network.
2 Likes