Why does Google WiFi keep dropping the connection every few minutes?

Frequent drops are usually caused by: (1) DHCP lease renewal failures between your ISP modem and Google WiFi — power cycle both in the correct order (modem first, then Google WiFi); (2) A mesh point losing backhaul signal — check if a specific point goes offline in the Google Home app and relocate it closer to the primary router; (3) 2.4 GHz interference — after rebooting, Google WiFi selects a new channel which may resolve interference-related drops; (4) ISP instability — test by connecting directly to your modem. If drops still occur, the problem is your ISP.

Why is Google WiFi so slow when my ISP plan is fast?

The most common causes of slow Google WiFi speeds are: (1) You are connected to the 2.4 GHz band instead of 5 GHz — move closer to a Google WiFi point or enable 'Prefer 5 GHz' in Google Home; (2) Wireless mesh backhaul is saturated — add an Ethernet cable between your primary router and mesh points for wired backhaul; (3) Double-NAT is occurring because your ISP modem is also in router mode — put your modem in bridge mode; (4) Your ISP is throttling your connection — test speed by connecting directly to the modem. Run a speed test in Google Home to isolate whether the problem is WAN or in-home WiFi.

Google WiFi shows 'Connected' but there is no internet access — how do I fix it?

This 'connected but no internet' state is most often a DNS failure or DHCP issue. Try these steps in order: (1) Power cycle your ISP modem and Google WiFi (modem first, wait 60 seconds, then Google WiFi); (2) In Google Home, go to WiFi → Settings → Advanced networking → DNS and set a custom DNS like 8.8.8.8; (3) Check if your ISP modem shows a valid WAN IP — log into the modem admin page and verify it has a public IP; (4) If your modem is also a router (showing 192.168.x.x as your WAN IP in Google Home), enable bridge mode on the modem; (5) As a last resort, factory reset your Google WiFi network and reconfigure it.

Why is my Google WiFi upload speed so slow compared to download?

Slow upload on Google WiFi can be caused by several factors: (1) Your ISP plan may have genuinely asymmetric speeds — many cable plans offer 500 Mbps down but only 20-50 Mbps up; verify your plan's upload speed with your ISP; (2) Double-NAT from having two routers in NAT mode significantly impacts upload — enable bridge mode on your ISP modem; (3) Other devices on the network saturating upload bandwidth with backups, P2P software, or video calls; (4) The Ethernet cable between your modem and Google WiFi may be faulty — try a Cat6 replacement cable; (5) If using wireless backhaul between mesh points, the 5 GHz band used for backhaul may be congested — switch to wired Ethernet backhaul.

How do I fix a Google WiFi mesh point that won't connect to the network?

If a mesh point shows offline or won't join: (1) Ensure it is within range — no more than 2 rooms or 30-40 feet from another point or the primary router, with minimal wall obstructions; (2) Unplug and re-plug the offline mesh point and wait 2-3 minutes; (3) Check the Google Home app for the exact error — a pulsing yellow light means it cannot reach the primary router, while red indicates hardware failure; (4) Factory reset the individual mesh point by holding its reset button for 10 seconds until the light flashes orange, then re-add it in Google Home under WiFi → Add → Add another device; (5) If it still fails, try placing the mesh point in a different outlet closer to the primary router to verify it works at shorter range, then optimize placement.

Google WiFi Not Working, Slow, or Dropping Connections: Complete Troubleshooting Guide

Fix Google WiFi not working, slow speeds, dropped connections, and no internet access. Step-by-step troubleshooting with real commands and solutions.

Last updated: February 27, 2026

Last verified: February 27, 2026

2,939 words

Key Takeaways

Google WiFi dropping connections or showing 'No Internet' is most often caused by ISP-side DHCP lease failures, DNS misconfiguration, or mesh node placement issues causing poor backhaul signal.
Slow Google WiFi speeds (upload or download) frequently stem from QoS throttling, WAN port negotiation issues, interference on the 5 GHz band used for mesh backhaul, or outdated firmware.
Most Google WiFi issues can be resolved in order: restart the primary router first, then mesh points, check ISP modem status, verify DNS settings (switch to 8.8.8.8), and factory reset as a last resort — all manageable within the Google Home app.

