Why does Google WiFi show 'connected but no internet'?

This means your devices can reach the Google WiFi router but Google WiFi itself cannot reach the internet. The most common causes are: (1) modem not fully synced — power-cycle the modem and wait 2 full minutes; (2) ISP outage — check your ISP's status page; (3) DNS failure — try setting your DNS manually to 1.1.1.1 in the Google Home advanced networking settings; (4) double-NAT — your modem is in router mode, and Google WiFi received a private WAN IP. Put the modem in bridge mode to resolve double-NAT.

Why is my Google WiFi so slow on upload but fast on download?

Asymmetric speed issues are often caused by: (1) a known firmware bug in certain Google Nest WiFi Pro versions — check for updates in Google Home app; (2) QoS settings deprioritizing upload traffic — check no device is set to 'High priority' in Google Home; (3) ISP plan asymmetry (common with cable/DSL plans); (4) wireless interference on the 5 GHz uplink band. Try running the mesh speed test in the Google Home app to see if the bottleneck is the ISP link or an inter-node backhaul link. If a specific node shows poor upload, move it closer to the primary point or use an ethernet backhaul connection.

Why does Google WiFi keep dropping connection every few hours?

Periodic drops (every 2–8 hours) most commonly indicate DHCP or IPv6 lease renewal failures. Disable IPv6 in Google Home app → WiFi → Advanced networking → IPv6 off. Also check if your ISP has a known IPv6 routing issue. Other causes: power-saving mode on the WiFi adapter of affected devices (disable 'Allow the computer to turn off this device to save power' in Windows Device Manager → Network adapters), or a firmware bug — update via Google Home app. If nodes use ethernet backhaul, test the cable with ethool or replace it.

How do I fix Google WiFi mesh not working (secondary node showing offline)?

When a mesh node shows offline: (1) Unplug the offline node, wait 30 seconds, re-plug it — allow 3 minutes for it to reconnect; (2) Check the LED: pulsing white = connecting, solid white = healthy, solid orange = no mesh connection; (3) Move the node within 15 meters of the primary or another healthy node; (4) In Google Home app, tap the offline node → Factory reset, then re-add it to your network; (5) If using ethernet backhaul, swap the cable or try a different switch port. Run 'ethool ethX' on a connected device to verify the port is at 1000 Mbps full duplex.

Google WiFi speed test in the app shows fast but devices are slow — why?

The in-app speed test measures the Google WiFi router's connection to the internet via ethernet — it bypasses WiFi entirely for that measurement. If the app shows fast speeds but devices are slow, the bottleneck is the wireless link between your device and the nearest Google WiFi node. Solutions: (1) move the device closer to a node; (2) run an actual device-side speed test at fast.com or speedtest.net; (3) check for 2.4 GHz vs 5 GHz band assignment — enable 5 GHz preference on the device; (4) check for interference using a WiFi analyzer app; (5) limit active devices or check if one device is consuming all bandwidth via Google Home device usage stats.

Google WiFi Not Working: Complete Troubleshooting Guide for No Internet, Slow Speeds & Dropping Connections

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

Last updated: February 27, 2026

Last verified: February 27, 2026

2,714 words

Key Takeaways

Root Cause 1: ISP outage or modem misconfiguration — Google WiFi cannot create internet if the upstream connection is down or the modem is handing out a double-NAT IP.
Root Cause 2: Mesh node placement or interference — nodes placed too far apart, behind thick walls, or near 2.4 GHz appliances cause packet loss, slow speeds, and dropped connections.
Root Cause 3: Firmware bugs or corrupted device state — outdated firmware or a stuck DHCP lease can produce 'connected but no internet' errors even when the ISP link is healthy.
Root Cause 4: DNS misconfiguration or IPv6 conflicts — Google WiFi defaulting to Google DNS (8.8.8.8) can conflict with ISP-side DNS requirements, causing no-internet symptoms.
Quick Fix Summary: Power-cycle modem → reboot primary Google WiFi point → check Google Home app for firmware updates → run a speed test from the app → factory reset as a last resort.

