Error Medic

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 in minutes. Step-by-step troubleshooting for eero 6, Pro 6, and mesh networks.

Last updated:
Last verified:
2,436 words
Key Takeaways
  • Most eero 'no internet' errors stem from ISP outages, modem misconfigurations, or a stale DHCP lease — power cycling the modem and eero gateway in the correct order resolves ~60% of cases.
  • Slow eero speeds are usually caused by ISP throttling, Wi-Fi channel congestion on 2.4 GHz, firmware bugs (especially on eero 6 / Pro 6 after an OTA update), or a device being too far from the nearest node.
  • The eero app error 'We found an issue' or 'Can't reach the internet' almost always clears after a full network restart (modem → gateway → beacons) and verifying the WAN IP is assigned; if it persists, factory-resetting the gateway and re-running setup fixes it in the remaining cases.
Fix Approaches Compared
MethodWhen to UseTimeRisk
Power-cycle modem + eero gatewayNo internet, 'eero can't find internet', connected but no internet2–5 minNone
Restart network via eero appIntermittent drops, slow speeds, beacon not connecting1–2 minNone
Change DNS to 8.8.8.8 / 1.1.1.1DNS resolution failures, slow browsing but fast speed tests2 minVery Low
Switch Wi-Fi band (5 GHz → 2.4 GHz or vice versa)2.4 GHz not working, gaming lag, weak signal in specific rooms1 minNone
Enable/Disable Bridge Mode on modemDouble NAT, eero won't connect to modem, wired connection not working5–10 minLow — may reset port forwards
Update eero firmware via appeero 6 issues post-update, Pro 6 speed issues, 'We found an issue' error5–15 minLow
Factory reset gateway eeroSetup problems, eero setup troubleshooting, persistent no-internet after all above10–20 minMedium — wipes all settings
Replace ethernet cable / check modem portWired connection slow, eero won't connect to modem5 minNone
Contact ISPSpeed test at modem is also slow, suspected throttling or line issue15–60 minNone

Understanding eero WiFi Errors

eero mesh systems consist of a gateway node (wired to your modem) and one or more leaf nodes or beacons that extend coverage wirelessly or via ethernet backhaul. When something breaks, the failure can happen at four layers:

  1. ISP / WAN layer — your ISP isn't delivering internet to the modem.
  2. Modem ↔ eero gateway layer — the modem isn't handing a WAN IP to eero, or the ethernet link is bad.
  3. eero mesh layer — nodes can't communicate with each other (beacon not connecting, extender not working).
  4. Client device layer — a phone or PC can't connect to eero, or gets an IP but no internet.

Knowing which layer is broken tells you exactly where to intervene.


Step 1: Identify the Symptom

Open the eero app → Home screen and look at the status indicator:

  • 🔴 Red dot / "We found an issue" → eero gateway has no WAN connectivity.
  • 🟡 Yellow dot / "Connected without internet" → eero got an IP from the modem but can't reach the internet (DNS or routing problem, or ISP outage).
  • 🟢 Green dot but slow → connectivity exists; issue is bandwidth, interference, or a client device.
  • Node shown offline → a beacon or extender lost its backhaul link.

Step 2: Test the Modem First

Before touching the eero, isolate whether the modem itself has internet:

  1. Unplug the ethernet cable from the eero gateway's WAN port.
  2. Plug a laptop directly into the modem via ethernet.
  3. Run a speed test at fast.com or speedtest.net.
  • If the laptop also has no internet → call your ISP. The problem is upstream.
  • If the laptop gets internet → the eero gateway is the issue; continue below.

Step 3: Power-Cycle in the Correct Order

This is the single most effective fix for eero can't connect to internet and eero connected but no internet.

  1. Unplug the modem's power cord (and battery backup if present). Wait 60 seconds.
  2. Unplug all eero nodes.
  3. Plug the modem back in. Wait until all lights are stable (30–90 seconds depending on ISP).
  4. Plug in the eero gateway (the one with the WAN ethernet cable). Wait 2 minutes.
  5. Plug in beacons/extenders one at a time, starting with those closest to the gateway.

