eero WiFi Not Working: Complete Troubleshooting Guide for 'Connected But No Internet' and Slow Speed Issues
Fix eero WiFi not working, slow speeds, and 'connected but no internet' errors. Step-by-step guide covering eero 6, Pro 6, mesh, and extender issues.
- Root Cause 1: ISP outage or modem misconfiguration — eero shows 'connected but no internet' when upstream connectivity fails, not the eero device itself.
- Root Cause 2: DHCP conflicts, DNS resolution failures, or stale IP leases cause eero to report 'we found an issue' or 'can't find internet' even with valid hardware.
- Root Cause 3: Firmware bugs on eero 6 and eero Pro 6 (particularly versions 6.x) cause random disconnects, slow speeds, and beacon pairing failures.
- Root Cause 4: Overheating due to poor ventilation throttles eero throughput by up to 60%, mimicking a slow internet connection.
- Quick Fix Summary: Power-cycle modem first, then eero gateway, then satellite nodes in order. If speeds remain slow, run a speed test wired directly to modem to isolate the source. Factory reset only as last resort after checking ISP status and firmware version.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Power-cycle modem + eero gateway | First step for any connectivity loss or slow speed | 2–5 min | None |
| eero App Network Restart | Quick restart without physical access to hardware | 1–3 min | None |
| Change DNS servers (8.8.8.8 / 1.1.1.1) | eero connected but no internet, slow browsing despite good speed test | 3 min | Low |
| Disable IPv6 on eero | eero 6 or Pro 6 dropping WiFi intermittently | 2 min | Low |
| Change eero band (force 2.4 GHz or 5 GHz) | Specific device connectivity issues, 2.4 GHz not working | 5 min | Low |
| Update eero firmware manually via app | eero 6 'we found an issue', known firmware bug | 10–15 min | Low |
| Factory reset single eero node | Beacon not connecting, extender not working after all else fails | 15–20 min | Medium — loses node config |
| Factory reset entire eero network | Persistent mesh not working, setup problems, corruption | 30–45 min | High — loses all settings |
| Replace Ethernet cable (modem to eero) | Wired connection slow or not working, eero won't connect to modem | 5 min | None |
| Contact ISP for modem replacement or provisioning reset | Modem-side DHCP failure, eero can't find internet after all local fixes | 20–60 min | None |
Understanding eero WiFi Not Working
The eero mesh system consists of a gateway node (connected to your modem) and one or more satellite nodes (beacons or additional eeros). When something goes wrong, the failure can occur at any layer: the ISP connection, the modem, the Ethernet link between modem and eero, the eero firmware, the mesh backhaul, or the client device itself.
Common error messages you may see in the eero app or on indicator lights include:
"We found an issue with your network""eero can't find the internet""eero Pro 6 can't reach the internet""eero is connected but has no internet access"(shown on client devices)- Solid white light (normal), blinking white (setup mode), blinking red (no internet), solid red (hardware fault)
Step 1: Diagnose the Layer of Failure
Before touching any eero hardware, identify where the problem lives.
1a. Check ISP Status Visit your ISP's outage page or use Downdetector (downdetector.com) to confirm no regional outage. If your ISP is down, no amount of eero troubleshooting will restore internet.
1b. Bypass eero — Connect Directly to Modem Plug a laptop directly into your modem via Ethernet. If internet works, the modem is fine and the eero is the problem. If internet fails here too, the issue is upstream (ISP or modem).
1c. Check eero LED Indicators
- Solid white = gateway is online and healthy
- Blinking blue = pairing/setup mode
- Blinking white = booting
- Blinking red / solid red = no internet or hardware error
- No light = not receiving power
1d. Open the eero App Navigate to Settings > Network > Health. The app will show which node in your mesh is experiencing issues and whether the problem is with the WAN connection or an individual satellite node.
Step 2: Fix — Power Cycle in Correct Order
A sequential power cycle resolves the majority of eero connectivity and slow-speed issues by forcing fresh DHCP lease acquisition and clearing stale ARP/routing tables.
- Unplug your modem (and modem/router combo if applicable). Wait 60 seconds — not 10, not 30. Sixty full seconds allows DRAM to clear and the ISP CMTS to drop your session.
- Unplug your eero gateway (the one connected to the modem via Ethernet).
- Unplug all satellite eero nodes and beacons.
- Plug in the modem first. Wait for it to fully sync — all indicator lights stable, typically 60–120 seconds.
- Plug in the eero gateway. Wait for its LED to turn solid white (up to 2 minutes).
- Plug in satellite nodes one at a time, waiting for each to show solid white before adding the next.
Step 3: Fix eero Slow Speeds
If eero reconnects but speeds are significantly below your subscribed plan, work through these in order:
3a. Run a Layered Speed Test
- Speed test wired directly to modem → baseline ISP speed
- Speed test wired to eero gateway LAN port → measures eero WAN processing overhead
- Speed test on 5 GHz WiFi close to gateway → measures radio performance
- Speed test on 2.4 GHz or at edge of mesh → measures backhaul and range
If wired-to-modem speed matches your plan but wired-to-eero is slow, the bottleneck is the eero hardware or its Ethernet cable. Replace the Cat5e/Cat6 cable between modem and eero.
3b. Check for eero Overheating eero devices throttle their radios when internal temperature exceeds safe thresholds. Signs include: device too hot to touch comfortably, speeds that start fast then degrade, poor performance in enclosed spaces. Ensure eero has 6+ inches of clearance on all sides, is not in a cabinet or entertainment center, and is not stacked on other electronics. A 10°C reduction in ambient temperature can restore 40–60% of lost throughput.
3c. Change DNS Servers In the eero app: Settings > Network Settings > DNS. Switch from automatic (ISP DNS) to:
- Cloudflare:
1.1.1.1/1.0.0.1 - Google:
8.8.8.8/8.8.4.4
This resolves the "eero connected but no internet" symptom caused by DNS resolution failures while IP connectivity exists.
3d. Disable IPv6 (eero 6 and Pro 6 Specific) A documented firmware bug affects IPv6 on eero 6 and eero Pro 6, causing intermittent drops and slow speeds. In the eero app: Settings > Troubleshooting > Advanced Settings > IPv6 → toggle off. Reboot the network afterward.
3e. Check for Interference on 2.4 GHz If eero 2.4 GHz is not working or slow: neighboring networks on channels 1, 6, or 11 may be congested. eero uses automatic channel selection, but you can improve performance by enabling eero Labs > Band Steering in the app, which pushes capable devices to 5 GHz automatically.
Step 4: Fix eero Beacon / Satellite Not Connecting
If a specific node shows offline in the eero app:
- Confirm the offline node has power (LED behavior as described above).
- Move the node physically closer to the gateway temporarily — if it connects, it was too far away or had too many obstructions for reliable mesh backhaul.
- In the eero app, tap the offline device → Restart. Wait 3 minutes.
- If it remains offline, hold the reset button on the back of that node for 7 seconds (LED flashes yellow) for a soft reset — this resets network config but keeps the device in your account.
- For a full factory reset of just that node: hold the reset button for 15 seconds until LED flashes red. You will need to re-add it through the app.
Step 5: Fix eero Won't Connect to Modem
When the eero app shows the gateway cannot reach the modem or you see "eero can't find internet":
- Confirm the Ethernet cable is plugged into the modem's LAN port, not a WAN/uplink port.
- Check if your modem requires MAC address cloning — some ISPs lock to the first registered MAC. Log into modem admin UI (typically
192.168.100.1) and clone the eero's MAC if required, or call ISP to register the new device. - Put modem into bridge mode if it is a modem/router combo — double NAT (eero behind router behind ISP) causes severe performance degradation and connectivity issues.
- If using a static IP from your ISP, configure it under eero app Settings > Network Settings > DHCP & NAT > Static IP.
Step 6: eero Gaming Lag and High Latency
For gaming lag specifically:
- Enable eero Labs > Band Steering and 160 MHz channels (eero Pro 6E only).
- Connect gaming devices via Ethernet directly to an eero LAN port — this bypasses WiFi congestion entirely.
- Check your internet plan's upload speed; upload below 10 Mbps causes significant gaming lag.
- Enable UPnP in eero settings if gaming consoles fail NAT traversal.
- Use eero's Priority feature in the app to prioritize gaming devices during peak household usage.
Step 7: Factory Reset — Last Resort
If all above steps fail, factory reset the entire eero network:
- In the eero app: Settings > Advanced > Reset Network.
- Alternatively, hold the reset button on the gateway for 15 seconds. All nodes will reset automatically.
- After reset, re-run setup from the eero app, connecting gateway to modem first.
Document your network name, password, and any port-forwarding rules before resetting — these will all be erased.
Frequently Asked Questions
#!/usr/bin/env bash
# eero Network Diagnostic Script
# Run on a Mac or Linux machine connected to your eero network
# Usage: chmod +x eero_diag.sh && ./eero_diag.sh
echo "=== eero Network Diagnostic Tool ==="
echo ""
# 1. Identify default gateway (eero IP)
GATEWAY=$(ip route show default 2>/dev/null | awk '/default/ {print $3}' || route -n get default 2>/dev/null | awk '/gateway/ {print $2}')
echo "[1] Detected eero Gateway IP: $GATEWAY"
echo ""
# 2. Ping eero gateway (LAN connectivity)
echo "[2] Pinging eero gateway (LAN test)..."
ping -c 4 "$GATEWAY" 2>&1
echo ""
# 3. Ping ISP gateway / upstream
echo "[3] Pinging 8.8.8.8 (internet reachability test)..."
ping -c 4 8.8.8.8 2>&1
echo ""
# 4. DNS resolution test
echo "[4] Testing DNS resolution via eero default DNS..."
nslookup google.com 2>&1
echo ""
# 5. DNS resolution via fallback DNS
echo "[5] Testing DNS resolution via Cloudflare 1.1.1.1..."
nslookup google.com 1.1.1.1 2>&1
echo ""
# 6. Traceroute to identify where packets drop
echo "[6] Running traceroute to 8.8.8.8 (first 15 hops)..."
traceroute -m 15 8.8.8.8 2>&1 || tracert -h 15 8.8.8.8 2>&1
echo ""
# 7. MTR one-shot for jitter and packet loss
echo "[7] Running MTR report (requires mtr to be installed)..."
if command -v mtr &>/dev/null; then
mtr --report --report-cycles 10 8.8.8.8
else
echo "MTR not installed. Install with: brew install mtr (Mac) or apt install mtr (Linux)"
fi
echo ""
# 8. Check local interface speed negotiation
echo "[8] Checking Ethernet interface link speed..."
if command -v ethtool &>/dev/null; then
IFACE=$(ip route show default | awk '/default/ {print $5}' | head -1)
ethtool "$IFACE" 2>&1 | grep -E 'Speed|Duplex|Link'
else
echo "ethtool not available. On Mac, use: networksetup -getMedia Wi-Fi"
networksetup -getMedia Wi-Fi 2>/dev/null || true
fi
echo ""
# 9. Speed test via curl (rough download benchmark)
echo "[9] Running quick download speed test via curl..."
echo "Downloading 100MB test file from Cloudflare..."
time curl -o /dev/null -s -w "%{speed_download} bytes/sec\n" https://speed.cloudflare.com/__down?bytes=104857600
echo ""
# 10. Check for duplicate IPs / ARP conflicts
echo "[10] ARP table (check for duplicate MACs)..."
arp -a 2>&1 | head -20
echo ""
echo "=== Diagnostic Complete ==="
echo "If 8.8.8.8 ping fails but gateway ping succeeds: ISP or modem issue."
echo "If DNS fails but 8.8.8.8 ping works: Change eero DNS to 1.1.1.1 in eero app."
echo "If gateway ping fails: Power-cycle eero and modem in sequence."
echo "If download speed < 50% of ISP plan: Check for overheating, firmware, or interference."Error Medic Editorial
The Error Medic Editorial team consists of senior DevOps engineers, SREs, and network architects with 10+ years of hands-on experience troubleshooting consumer and enterprise networking hardware. Our guides are tested on real hardware under real failure conditions and updated continuously as firmware and ISP configurations change.
Sources
- https://support.eero.com/hc/en-us/articles/207849903-Troubleshooting-your-eero-network
- https://support.eero.com/hc/en-us/articles/207621403-How-do-I-restart-my-eero-network
- https://support.eero.com/hc/en-us/articles/209014513-How-do-I-factory-reset-my-eero
- https://www.reddit.com/r/eero/comments/troubleshooting_eero_6_slow_speeds_ipv6_fix
- https://community.eero.com/network-204/eero-6-pro-dropping-connection-firmware-issue-thread
- https://stackoverflow.com/questions/tagged/eero+networking
- https://www.dslreports.com/forum/eero