Fix Approaches Compared
Method	When to Use	Time	Risk
Power-cycle modem + primary point	First step for any outage or no-internet symptom	2–5 min	None
Reboot all mesh nodes via Google Home app	Nodes show offline or mesh not working	3–5 min	None
Move mesh node closer / change channel	Slow speed, packet loss, dropping connections	10–20 min	Low
Change DNS to 1.1.1.1 or ISP DNS	Connected but no internet, very slow DNS lookups	5 min	Low
Disable IPv6 on primary point	IPv6 conflicts causing intermittent drops	5 min	Low
Update Google WiFi firmware manually	Known firmware bug causing drops or slow upload	10 min	Low
Factory reset primary point	Corrupted config, setup issues, persistent no-internet	20–30 min	High — loses all settings
Replace with bridge mode modem	Double-NAT causing packet loss or VPN failures	30–60 min	Medium
Run Google WiFi mesh speed test in app	Diagnosing which node is the bottleneck	5 min	None
Contact ISP + verify modem firmware	All local fixes exhausted, upstream issue suspected	30–90 min	None

Understanding Why Google WiFi Stops Working

Google WiFi (and its successor, Google Nest WiFi) uses a mesh architecture where one device acts as the primary router connected to your modem, and additional points extend coverage wirelessly or via ethernet backhaul. When something breaks in this chain — the ISP link, the modem handoff, the mesh backhaul, or the device firmware — you get symptoms ranging from 'No internet access' to painfully slow upload speeds.

Common error states you may see in the Google Home app or on connected devices:

'No internet' banner in the Google Home app
'Connected, no internet' on Android/Windows devices
'This site can't be reached' in browsers despite WiFi showing connected
Speed tests showing <1 Mbps when your plan is 300+ Mbps
Mesh node showing 'Offline' in Google Home app
Packet loss warnings in gaming or video call apps

Phase 1: Isolate the Problem Layer

Before touching any Google WiFi setting, determine where the failure lives.

Step 1: Check your ISP link directly

Plug a laptop directly into your modem via ethernet and run:

curl -I https://www.google.com
ping -c 10 8.8.8.8
traceroute 8.8.8.8

If this also fails, the problem is upstream (ISP or modem). Call your ISP or reboot the modem before touching Google WiFi.

Step 2: Check what IP your primary Google WiFi point is receiving

Log into the Google Home app → select your WiFi network → tap the gear icon → Network info. The WAN IP shown should be a public IP (e.g., 203.x.x.x) not a private 192.168.x.x or 10.x.x.x. A private WAN IP means your modem is in router mode, creating double-NAT — a common cause of slow speeds and VPN/game failures.

Fix for double-NAT: Put your modem into bridge mode (consult your ISP/modem manual). This passes the public IP directly to Google WiFi.

Phase 2: Fix 'Google WiFi Not Connecting to Internet'

Step 1: Power-cycle in the correct order

Unplug your modem (and its battery backup if present).
Unplug the primary Google WiFi point.
Unplug all secondary mesh nodes.
Wait 60 seconds — this clears DHCP leases and ARP caches.
Plug in the modem. Wait for it to fully sync (all lights stable, ~2 minutes).
Plug in the primary Google WiFi point. Wait for it to show solid white.
Plug in secondary nodes one by one.

Step 2: Release and renew DHCP lease on the primary point

Google WiFi does not expose a shell by default, but you can force a DHCP renewal by disabling and re-enabling the WAN connection:

Google Home app → WiFi settings → Network & general → turn off, wait 30 seconds, turn on.