The eero app should show a green indicator within 3–4 minutes. If you see "eero can't find internet" after this, proceed to Step 4.


Step 4: Check for Double NAT / Bridge Mode Issues

Many ISP-supplied modems are actually modem-router combos (e.g., Arris, Technicolor). If the modem is also acting as a router, eero sits behind a second NAT — this can prevent eero from getting a proper public IP, causing eero won't connect to modem and eero Pro 6 can't reach the internet.

Fix: Log into your modem's admin UI (usually at 192.168.100.1 or 192.168.0.1) and enable Bridge Mode (also called IP Passthrough or DMZ mode). Consult your ISP or modem manual for the exact steps — the process varies by carrier.

After enabling bridge mode, power-cycle everything per Step 3.


Step 5: Fix Slow eero Speeds

5a. Check band steering and force a band: eero uses band steering to auto-assign devices to 2.4 GHz or 5 GHz. If you're seeing eero 2.4 GHz not working or eero slow speeds on a specific device, try manually connecting to the 5 GHz band (look for a _5G suffix if you've split bands, or use the eero app's Advanced → Band Steering → Off to split bands).

5b. Check Wi-Fi channel congestion: In dense neighborhoods, the 2.4 GHz band (channels 1, 6, 11) gets saturated. Open the eero app → Settings → Network Settings → Advanced and check the channel in use. You can't manually set channels in the consumer eero app, but restarting the network sometimes triggers a fresh channel scan.

5c. Check physical placement: For eero beacon not connecting or eero extender not working, nodes placed too far apart drop to weak backhaul links. Each node should be within 30–40 feet with no more than one wall between it and the next node. Use the eero app's Health Check feature to see signal strength between nodes.

5d. Update firmware: Several known bugs in eero 6 and Pro 6 firmware caused eero slow speeds and eero Pro 6 dropping WiFi after OTA updates. In the eero app go to Settings → Software Updates → Check for Updates. If the latest firmware is already installed and problems persist, check the eero community forum for rollback workarounds.

5e. Check for overheating: The eero Pro 6 in particular can throttle performance when overheated. Symptoms include eero overheating LED behavior (solid red) and intermittent drops. Ensure the unit has 6 inches of clearance on all sides, is not inside a cabinet, and is not stacked on other devices.


Step 6: Restart the eero Network (App Method)

If you prefer not to physically unplug devices:

  1. Open the eero app.
  2. Tap the Menu icon (☰)Network Settings.
  3. Scroll down and tap Restart Network.
  4. Wait 2–3 minutes for all nodes to come back online.

This is equivalent to a soft reboot of all nodes simultaneously.


Step 7: DNS Troubleshooting for "Connected But No Internet"

If eero shows green/connected but browsers say "DNS_PROBE_FINISHED_NXDOMAIN" or pages won't load:

  1. In the eero app go to Settings → Network Settings → DNS.
  2. Change from Automatic to Custom.
  3. Set Primary DNS to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google).
  4. Set Secondary DNS to 1.0.0.1 or 8.8.4.4.
  5. Save and restart the network.

Step 8: Factory Reset (Last Resort)

If eero setup problems persist or the gateway is stuck in an error state:

  1. In the eero app, go to Settings → eero Devices → [select gateway] → Advanced → Reset eero. Choose Reset and Remove.
  2. Alternatively, hold the reset button on the back of the eero for 15 seconds until the LED flashes yellow.
  3. Re-add the device in the eero app and run setup from scratch.

Warning: This erases your network configuration, device nicknames, profiles, and parental controls.


Step 9: Wired Connection Issues