Google WiFi Fix Approaches Compared
Method	When to Use	Time	Risk
Power cycle primary router + mesh points	First response to any outage or slowdown	2-5 min	None
Change DNS to 8.8.8.8 / 1.1.1.1	Connected but no internet, slow browsing, DNS errors	3 min	Very Low
Relocate mesh points	Dropping connections, slow mesh backhaul	10-30 min	None
Change WiFi channel / band steering	Slow speeds, interference from neighbors	5 min	Low
Update Google WiFi firmware	Persistent bugs, known issues, packet loss	5-15 min	Low
Factory reset individual mesh node	Node offline, won't rejoin mesh	10 min	Medium — loses config
Factory reset entire network	Corrupted config, persistent 'No Internet'	20-40 min	High — full reconfigure
Replace ISP modem/router in bridge mode	Double-NAT issues, slow WAN throughput	30-60 min	Medium
Check for ISP outage	Total outage, no fix working	5 min	None

Understanding Google WiFi Problems

Google WiFi (and its successor Google Nest WiFi) uses a mesh networking architecture where one unit acts as the primary router connected to your ISP modem, and additional points extend coverage wirelessly or via Ethernet backhaul. This architecture introduces several unique failure modes beyond a traditional single router setup.

Common symptoms include:

"No internet" or "Connected, no internet" in device status bars
Devices disconnecting and reconnecting repeatedly
Upload speed significantly slower than download
Mesh points showing as offline in the Google Home app
Speed test results far below your ISP plan speeds
Packet loss causing lag in gaming or video calls
Google WiFi Pause feature not working as expected

Step 1: Confirm the Problem Scope

Before diving into fixes, narrow down whether the issue is with your ISP, your primary router, or the mesh network.

Check ISP first:

Bypass Google WiFi entirely — connect your computer directly to the ISP modem via Ethernet.
If you still have no internet or slow speeds, the problem is upstream (call your ISP).
If the direct connection works fine, the issue is within your Google WiFi setup.

Check the Google Home app:

Open Google Home → tap your WiFi network → look for error banners.
If a mesh point shows a yellow or red indicator, it has lost its backhaul connection to the primary router.
Navigate to WiFi → Devices to see which devices are connected and their signal strength.

Run a speed test from the Google Home app:

Go to WiFi → Run speed test — this tests WAN speed at the primary router, ruling out in-home WiFi as the bottleneck.
Then run a speed test from a device over WiFi (use fast.com or speedtest.net). A large gap means your in-home WiFi, not your ISP, is the problem.

Step 2: Power Cycle in the Correct Order

This resolves the majority of Google WiFi issues including DHCP lease failures and mesh connection drops.

Unplug your ISP modem (and any separate ISP router) — wait 60 seconds.
Unplug your Google WiFi primary router — wait 30 seconds.
Unplug all Google WiFi mesh points — wait 30 seconds.
Plug in your ISP modem first — wait until all status lights are solid (1-3 minutes).
Plug in Google WiFi primary router — wait until its light is solid white (up to 2 minutes).
Plug in mesh points one at a time — each should glow solid white within 2 minutes.

If a mesh point pulses white or shows amber/yellow after 3 minutes, it cannot find the primary router's signal — see Step 5.

Step 3: Fix "Connected But No Internet" Errors

This is the most reported Google WiFi issue. The device connects to the WiFi network but cannot reach the internet. Common causes:

A. DNS Resolution Failure Google WiFi uses its own DNS proxy by default. If this fails, you'll see "No Internet" even though your WAN connection is live.

Fix: Change DNS servers on your network.

Open Google Home → WiFi → Settings (gear icon) → Advanced networking → DNS.
Switch from "Automatic" to custom DNS: 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare).
Save and restart your network.

B. Double-NAT (Two Routers in NAT mode) If your ISP modem is also a router (common with cable and DSL providers), Google WiFi may receive a private IP address like 192.168.1.x instead of a public IP. This causes connectivity issues and severely impacts upload speeds.

Fix:

Log into your ISP modem's admin panel (usually 192.168.100.1 or printed on the modem).
Enable Bridge Mode or IP Passthrough to let Google WiFi handle all NAT.
Alternatively, in Google Home go to WiFi → Settings → Advanced networking → WAN and switch to PPPoE if your ISP uses it, or verify DHCP settings.

C. DHCP Lease Failure Google WiFi may fail to obtain an IP from your ISP. In the Google Home app this sometimes shows as "WAN IP: 0.0.0.0" or no WAN IP listed.

Fix: Power cycle (Step 2). If the issue persists, call your ISP — they may need to release/renew your modem's MAC address registration.

Step 4: Fix Slow Google WiFi Speeds

A. Check band assignment Google WiFi uses 2.4 GHz for longer range and 5 GHz for faster speeds. Band steering is automatic, but nearby interference can force devices onto 2.4 GHz.

