eero WiFi Not Working: Complete Troubleshooting Guide for No Internet, Slow Speeds & Connection Problems
Fix eero WiFi not working, slow speeds, and no internet issues. Step-by-step guide covering eero 6, eero Pro 6, beacon, and mesh network problems.
- Root cause 1: ISP or modem issues upstream of your eero — the eero hardware itself is fine but has no signal to pass through (shows as 'eero connected but no internet').
- Root cause 2: DHCP conflicts, double NAT, or incorrect DNS settings causing eero to fail handing out IP addresses to client devices, resulting in 'can't connect to internet' errors.
- Root cause 3: Overheating or firmware bugs on eero 6 / eero Pro 6 nodes causing random disconnects, slow speeds, or beacon not connecting to the gateway node.
- Root cause 4: Wireless interference on 2.4 GHz band or suboptimal mesh placement causing eero slow speeds, gaming lag, and upload/download bottlenecks.
- Quick fix summary: Power-cycle modem and eero in the correct order → verify ISP line status → check eero app for firmware updates → change DNS to 1.1.1.1 → reposition nodes for better signal → factory reset as a last resort.
| Method | When to Use | Time | Risk |
|---|---|---|---|
| Power-cycle modem + eero (correct order) | First step for any 'no internet' or dropped connection issue | 2–5 min | None |
| Change DNS to 1.1.1.1 or 8.8.8.8 in eero app | eero shows connected but websites won't load; DNS resolution failures | 2 min | Very Low |
| Disable IPv6 on eero | eero Pro 6 can't reach internet or intermittent drops on IPv6-only ISP configs | 1 min | Low |
| Factory reset single beacon/node | Beacon not connecting to mesh, eero extender not working after move | 10–15 min | Medium — must re-add node |
| Enable/disable eero 2.4 GHz band separately | 2.4 GHz not working or interfering with 5 GHz clients | 2 min | Low |
| Replace Ethernet cable modem-to-eero | Wired connection slow or not working, eero won't connect to modem | 5 min | None |
| Full factory reset + fresh setup | Persistent 'eero 6 we found an issue' or setup won't complete | 30–45 min | High — wipes all settings |
| Contact ISP about line signal | eero can't find internet even after full reset and new equipment test | 30–60 min | None |
Understanding Why eero WiFi Stops Working
eero mesh systems sit between your ISP modem and your devices. When any link in that chain breaks, you'll see symptoms ranging from 'eero connected but no internet' to 'eero slow speeds' to a complete inability to connect. Understanding the chain helps you isolate the failure fast:
ISP Line → Modem/ONT → Ethernet → eero Gateway → Mesh Nodes (Beacons) → Your Devices
The eero app will show one of these status indicators:
- Solid white LED — everything working
- Blinking white LED — booting or updating
- Solid red LED — no internet detected
- Blinking red LED — hardware issue or overheating
- Yellow/amber LED — eero is connected to the gateway but has a warning
Error messages you may see in the eero app include:
- "We found an issue with your network"
- "eero can't find the internet"
- "Your eero is offline"
- "eero Pro 6 can't reach the internet"
- "Device not found" (during setup)
Step 1: Isolate Whether It's the ISP, Modem, or eero
Before touching any eero settings, confirm where the fault lies.
- Bypass eero entirely. Connect a laptop directly to your modem via Ethernet. If you still have no internet, the problem is upstream of eero — call your ISP.
- Check ISP status page. Most ISPs publish outage maps. Search "[your ISP] outage" or check Downdetector.
- Inspect modem lights. The modem's WAN/Internet LED should be solid. A blinking or red WAN light means the ISP line is down.
- Check the Ethernet cable between modem and eero gateway. Swap it for a known-good Cat5e or Cat6 cable. A faulty cable is one of the most overlooked causes of 'eero won't connect to modem'.
Step 2: Power-Cycle in the Correct Order
Power-cycling in the wrong sequence is a common mistake. Always follow this order:
- Unplug your modem (remove battery backup if applicable). Wait 60 seconds.
- Unplug your eero gateway (and all beacon nodes). Wait 30 seconds.
- Plug in the modem first. Wait for it to fully sync (all lights stable, usually 60–90 seconds).
- Plug in the eero gateway. Wait 60 seconds.
- Plug in beacon nodes one at a time.
This sequence allows the modem to assign a fresh DHCP lease to the eero gateway, resolving the majority of 'eero can't connect to internet' issues.
Step 3: Fix DNS Issues ("eero Connected But No Internet")
When your device shows WiFi connected but no internet, DNS is a common culprit. Your ISP's DNS servers may be slow or unreachable.
- Open the eero app → tap your network → Advanced Settings → DNS.
- Change from Automatic to Custom.
- Enter
1.1.1.1(Cloudflare) and1.0.0.1as secondary, or8.8.8.8/8.8.4.4(Google). - Save and wait for eero to apply the change (~30 seconds).
Alternatively, test DNS from a connected device:
nslookup google.com 1.1.1.1
If this resolves but nslookup google.com (using default DNS) fails, your ISP DNS is the problem.
Step 4: Address eero Slow Speeds
Slow speeds on eero — whether slow download speed, slow upload speed, or gaming lag — usually have one of these causes:
a) Double NAT If your modem is actually a router-modem combo and you haven't put it in bridge/passthrough mode, you have double NAT. This degrades speed and causes gaming issues.
- Log in to your modem's admin interface (usually
192.168.0.1or192.168.100.1). - Enable IP Passthrough or Bridge Mode.
- Re-run the eero setup.
b) Mesh Node Placement Beacons too far from the gateway cause weak backhaul, throttling all traffic. eero recommends nodes be within 40 feet of each other (or within 2 rooms). Move nodes closer and re-run a speed test.
c) 2.4 GHz Interference If eero 2.4 GHz is not working well or clients keep connecting to 2.4 GHz instead of 5 GHz:
- Go to eero app → Advanced → Troubleshooting → check band steering is enabled.
- Change your WiFi channel manually if nearby networks use the same 2.4 GHz channels (1, 6, or 11).
d) Overheating The eero Pro 6 in particular can throttle speeds when overheating. Ensure your eero has at least 6 inches of clearance on all sides, is not enclosed in a cabinet, and is not stacked on other electronics. A blinking red LED or warm-to-the-touch device is a sign.
e) Firmware Bug — Restart Network Apply firmware updates and restart the network:
- eero app → Settings → Advanced → Restart Network
- Or use the eero API (see code block below).
Step 5: Fix eero 6 / eero Pro 6 Specific Issues
The eero 6 and eero Pro 6 introduced WiFi 6 (802.11ax), and some issues are unique to these models:
"eero 6 we found an issue" during setup:
- Make sure Bluetooth is enabled on your phone (required for initial setup pairing).
- Ensure the eero is within 5 feet of your phone during setup.
- Force-quit the eero app, re-open, and retry.
- If the error persists, hold the reset button on the back of the eero for 15 seconds until the LED turns red, then retry setup.
eero Pro 6 dropping WiFi / intermittent disconnects:
- Disable IPv6 in eero app → Advanced Settings if your ISP doesn't fully support it.
- Check for conflicting DHCP — ensure only the eero (not the modem) is acting as DHCP server.
- Enable WPA3/WPA2 mixed mode instead of WPA3-only if older devices keep dropping.
eero Pro 6 speed issues (not reaching subscribed speeds):
- Use a wired speed test directly to the eero gateway via Ethernet first. If wired speeds are slow, the issue is upstream.
- Ensure you're testing with a WiFi 6-capable device to see 802.11ax speeds.
- Enable 160 MHz channel width in Advanced settings if your environment supports it.
Step 6: Fix eero Beacon / Extender Not Connecting
If an eero beacon or extender node shows offline in the app:
- Move the beacon closer to the gateway (within 30 feet) and wait 3–5 minutes.
- Plug and unplug the beacon — eero beacons use wall outlets and don't have power buttons.
- Remove and re-add the node in the eero app: tap the offline node → Remove from Network → Add eero and follow prompts.
- Factory reset the beacon using the reset button (hold until LED flashes red).
Step 7: eero Wired Connection Not Working
- Check which Ethernet port you're using. The eero gateway's WAN port (marked with a globe icon) connects to your modem. The LAN ports connect wired devices.
- Enable wired client isolation is NOT enabled if devices can't talk to each other.
- For wired connections that are slow: test with a different cable, and confirm your device's NIC supports Gigabit Ethernet.
- Check the eero app: Devices → select your wired device → confirm it shows the expected IP.
Step 8: Factory Reset (Last Resort)
If all else fails:
- In the eero app: Settings → Advanced → Reset → Reset and Remove eeros.
- Or physically: hold the reset button on each eero for 15 seconds until the LED turns red.
- Reconfigure from scratch using the eero app.
Frequently Asked Questions
#!/usr/bin/env bash
# ============================================================
# eero WiFi Diagnostic & Fix Script
# Run from any device on the same network as your eero
# ============================================================
echo "=== eero Network Diagnostic Tool ==="
echo ""
# ---- 1. Check if default eero gateway is reachable ----
EERO_GW="192.168.4.1" # Default eero gateway IP
echo "[1] Pinging eero gateway at $EERO_GW ..."
ping -c 4 $EERO_GW
if [ $? -ne 0 ]; then
echo "FAIL: eero gateway not reachable. Check physical connection."
else
echo "OK: eero gateway is reachable."
fi
echo ""
# ---- 2. Check DNS resolution using ISP default DNS ----
echo "[2] Testing DNS resolution (default)..."
nslookup google.com
if [ $? -ne 0 ]; then
echo "FAIL: Default DNS failing. Try changing to 1.1.1.1 in eero app."
fi
echo ""
# ---- 3. Test DNS resolution using Cloudflare 1.1.1.1 ----
echo "[3] Testing DNS via Cloudflare 1.1.1.1..."
nslookup google.com 1.1.1.1
if [ $? -eq 0 ]; then
echo "OK: 1.1.1.1 DNS works. Change DNS in eero app to 1.1.1.1."
else
echo "FAIL: Even 1.1.1.1 fails. Likely upstream ISP/modem issue."
fi
echo ""
# ---- 4. Check latency to internet (8.8.8.8) ----
echo "[4] Checking latency to Google DNS (8.8.8.8)..."
ping -c 10 8.8.8.8 | tail -2
echo ""
# ---- 5. Trace route to detect where packets drop ----
echo "[5] Running traceroute to detect network hop failures..."
traceroute -m 15 8.8.8.8 2>/dev/null || tracert 8.8.8.8 2>/dev/null
echo ""
# ---- 6. Check for double NAT (multiple private IPs in trace) ----
echo "[6] Checking for Double NAT..."
ROUTE_HOPS=$(traceroute -m 5 8.8.8.8 2>/dev/null | grep -oE '(10\.|172\.(1[6-9]|2[0-9]|3[0-1])\.|192\.168\.)([0-9]{1,3}\.){1}[0-9]{1,3}' | sort -u)
HOP_COUNT=$(echo "$ROUTE_HOPS" | grep -c .)
if [ "$HOP_COUNT" -gt 1 ]; then
echo "WARNING: Double NAT detected. Found $HOP_COUNT private IP hops:"
echo "$ROUTE_HOPS"
echo "Fix: Put modem in bridge/passthrough mode."
else
echo "OK: No double NAT detected."
fi
echo ""
# ---- 7. Speed test via CLI (requires speedtest-cli) ----
echo "[7] Running speed test (requires speedtest-cli installed)..."
if command -v speedtest-cli &>/dev/null; then
speedtest-cli --simple
elif command -v speedtest &>/dev/null; then
speedtest
else
echo "speedtest-cli not installed. Install with: pip install speedtest-cli"
echo "Or run: curl -s https://raw.githubusercontent.com/sivel/speedtest-cli/master/speedtest.py | python3 -"
fi
echo ""
# ---- 8. Check local WiFi interface signal strength (Linux) ----
if command -v iwconfig &>/dev/null; then
echo "[8] WiFi signal strength (Linux):"
iwconfig 2>/dev/null | grep -E 'ESSID|Signal|Bit Rate'
elif command -v airport &>/dev/null; then
echo "[8] WiFi signal strength (macOS):"
/System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport -I | grep -E 'SSID|agrCtlRSSI|lastTxRate|maxRate'
else
echo "[8] Run 'netsh wlan show interfaces' on Windows for signal info."
fi
echo ""
# ---- 9. Flush DNS cache ----
echo "[9] Flushing local DNS cache..."
if [[ "$OSTYPE" == "darwin"* ]]; then
sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder
echo "macOS DNS cache flushed."
elif [[ "$OSTYPE" == "linux-gnu"* ]]; then
sudo systemd-resolve --flush-caches 2>/dev/null || sudo /etc/init.d/dns-clean restart 2>/dev/null
echo "Linux DNS cache flushed."
else
echo "Windows: Run 'ipconfig /flushdns' in an elevated command prompt."
fi
echo ""
# ---- 10. eero API restart (unofficial, requires token) ----
# Get your token by inspecting the eero app network calls or using:
# curl -s -X POST https://client.eero.com/api/v1/login -d '{"login":"your@email.com"}'
# Then verify with the code sent to your email/phone.
# Replace TOKEN and NETWORK_ID with your values.
# EERO_TOKEN="your_session_token_here"
# NETWORK_ID="your_network_id_here"
# echo "[10] Restarting eero network via API..."
# curl -s -X PUT \
# -H "cookie: s=$EERO_TOKEN" \
# -H "Content-Type: application/json" \
# "https://client.eero.com/api/v1/networks/$NETWORK_ID/reboot"
echo "=== Diagnostic Complete ==="
echo "Review output above for FAIL or WARNING messages."
echo "If all checks pass but internet still slow, check eero app for firmware updates."Error Medic Editorial
The Error Medic Editorial team consists of senior DevOps engineers, SREs, and network specialists with 10+ years of experience troubleshooting enterprise and home networking infrastructure. Our guides are based on hands-on testing, official vendor documentation, and real-world incident resolution. We specialize in mesh networking, ISP integration, and WiFi optimization across platforms including eero, Orbi, and UniFi.
Sources
- https://support.eero.com/hc/en-us/articles/207852543-How-do-I-restart-my-eero-network
- https://support.eero.com/hc/en-us/articles/207908443-How-do-I-factory-reset-my-eero
- https://support.eero.com/hc/en-us/articles/207852523-My-eero-is-offline-what-do-I-do
- https://support.eero.com/hc/en-us/articles/360000513486-What-does-the-LED-on-my-eero-mean
- https://www.reddit.com/r/eero/comments/troubleshooting_megathread
- https://github.com/343max/eero-client/issues
- https://community.eero.com/t/eero-pro-6-dropping-connection/12453