For eero wired connection not working or eero wired connection slow:

  • Swap the ethernet cable — Cat5e or better is required for gigabit backhaul.
  • Try a different LAN port on the eero (Pro 6 has two).
  • Check that the switch or device supports the same duplex/speed (use ethtool eth0 on Linux to inspect).
  • If using a managed switch, check for VLAN or STP misconfiguration blocking eero traffic.

Step 10: Gaming Lag (eero Gaming Lag)

  • Enable eero Plus's built-in QoS if subscribed, or prioritize your gaming device in the eero app: Devices → [device] → Activity → Mark as Priority.
  • Connect your gaming console to the eero's ethernet LAN port for the lowest latency.
  • Check for firmware updates — the eero 6 line had documented high-latency bugs fixed in later firmware.
  • If ping spikes persist, use mtr or ping -c 100 8.8.8.8 to identify packet loss at the ISP hop.

Frequently Asked Questions

bash
#!/usr/bin/env bash
# ============================================================
# eero Network Diagnostic Script
# Run on a Mac or Linux machine connected to the eero network
# ============================================================

echo "=== 1. Local IP and Gateway ==="
if [[ "$OSTYPE" == "darwin"* ]]; then
  ipconfig getifaddr en0         # Mac Wi-Fi
  netstat -nr | grep default     # Default gateway (should be eero IP)
else
  ip addr show                   # Linux
  ip route show default
fi

echo ""
echo "=== 2. Ping eero Gateway ==="
# Replace 192.168.4.1 with your eero gateway IP if different
GATEWAY=$(ip route show default 2>/dev/null | awk '/default/ {print $3}' || netstat -nr 2>/dev/null | awk '/default/ {print $2}' | head -1)
ping -c 4 "$GATEWAY"

echo ""
echo "=== 3. DNS Resolution Test ==="
nslookup google.com 1.1.1.1       # Test with Cloudflare DNS
nslookup google.com 8.8.8.8       # Test with Google DNS

echo ""
echo "=== 4. Ping Public Internet ==="
ping -c 4 8.8.8.8                  # Test raw connectivity (no DNS)
ping -c 4 1.1.1.1

echo ""
echo "=== 5. Traceroute to Detect ISP Hop Issues ==="
if command -v mtr &>/dev/null; then
  mtr --report --report-cycles 10 8.8.8.8
else
  traceroute 8.8.8.8
fi

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

echo ""
echo "=== 7. Check Wi-Fi Signal (Linux only) ==="
if command -v iwconfig &>/dev/null; then
  iwconfig 2>/dev/null | grep -E 'Signal|Bit Rate|ESSID'
elif command -v nmcli &>/dev/null; then
  nmcli -f SSID,BSSID,SIGNAL,FREQ dev wifi
fi

echo ""
echo "=== 8. Check for Duplicate IP / ARP Issues ==="
if command -v arp-scan &>/dev/null; then
  sudo arp-scan --localnet 2>/dev/null | head -20
else
  arp -a
fi

echo ""
echo "=== 9. Flush DNS Cache ==="
if [[ "$OSTYPE" == "darwin"* ]]; then
  sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder
  echo "macOS DNS cache flushed."
elif command -v systemd-resolve &>/dev/null; then
  sudo systemd-resolve --flush-caches
  echo "Linux systemd-resolved DNS cache flushed."
fi

echo ""
echo "=== Diagnostic Complete ==="
echo "If ping 8.8.8.8 fails but ping to gateway succeeds, the issue is at the ISP or modem level."
echo "If ping gateway fails, the eero node or LAN link is broken."
echo "If nslookup fails but ping 8.8.8.8 works, set custom DNS in the eero app (1.1.1.1 / 8.8.8.8)."
E

Error Medic Editorial

The Error Medic Editorial team is composed of senior DevOps engineers, SREs, and network specialists with a combined 40+ years of experience troubleshooting enterprise and home network infrastructure. We specialize in translating complex networking diagnostics into actionable, plain-language guides so anyone — from a homeowner to a systems architect — can resolve connectivity issues fast.

Sources

Related Articles in Eero

Explore More wifi Guides