Google WiFi Not Working: Fix Dropped Connections, Slow Speed & No Internet Access
Google WiFi not working? Fix dropped connections, slow speeds, no internet access & mesh issues with step-by-step troubleshooting. Includes diagnostic commands.
- Root Cause 1: ISP-side outages or modem misconfiguration prevent Google WiFi from obtaining a valid WAN IP, causing 'No Internet' errors even when the mesh is healthy.
- Root Cause 2: Channel congestion, band-steering bugs, or firmware defects cause the router puck to drop connections repeatedly or throttle upload/download speeds below expected thresholds.
- Root Cause 3: Mesh point placement issues (too far apart, physical obstructions) cause mesh nodes to lose their backhaul link, producing 'Google WiFi mesh not connecting' symptoms.
- Quick Fix Summary: Power-cycle the modem first, then the Google WiFi router puck, run a speed test from the Google Home app, check for firmware updates, and if problems persist, perform a factory reset followed by reconfiguration.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Power-cycle modem + router | First step for any connectivity issue | 2-5 min | None |
| Google Home app network check | Diagnosing where the failure is (WAN vs mesh vs device) | 5-10 min | None |
| Change WiFi channel / band | Persistent slow speeds or intermittent drops in congested areas | 10-15 min | Brief service interruption |
| Firmware update via Google Home | Bugs, security patches, or mesh instability after recent changes | 15-30 min | Low – auto-applied by Google |
| DNS server change (8.8.8.8) | Slow browsing but speed tests are normal; DNS resolution failures | 5 min | None |
| Factory reset single puck | Corrupted config on one mesh node; mesh not connecting | 20-30 min | Loses saved config for that puck |
| Full network factory reset | All else fails; persistent 'Google WiFi broken' state | 45-60 min | High – wipes all settings |
| ISP modem bridge/DMZ mode | Double-NAT causing packet loss or VPN/port-forward failures | 30-60 min | Medium – requires ISP coordination |
Understanding Why Google WiFi Stops Working
Google WiFi (and its successor Nest WiFi) operates as a mesh system managed entirely through the Google Home app. Unlike traditional routers with a local admin panel at 192.168.86.1 (which is only accessible for very basic diagnostics), most configuration lives in Google's cloud. This architecture means failures can originate at multiple layers: your ISP, the WAN handoff, the router puck itself, the mesh backhaul between pucks, or client devices.
Common error messages and symptoms include:
- "No internet" banner in the Google Home app with a red exclamation on the router icon
- "Can't reach internet" shown during a network check
- Speed tests showing <1 Mbps upload ("google wifi upload speed slow") while download is normal
- Devices showing "Connected, no internet" in their WiFi settings
- Mesh points showing as "offline" or "not connected to mesh" in the Google Home app
- Intermittent drops every 10-30 minutes ("google wifi dropping connections")
Step 1: Isolate the Failure Layer
Before touching any settings, determine where the problem actually lives.
A. Check ISP First Plug a laptop directly into your modem (bypassing Google WiFi entirely) using an Ethernet cable. If you still have no internet, call your ISP — Google WiFi is not the problem.
B. Run the Built-in Network Check
- Open the Google Home app on your phone.
- Tap WiFi → your network name → the gear icon.
- Tap Test network (or Run a test depending on app version).
- Wait for the diagnostic to complete. It will report:
- DNS: Whether the router can resolve hostnames
- Internet: Whether a WAN IP was obtained
- Router: Whether the primary puck is reachable
- Mesh points: Whether satellites are on the backhaul
If the test returns "Router: Unable to reach router", the primary puck has a hardware or firmware issue. If it returns "Internet: No internet detected" but the router is reachable, the problem is between the puck and your modem/ISP.
C. Check WAN IP Assignment Navigate to Google Home app → WiFi → Settings → Advanced networking → WAN. If the WAN IP shows as 0.0.0.0 or is blank, the router never received an IP from your modem. This is almost always a modem issue or a DHCP handshake failure. Power-cycle the modem (unplug for 30 seconds) while Google WiFi is off, then plug the modem back in, wait 60 seconds for it to sync with your ISP, and then plug in the Google WiFi router puck.
Step 2: Fix Connection Drops and Slow Speeds
Power-Cycle in the Correct Order Order matters. Always cycle from the ISP side inward:
- Unplug your modem (and any separate ONT/gateway).
- Unplug all Google WiFi pucks.
- Wait 60 seconds.
- Plug in the modem; wait until all lights are solid (1-2 minutes).
- Plug in only the primary Google WiFi router puck; wait for it to show a solid white light (up to 3 minutes).
- Plug in mesh point pucks one at a time.
Address Channel Congestion (Slow Speeds) Google WiFi auto-selects channels, but in apartment buildings with dozens of networks, this fails. Unfortunately, Google WiFi on original hardware does not expose manual channel selection — this is one of its limitations. Workarounds:
- Enable "Preferred activities" under WiFi Settings to prioritize a device temporarily.
- If you have Nest WiFi Pro (Wi-Fi 6E), ensure 6 GHz band is enabled for backhaul.
- Move mesh points to use wired backhaul (Ethernet between pucks) — this is the single biggest speed improvement available and eliminates wireless backhaul congestion entirely.
To set up wired backhaul:
- Run an Ethernet cable from a LAN port on the primary puck to the WAN/LAN port of each additional puck.
- In the Google Home app, navigate to WiFi → Settings and the app should automatically detect and enable wired mesh.
Fix Upload Speed Specifically If download is fast but upload is very slow (a common complaint: "google wifi slow upload speed"), the issue is often:
- Upload QoS throttling: Disable any active family pause schedules temporarily and retest.
- ISP asymmetric plan: Confirm your plan's upload speed with your ISP.
- WMM (Wi-Fi Multimedia) negotiation bug: Perform a factory reset of the affected puck and reconfigure.
- DNS-over-HTTPS conflicts: Change your DNS to 8.8.8.8 / 8.8.4.4 in Advanced networking settings.
Resolve Mesh Points Not Connecting If mesh points show as offline:
- Bring the mesh point within 15 feet of the primary puck for initial setup.
- Factory reset the offline puck by holding the reset button on the bottom for 10 seconds until the light flashes orange.
- Re-add it in the Google Home app: WiFi → Add → Add point.
- Once it connects at close range, move it to the desired location (ideally no more than one room and one wall away from another puck).
Address Packet Loss Packet loss manifests as choppy video calls, game lag, or stuttering streams even when speed tests look fine. Diagnose it with a continuous ping:
ping -c 100 8.8.8.8
If you see more than 1-2% packet loss to 8.8.8.8 but zero packet loss to 192.168.86.1 (the Google WiFi router), the loss is happening between the router and the internet — an ISP issue. If you see packet loss to 192.168.86.1 itself, there is a wireless issue between your device and the puck.
Fix Family Pause / Pause Not Working If Google WiFi Pause is not working as expected (devices still connecting when paused), this is often due to:
- The device using a randomized MAC address (common on iOS 14+, Android 10+). Go to your device's WiFi settings → your network → disable Private/Random MAC.
- Multiple devices sharing an account that isn't being fully paused.
- App cache issues — force-close the Google Home app, clear its cache, and retry.
Step 3: Factory Reset as Last Resort
If all else fails and your network is still broken:
- Open Google Home app → WiFi → Settings → Factory reset network.
- Alternatively, hold the reset button on the primary puck for 10 seconds (factory resets that puck only).
- After the reset, set up the network fresh. Do NOT restore from a backup, as the backup may contain the corrupt configuration causing your issue.
- After setup, update firmware immediately: Google Home → WiFi → Settings → Software version → Check for updates.
Step 4: Eliminate Double-NAT
If your ISP gives you a combo modem/router (common with Xfinity, AT&T, Spectrum), your Google WiFi is sitting behind another router, creating Double-NAT. This causes:
- High ping and packet loss
- VPN connection failures
- Port forwarding not working
- Inconsistent speeds
Fix: Log into your ISP gateway (usually 192.168.1.1 or 10.0.0.1), find DMZ or IP Passthrough settings, and point it to the WAN IP of your Google WiFi puck. Alternatively, call your ISP and ask them to put the gateway in bridge mode.
Frequently Asked Questions
#!/usr/bin/env bash
# Google WiFi Diagnostic Script
# Run from any device on your Google WiFi network
# Works on Linux/macOS; on Windows use WSL or adapt ping syntax
ROUTER_IP="192.168.86.1"
EXTERNAL_DNS="8.8.8.8"
EXTERNAL_HOST="google.com"
echo "========================================="
echo " Google WiFi Network Diagnostics"
echo "========================================="
# 1. Check local gateway reachability
echo ""
echo "[1] Pinging Google WiFi router puck ($ROUTER_IP)..."
ping -c 10 $ROUTER_IP | tail -3
# 2. Check internet reachability (packet loss test)
echo ""
echo "[2] Pinging external DNS ($EXTERNAL_DNS) — 50 packets for packet loss %..."
ping -c 50 $EXTERNAL_DNS | tail -3
# 3. DNS resolution test
echo ""
echo "[3] DNS resolution test (resolving $EXTERNAL_HOST)..."
nslookup $EXTERNAL_HOST $EXTERNAL_DNS 2>&1 | grep -E "Address|Name|error"
# 4. Traceroute to identify where hops fail
echo ""
echo "[4] Traceroute to $EXTERNAL_DNS (first 10 hops)..."
traceroute -m 10 $EXTERNAL_DNS 2>/dev/null || tracepath -m 10 $EXTERNAL_DNS
# 5. Check current IP and default gateway
echo ""
echo "[5] Current network configuration..."
ip route show default 2>/dev/null || route -n get default 2>/dev/null || netstat -rn | grep default
echo ""
echo "[6] Your device IP on Google WiFi network..."
hostname -I 2>/dev/null || ipconfig getifaddr en0 2>/dev/null
# 6. MTU path discovery (helps identify packet fragmentation issues)
echo ""
echo "[7] Testing MTU size (fragmentation check)..."
ping -c 3 -M do -s 1472 $EXTERNAL_DNS 2>&1 | grep -E "bytes|error|frag"
# If this fails with 'frag needed', your MTU is set too high
# Fix: sudo ip link set eth0 mtu 1400
# 7. Speed indication via curl download
echo ""
echo "[8] Quick download speed indicator (100MB test file)..."
curl -o /dev/null --max-time 15 \
-w "Download speed: %{speed_download} bytes/sec\nTime total: %{time_total}s\n" \
"https://speed.cloudflare.com/__down?bytes=10000000" 2>/dev/null
# 8. Check DNS latency specifically
echo ""
echo "[9] DNS query latency (Google DNS)..."
for i in 1 2 3; do
time nslookup $EXTERNAL_HOST $EXTERNAL_DNS > /dev/null 2>&1
done
echo ""
echo "========================================="
echo " Diagnostics Complete"
echo " If packet loss > 2% to 8.8.8.8: ISP issue"
echo " If packet loss > 2% to 192.168.86.1: WiFi issue"
echo " If DNS fails: change DNS to 8.8.8.8 in Google Home app"
echo " If MTU test fails: try setting MTU to 1400"
echo "========================================="
# Bonus: Check if you're behind double-NAT
echo ""
echo "[10] Double-NAT detection..."
EXTERNAL_IP=$(curl -s https://api.ipify.org)
LOCAL_GATEWAY=$(ip route show default 2>/dev/null | awk '/default/{print $3}' || route -n get default 2>/dev/null | awk '/gateway:/{print $2}')
echo "Your external IP: $EXTERNAL_IP"
echo "Your local gateway: $LOCAL_GATEWAY"
echo "If gateway is 192.168.x.x AND external IP looks like 10.x/172.x/192.168.x, you may have Double-NAT"Error Medic Editorial
The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and network specialists with 10+ years of experience diagnosing infrastructure failures across consumer, enterprise, and cloud environments. We focus on practical, command-level troubleshooting guides that go beyond surface-level advice. Our network troubleshooting content covers everything from home mesh systems to carrier-grade routing.
Sources
- https://support.google.com/googlenest/answer/6246994
- https://support.google.com/googlenest/answer/9228237
- https://support.google.com/googlenest/answer/6240364
- https://support.google.com/googlenest/answer/9548693
- https://support.google.com/googlenest/thread/15498571
- https://www.reddit.com/r/GoogleWiFi/comments/common_issues_megathread