In Google Home, enable "Prefer 5 GHz" — this encourages capable devices to use the faster band.

B. Mesh backhaul congestion Google WiFi uses the 5 GHz band for both client connections AND mesh backhaul between nodes by default (wireless backhaul). Heavy wireless use can saturate the backhaul channel.

Fix — Use Ethernet backhaul:

Run an Ethernet cable between your Google WiFi primary router and each mesh point.
Google WiFi automatically detects and prefers wired backhaul, freeing the 5 GHz band entirely for client devices.
This alone can triple effective mesh throughput.

C. Slow upload speed specifically Slow upload on Google WiFi is frequently caused by:

Asymmetric ISP plan — confirm your plan's upload speed with ISP.
QoS (Quality of Service) prioritization — Google WiFi does not currently expose manual QoS controls; heavy downloads from other devices can eat upload bandwidth.
Double-NAT — resolve as described in Step 3B.
Half-duplex WAN port negotiation — in rare cases the WAN port negotiates incorrectly with certain modems. Try a different Ethernet cable between modem and Google WiFi.

D. Interference and channel selection Google WiFi selects channels automatically but can pick crowded channels.

Use a WiFi analyzer app (e.g., WiFi Analyzer on Android) to see which 2.4 GHz and 5 GHz channels are most congested in your area.
Google WiFi does not allow manual channel selection through the consumer app; however, channels are re-evaluated after each restart, so rebooting can trigger a better channel selection.

Step 5: Fix Mesh Points Not Connecting

"Google WiFi mesh not working" — node shows offline in Google Home:

Check distance — mesh points should be no more than 2 rooms or ~40 feet from the primary router or another mesh point. Walls, especially concrete or brick, dramatically reduce signal.
Avoid interference — keep mesh points away from microwaves, baby monitors, cordless phones, and other 2.4 GHz devices.
Factory reset the individual mesh point:
- Unplug the mesh point.
- Hold the reset button (small hole on the bottom) while plugging back in.
- Hold for ~10 seconds until the light flashes orange/amber, then release.
- Re-add it in Google Home: WiFi → Add → Add another device.
Check for firmware updates in Google Home: Settings → Nest WiFi → Software version — updates are automatic but can be forced by rebooting the network.

Step 6: Fix Google WiFi Pause Not Working

The Pause feature in Google Home stops internet access for specific devices or family groups. If Pause is not working:

Devices connected via Ethernet directly to a Google WiFi point may bypass the Pause function — ensure devices use WiFi only.
Devices with static IPs (manually assigned) can sometimes bypass Pause; ensure DHCP is used.
The Pause feature only blocks internet, not local network traffic. The device will still appear connected to WiFi.
Sign out and back into Google Home app, as authentication token expiry can cause control failures.
If a device still accesses the internet while paused, check if it has a cellular connection or is using a VPN.

Step 7: Factory Reset as Last Resort

If all other steps fail and Google WiFi shows persistent errors, a full factory reset may be required.

To factory reset the entire network:

In Google Home: go to WiFi → Settings → Factory reset network.
Confirm the reset. All points will reset simultaneously.
After reset, set up your network fresh in Google Home.

To factory reset a single point manually:

With the unit powered on, hold the reset button for 10+ seconds until the light flashes and pulses orange, then white.

Step 8: Check for Known Firmware Bugs and Packet Loss

Google periodically releases firmware updates that fix packet loss and stability issues. Packet loss manifests as:

Games feeling laggy despite fast speeds
Video calls freezing or dropping
Speed tests showing inconsistent results

Diagnose packet loss using the commands in the code block section. If packet loss exceeds 1-2%, restart your network. If it persists after restart and bypassing Google WiFi eliminates the packet loss, contact Google support for RMA evaluation of a potentially defective unit.

Frequently Asked Questions

bash

#!/usr/bin/env bash
# Google WiFi Diagnostic Script
# Run on any Mac or Linux machine connected to your Google WiFi network

echo "=== Google WiFi Network Diagnostics ==="
echo ""

# 1. Check your current IP address and gateway (should be 192.168.86.1 for Google WiFi default)
echo "--- Local IP and Gateway ---"
if [[ "$OSTYPE" == "darwin"* ]]; then
  # macOS
  ifconfig en0 | grep inet
  netstat -rn | grep default
else
  # Linux
  ip addr show | grep 'inet '
  ip route show default
fi
echo ""