Alternatively, connect a device via ethernet to a LAN port and verify it gets an IP in the 192.168.86.x range (Google WiFi's default subnet).

Step 3: Check DNS

Google WiFi uses 8.8.8.8 and 8.8.4.4 by default. Some ISPs block or throttle external DNS. Test by temporarily switching your device's DNS manually:

On Windows: ncpa.cpl → adapter properties → IPv4 → set DNS to 1.1.1.1
On Mac: System Settings → Network → DNS → add 1.1.1.1

If the internet works after changing device DNS, the fix is to configure custom DNS in Google Home: Google Home app → WiFi → Settings → Advanced networking → DNS → enter 1.1.1.1 (Cloudflare) or your ISP's DNS.

Phase 3: Fix Google WiFi Slow Speed & Slow Upload

Slow speeds are the most reported Google WiFi complaint. Attack them systematically:

Step 1: Run the in-app mesh speed test

Google Home app → WiFi → Run speed test. Note which node shows poor speed. The app also shows the speed between nodes (backhaul speed). If a node shows <50 Mbps backhaul but your plan is 300 Mbps, that node is the bottleneck.

Step 2: Check wireless interference

Google WiFi automatically selects channels but does not always make the optimal choice. Install a WiFi analyzer app (e.g., WiFi Analyzer on Android) and check:

Overlapping 2.4 GHz channels (use only 1, 6, or 11)
Neighboring networks on the same 5 GHz channel
Microwave ovens, baby monitors, and cordless phones near nodes

Step 3: Optimize node placement

For reliable mesh, each node should:

Be within 15–20 meters (50–65 ft) line of sight of the next node
Avoid thick concrete/brick walls between nodes
Be elevated (countertop, bookshelf) rather than on the floor
Have a clear path with no metal objects directly adjacent

Step 4: Force 5 GHz connection for speed-sensitive devices

Google WiFi uses band steering but sometimes parks devices on 2.4 GHz. You cannot manually split bands in the standard UI, but you can:

Enable 'Prefer 5 GHz' in device WiFi settings (Android/Windows)
Temporarily disable 2.4 GHz by creating a guest network as a 2.4-GHz-only decoy — not ideal, but effective for testing

Step 5: Check for QoS or device priority conflicts

Google Home app → WiFi → Devices — ensure no device is set to high priority accidentally, starving other devices.

Phase 4: Fix Google WiFi Dropping Connections

Step 1: Check for IPv6 conflicts

IPv6 mismatches between your ISP and Google WiFi cause intermittent drops every few hours as IPv6 lease renewal fails and the device falls back to IPv4. To disable IPv6 on Google WiFi:

Google Home app → WiFi → Settings → Advanced networking → IPv6 → toggle off

Monitor for 24 hours. If drops stop, your ISP has a known IPv6 routing issue.

Step 2: Check ethernet backhaul

If nodes are connected via ethernet, a faulty cable causes repeated drops with the node cycling online/offline. Test by:

ethool eth0   # run on a device connected to the suspect switch port
# Look for: Link detected: yes, Speed: 1000Mb/s, Duplex: Full
# Speed: 100Mb/s or half-duplex indicates a bad cable or port

Replace the cable or try a different switch port.

Step 3: Update firmware

Google WiFi firmware updates automatically, but updates can stall. Force a check:

Google Home app → tap your home → Settings → Updates → check for updates

Known firmware versions with dropping issues (documented in community forums):

8324.176.x — caused mesh instability (fixed in 8324.180+)
11568.x series — slow upload bug on Nest WiFi Pro

Phase 5: Factory Reset (Last Resort)

If all else fails — especially for persistent 'no internet' or setup issues:

Press and hold the reset button on the bottom of the primary point for 10 seconds until the light pulses orange.
Wait for the device to restart (~3 minutes).
Re-run setup via Google Home app as a new network.
Re-add secondary nodes one at a time.

Warning: This erases all WiFi names, passwords, port forwarding rules, and device labels.

Phase 6: Advanced — Google WiFi Pause Not Working

If the 'Pause' feature in Google Home isn't blocking internet for a device:

Ensure the device is using Google WiFi as its DHCP server (not a secondary router).
Check if the device has a static IP outside the Google WiFi DHCP range — pause targets DHCP-assigned IPs.
Verify the Google Home app is updated to the latest version.
Pause works at Layer 3 (IP blocking), so a device with a VPN app active may bypass it — disable VPN on the device to test.

Phase 7: Persistent Packet Loss Investigation

Use mtr (Matthew's Traceroute) for ongoing packet loss diagnosis — this reveals whether loss is inside your network or at the ISP:

mtr --report --report-cycles 60 8.8.8.8

If loss appears at hop 1 (your router gateway 192.168.86.1), the issue is local (WiFi signal, interference, or firmware). If loss first appears at hop 2 or 3 (ISP infrastructure), escalate to your ISP with the MTR report.

Frequently Asked Questions

bash

#!/usr/bin/env bash
# Google WiFi Diagnostic Script
# Run on a laptop/desktop connected to Google WiFi (wired or wireless)
# Requires: ping, curl, traceroute/tracert, mtr (optional), nslookup

echo "====================================="
echo " Google WiFi Network Diagnostic Tool"
echo "====================================="

# 1. Show current IP and gateway (should be 192.168.86.1 for Google WiFi)
echo ""
echo "[1] Local Network Info:"
if [[ "$OSTYPE" == "darwin"* ]]; then
  ipconfig getifaddr en0
  netstat -rn | grep default | head -3
else
  ip addr show | grep 'inet ' | grep -v '127.0.0.1'
  ip route | grep default
fi

# 2. Ping Google WiFi primary point (default gateway)
GATEWAY="192.168.86.1"
echo ""
echo "[2] Pinging Google WiFi primary point ($GATEWAY):"
ping -c 5 $GATEWAY

# 3. Check ISP DNS resolution
echo ""
echo "[3] DNS Resolution Test:"
nslookup google.com 8.8.8.8
nslookup google.com 1.1.1.1

# 4. Traceroute to internet (first 5 hops)
echo ""
echo "[4] Traceroute (first 5 hops to 8.8.8.8):"
if command -v traceroute &>/dev/null; then
  traceroute -m 5 8.8.8.8
elif command -v tracert &>/dev/null; then
  tracert -h 5 8.8.8.8
fi

# 5. MTR report for packet loss (60 cycles)
echo ""
echo "[5] MTR Packet Loss Report (60 cycles to 8.8.8.8):"
if command -v mtr &>/dev/null; then
  mtr --report --report-cycles 60 8.8.8.8
else
  echo "mtr not installed. Install with: sudo apt install mtr / brew install mtr"
  echo "Falling back to extended ping:"
  ping -c 60 8.8.8.8 | tail -5
fi

# 6. Check WAN IP type (public vs private = double-NAT indicator)
echo ""
echo "[6] External/WAN IP Check:"
WAN_IP=$(curl -s https://api.ipify.org)
echo "Your public IP as seen from internet: $WAN_IP"
# Get gateway IP reported by router
GW_IP=$(ip route | grep default | awk '{print $3}' | head -1)
echo "Your local gateway: $GW_IP"
# If GW_IP starts with 10., 172.16-31., or 192.168. AND WAN_IP is different, that's expected
# But if Google WiFi WAN IP (check in app) is ALSO private, you have double-NAT
echo "ACTION: In Google Home app, check WiFi > Network info > WAN IP."
echo "If WAN IP is 10.x.x.x or 192.168.x.x, you have double-NAT. Put modem in bridge mode."

# 7. Speed test via curl (rough bandwidth estimate)
echo ""
echo "[7] Rough Download Speed Test (100MB file from Cloudflare):"
curl -o /dev/null --max-time 15 -w "Download speed: %{speed_download} bytes/sec\n" \
  https://speed.cloudflare.com/__down?bytes=100000000

# 8. Check for DNS latency
echo ""
echo "[8] DNS Latency Comparison:"
for DNS in 8.8.8.8 1.1.1.1 9.9.9.9; do
  TIME=$(dig @$DNS google.com | grep 'Query time' | awk '{print $4}')
  echo "  DNS $DNS query time: ${TIME} ms"
done

echo ""
echo "====================================="
echo " Diagnostic complete."
echo " Share this output with your ISP or"
echo " Google support for faster resolution."
echo "====================================="

Error Medic Editorial

The Error Medic Editorial team consists of senior DevOps engineers, network administrators, and SREs with 10+ years of experience diagnosing and resolving infrastructure and consumer networking issues. We specialize in translating complex network failure modes into clear, actionable troubleshooting guides. All 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.