# 2. Ping the Google WiFi primary router (default gateway is usually 192.168.86.1)
GATEWAY="192.168.86.1"
echo "--- Ping Primary Router ($GATEWAY) ---"
ping -c 10 $GATEWAY
echo ""

# 3. Test DNS resolution
echo "--- DNS Resolution Test ---"
nslookup google.com 8.8.8.8
nslookup google.com 1.1.1.1
nslookup google.com $GATEWAY
echo ""

# 4. Trace route to internet (identifies where packets are dropping)
echo "--- Traceroute to 8.8.8.8 (Google DNS) ---"
if [[ "$OSTYPE" == "darwin"* ]]; then
  traceroute -n 8.8.8.8
else
  traceroute -n 8.8.8.8
fi
echo ""

# 5. Packet loss test (send 100 pings, look for loss > 1%)
echo "--- Packet Loss Test (100 pings to 8.8.8.8) ---"
ping -c 100 8.8.8.8 | tail -3
echo ""

# 6. MTR for continuous path analysis (install with: brew install mtr OR apt install mtr)
echo "--- MTR Path Analysis (requires mtr installed) ---"
if command -v mtr &> /dev/null; then
  mtr --report --report-cycles 30 --no-dns 8.8.8.8
else
  echo "MTR not installed. Install with: brew install mtr (Mac) or sudo apt install mtr (Linux)"
fi
echo ""

# 7. Speed test via CLI (requires speedtest-cli: pip install speedtest-cli)
echo "--- Speed Test (requires speedtest-cli) ---"
if command -v speedtest-cli &> /dev/null; then
  speedtest-cli --simple
elif command -v speedtest &> /dev/null; then
  speedtest
else
  echo "Install speedtest-cli: pip3 install speedtest-cli"
fi
echo ""

# 8. Check for DHCP lease info
echo "--- DHCP Lease Info ---"
if [[ "$OSTYPE" == "darwin"* ]]; then
  ipconfig getpacket en0 2>/dev/null | grep -E 'ip_address|server_identifier|lease_time|domain_name'
else
  cat /var/lib/dhcp/dhclient.leases 2>/dev/null | grep -E 'fixed-address|dhcp-server|dhcp-lease-time' | head -10
fi
echo ""

# 9. WiFi signal strength (Mac only)
if [[ "$OSTYPE" == "darwin"* ]]; then
  echo "--- WiFi Signal Strength (RSSI) ---"
  /System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport -I | grep -E 'agrCtlRSSI|channel|SSID|lastTxRate'
  echo "Note: RSSI above -70 dBm is good; below -80 dBm causes drops"
fi
echo ""

# 10. Check if connected to correct band (2.4 vs 5 GHz by channel)
if [[ "$OSTYPE" == "darwin"* ]]; then
  echo "--- Band Detection (channel > 13 = 5GHz) ---"
  CHANNEL=$(/System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport -I | grep channel | awk '{print $2}' | cut -d, -f1)
  if [ "$CHANNEL" -gt 13 ] 2>/dev/null; then
    echo "Connected to 5 GHz band (Channel $CHANNEL) — Good for speed"
  else
    echo "Connected to 2.4 GHz band (Channel $CHANNEL) — May be slow; move closer to a WiFi point"
  fi
fi

echo ""
echo "=== Diagnostics Complete ==="
echo "If packet loss > 1%, restart your Google WiFi network."
echo "If traceroute shows loss at hop 1 (192.168.86.1), the issue is in-home WiFi."
echo "If loss starts at hop 2+, the issue is your ISP or beyond."

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers, SREs, and network administrators with 10+ years of experience diagnosing home and enterprise networking issues. We specialize in translating complex network troubleshooting into clear, actionable steps for both technical and non-technical users. Our guides are tested against real hardware before publication.

Sources

Explore More wifi Guides

"Connected Without Internet" Error: Complete Fix Guide for Wi-Fi, Routers, Android & ISP Issues

Fix the "Connected Without Internet" error on Wi-Fi, Android, hotspots & routers. Step-by-step commands for Cox, CenturyLink, Frontier, T-Mobile & more.

"Connected Without Internet" Error: Complete Fix Guide for WiFi, Routers, Android & ISP Issues

Fix the 'connected without internet' error on WiFi, Android, hotspots & ISPs like Cox, CenturyLink & Fios. Step-by-step commands and solutions inside.

"Connected Without Internet" Error: What It Means and How to Fix It (All Devices & ISPs)

Fix the 'Connected Without Internet' WiFi error on Android, router, hotspot, Cox, CenturyLink, Fios & more. Step-by-step commands and solutions inside.