Eero Blinking Red

An eero blinking red almost always means one thing: your eero has lost its internet connection. It's not a random glitch, and it's rarely a dead unit. The light is the system telling you it can't reach the internet, so it keeps cycling through reconnect attempts.

Your job is to figure out which link in the chain broke.

Per eero's published LED guide, blinking red is a no-internet state, which is a different fault class from a solid red error light. That distinction matters because the fixes are completely different. A full eero reboot cycle takes roughly 60 to 120 seconds, so you'll have plenty of time to watch the pattern.

Here's how to read the signal and work through it in the right order.

Quick Answer

An eero blinking red means it has no internet connection. The eero itself is usually fine. Check your modem or ONT lights first.

Then reboot the modem and the gateway eero. If that fails, check for an ISP outage.

Why Your eero Is Blinking Red (and What It Actually Means)

An eero is a mesh Wi-Fi system made by Amazon. Instead of one router in a corner, you get several units that talk to each other and blanket your home in signal. One unit acts as the gateway, and the rest are nodes, often called leaves.

The gateway is the only eero physically wired to your modem or ONT. Everything else hops through it. That single cable is the whole network's lifeline.

Because eero units have no screen and no web admin page you can browse to, the LED is the entire diagnostic interface. The color and the blink pattern are the message. Blinking red is the system saying "I'm powered on, my radios are working, but I cannot reach the internet."

What blinking red is actually reporting

Think of it as a handshake that keeps failing. The eero reaches out to the internet through its WAN port, gets nothing back, waits, and tries again. That retry loop is what you see.

The failure can sit in any of these places:

• Your ISP has an outage in your area
• Your modem or ONT has lost its signal
• The Ethernet cable between the modem and the gateway eero is loose or dead
• Your modem is still in router mode, creating a double NAT conflict
• Your ISP needs PPPoE credentials or a VLAN tag that the eero doesn't have
• Your ISP locked the connection to a different device's MAC address
• A firmware update got interrupted mid-install
• Amazon's own cloud services are having a bad day

Notice that only two of those eight are actually eero's fault. That's why "just restart the eero" so often does nothing.

What blinking red is not

It is not a hardware failure. A dying eero usually goes dark, flickers, or drops off the network entirely rather than blinking red on a steady loop.

It is also not a Wi-Fi password problem. Bad credentials produce a device that can't join your network, not a gateway that can't reach the internet.

Blinking Red vs. Solid Red: Reading the LED Correctly

This is where most people go wrong. Blinking red and solid red look similar at a glance, especially in a dim room. They mean different things.

Blinking red means no internet connection. The unit is healthy and actively trying. Solid red means the unit itself hit a problem it can't work through, which often points to a failed boot, corrupted firmware, or a hardware fault.

eero LED states at a glance

Manufacturer documentation confirms these states across the current lineup, including the eero 6, eero 6+, eero Pro 6E, and eero Max 7. The core meanings have stayed consistent across generations.

The LED-off trap

Here's a wrinkle that trips people up. You can turn the LED off entirely in the eero app. It's a popular setting for bedrooms and living rooms where a glowing light is annoying.

If you've done that, a blinking red eero looks exactly like a healthy one. Before you panic about a silent unit, open the app and check whether the status light is disabled.

In our research, this single setting accounts for a surprising share of "my eero is dead" reports. The hardware was fine the whole time.

Firmware updates and the red loop

eero pushes firmware updates automatically, usually overnight. If an update gets interrupted by a power cut or an unplugged cable, the unit can get stuck cycling.

You'll see a repeating blink pattern that never resolves into white. Give it a full 10 minutes before you intervene. If it's still cycling after that, a soft reset is the next step, not a factory reset.

Gateway or Leaf? Which eero Is Actually the Problem

Before you touch anything, figure out which unit is unhappy. A single blinking leaf is a very different problem from a blinking gateway.

The gateway is the eero with an Ethernet cable running to your modem or ONT. It's usually the one closest to wherever your internet enters the house. On most setups it's also the first unit listed in the eero app.

Every other eero is a leaf. Leaves get their connection from the gateway, either wirelessly or through an Ethernet backhaul cable if you've wired them.

Why the distinction changes everything

If the gateway is blinking red, your whole network is down. Every device in the house loses internet, and every leaf will typically show trouble too.

If a single leaf is blinking red while the rest of the house works fine, the gateway is healthy. You've got a local problem with that one node, its placement, or its backhaul cable.

That's a 30-second diagnosis that saves a lot of pointless rebooting.

How to identify each unit in the app

Open the eero app and tap into your network. Each device shows its own status, name, and location. You can rename them to match where they physically sit, like "Office" or "Upstairs Hall."

If you haven't done that yet, do it now while things are working. It takes two minutes and makes every future outage dramatically easier to debug.

One more thing. The gateway is the unit you should never factory reset casually. Resetting it can wipe your entire network configuration, and you'll have to rebuild every node and every device connection from scratch.

The 60-Second Triage: Before You Touch Anything

Resist the urge to start unplugging things. Spend one minute gathering information first. The pattern you see will tell you exactly which branch to follow.

Step 1: Look at every eero in the house

Walk around and check each unit. Note which ones are blinking red and which are white. This takes 30 seconds and it's the single most useful data point you'll collect.

Step 2: Check your modem or ONT lights

Find your modem or ONT and look at its indicator lights. A healthy cable modem shows power, a solid downstream light, a solid upstream light, and a solid online light. A healthy fiber ONT shows power and a solid PON light.

If those lights are dark, flashing, or showing red, stop. Your problem is upstream of eero, and no amount of eero troubleshooting will fix it.

Step 3: Open the eero app

The app shows a network status banner at the top. It also shows whether eero detects an internet outage and, in many cases, which provider is affected.

Step 4: Run the in-app speed test

The eero app has a built-in speed test that runs from the gateway itself, not from your phone. That's important. It tests the actual WAN link, so a failure there confirms the problem is between your gateway and your ISP.

Step 5: Check whether other devices are affected

If your phone shows no internet but your smart TV is streaming fine, the problem is your phone, not the network. If everything is down, the network is down.

What your findings mean

Branch 1: Your Modem or ONT Lights Are Also Out

If your modem or ONT is showing trouble, the eero is innocent. It's reporting a problem accurately. Fix the upstream device first and the eero will usually recover on its own within a couple of minutes.

Reading cable modem lights

A cable modem typically has four or five indicators. Power should be solid. The downstream and upstream lights should be solid once locked.

The online or status light should be solid.

A flashing downstream light means the modem is hunting for a signal on the coax line. A flashing upstream light means it's trying to talk back to the ISP's equipment. If it never settles, the coax line, a splitter, or the ISP's node is the issue.

DOCSIS 3.1 modems, which are what most US cable providers now require for their faster tiers, can take two to five minutes to lock on after a reboot. Give it that full window before you declare it dead.

Reading fiber ONT lights

Fiber installs use an ONT instead of a modem. The key indicators are power, PON, and LOS.

LOS stands for Loss of Signal. If LOS is red or blinking, the fiber line itself has a problem. That could be a dirty connector, a bent fiber patch cable, or damage on the provider's side.

A red LOS light is not something you can fix by rebooting. Check that the fiber patch cable is fully seated and not kinked, then call your ISP. Never look into the end of a fiber connector.

The light is invisible and it can damage your eyes.

The power-cycle order that actually works

Order matters here. Do it in the wrong sequence and you'll just create a new failure.

1. Unplug the modem or ONT from power.
2. Unplug the gateway eero from power.
3. Leave the leaves plugged in for now.
4. Wait a full 60 seconds.
5. Plug the modem or ONT back in.
6. Wait until its lights settle, up to 5 minutes on cable.
7. Plug the gateway eero back in.
8. Wait 2 minutes for it to boot and go white.

Leaves will rejoin on their own once the gateway is back online. If one doesn't, reboot that single unit.

Cabling checks people skip

A loose or failing Ethernet cable between the modem and the gateway is a classic cause of a stubborn blinking red light. Unplug it, look at the clip, and plug it back in until you hear a click.

Check that it's in the correct port. On the gateway, the WAN port is the one that connects to the modem. Some eero models have multiple ports, and plugging into the wrong one produces exactly this symptom.

Coax connections should be finger-tight plus a quarter turn. If you have a splitter feeding both your modem and a TV box, try connecting the modem directly to the wall outlet to rule the splitter out.

When the modem is the problem but looks fine

Sometimes the modem's lights are all green and the eero still can't get online. That usually points to one of three things. The modem is still acting as a router, your ISP requires credentials the eero doesn't have, or the ISP has locked the connection to a different device.

For the first issue, check whether your modem is a combo modem-router. If it is, you'll want it in bridge mode so only the eero handles routing. Two routers fighting for the same job creates a double NAT, which breaks a lot of things.

For the second and third, you'll need your ISP. Ask specifically about PPPoE credentials, VLAN tagging, and whether they use MAC address authentication. Those three details cover most of the setup problems we see reported.

The eero support site maintains a current list of supported ISP configurations. The FCC also publishes broadband consumer labels that spell out what each provider's equipment expects. Both are worth a look before you spend an hour on the phone.

Branch 2: Modem Looks Fine, but the eero App Says "No Internet"

This branch is the trickiest one. Your modem or ONT shows all its normal solid lights. Your gateway eero is blinking red.

The eero app reports no internet connection. Everything looks healthy, yet nothing works.

When you hit this combination, the break is almost always in one of three places. Either the eero can't authenticate with your ISP, your ISP has an issue it hasn't published yet, or something in your local configuration changed without you noticing.

What the eero app is actually telling you

The eero app runs its own connection check from the gateway outward. When it says "no internet," it means the gateway tried to reach eero's servers and failed. That's a real, tested failure, not a guess.

Tap into the network view and look for the outage banner. eero aggregates outage data across its user base, so if your neighbors are also offline, you'll often see the provider named directly. That's a strong signal to skip local troubleshooting entirely.

If there's no outage banner, the app is telling you the problem is on your side of the modem. That's when the deeper checks matter.

Run the in-app speed test first

The eero app's speed test runs from the gateway, not your phone. That distinction is everything here. A phone speed test only measures Wi-Fi throughput.

The gateway test measures the actual WAN link between your eero and your ISP.

If the gateway speed test fails outright, the eero can't reach the internet at all. If it succeeds but shows very low numbers, you've got a signal quality problem rather than a total outage.

Either result narrows the field fast. A failed test with healthy modem lights points straight at authentication or provisioning.

The four usual suspects

Four configuration issues cause most of these cases. They all produce the same symptom, and they all require slightly different fixes.

• Double NAT. Your modem is also a router, so two devices are trying to route. Put the modem in bridge mode, or replace it with a plain modem.
• PPPoE credentials missing. Some ISPs require a username and password for the connection. The eero app supports this during setup, but only if you enter it.
• VLAN tagging. A handful of fiber providers require a specific VLAN ID. If it's not set, the eero never sees the internet.
• MAC address lock. The ISP has the old router's hardware address on file. A new device won't authenticate until they release it.

How to tell which one you're facing

When to stop troubleshooting and call

If the modem lights are solid, the app shows no outage, and you've confirmed there's no double NAT or missing credentials, call your ISP. Ask three specific questions.

First, is there an outage on my line right now? Second, does my account require PPPoE or a VLAN tag? Third, is there a MAC address lock on my account?

Those three answers cover the vast majority of "modem fine, eero red" cases. Having them ready saves you from a long, circular support call.

Branch 3: Only One eero Is Blinking Red

One red leaf is good news. It means your gateway is healthy, your internet connection is live, and the rest of the house is working. You're dealing with a single node problem, and those are usually simple.

The fix depends on how that node connects back to the network. If it's wireless, you're looking at range, interference, or a failing unit. If it's wired, you're looking at a cable, a port, or a switch.

Check the backhaul first

If the node has an Ethernet cable running back to the gateway or a switch, that cable is your prime suspect. Unplug both ends and reseat them until they click.

Try a different cable if you have one. A cable that worked fine for months can fail after a bend, a staple, or a pet chewing on it.

Also check whether the cable is plugged into the correct port. On most eero models, any port can carry backhaul traffic. But if there's a dedicated WAN port and you've plugged into it by mistake, the node won't behave as expected.

If the node is wireless

Wireless nodes fall off the mesh for a few reasons. Distance is the most common. Walls, floors, and large appliances all eat signal, and a node that worked in winter can struggle in summer when foliage or furniture shifts.

Move the node closer to the gateway and see if it recovers. If it does, you've found a placement problem, not a hardware fault.

Interference is the second cause. Microwaves, cordless phones, baby monitors, and neighboring networks all compete for the same airspace. If the node sits next to any of those, try relocating it.

Rebooting a single node

Unplug just that node. Wait 30 seconds. Plug it back in.

Watch the LED.

A healthy node goes white within two minutes. If it goes straight back to blinking red, the problem is persistent, not a transient glitch.

Do not factory reset the node yet. Reset is the last step, not the first.

Removing and re-adding the node

If a reboot doesn't fix it, remove the node from the network in the eero app, then add it back. This forces a clean rejoin and clears any stale pairing data.

You'll need the node to be nearby during re-add. Once it's back on the network, move it to its original spot and watch the LED for a few minutes.

When the node is genuinely dead

Aggregate user reports describe a small but real failure rate on eero nodes after roughly three to five years. The symptoms are consistent. The unit never reaches white, it reboots in a loop, or it drops off the network every few hours.

If a node fails to re-add after two attempts, and it fails in a different location, treat it as a hardware fault. eero's standard warranty runs 12 months, with longer coverage on some models. Check your purchase date before you buy a replacement.

Overheating and power issues

A node crammed behind a TV or inside a closed cabinet can overheat. When it does, it may drop and reconnect repeatedly, sometimes landing on a red LED.

Give it airflow. If the power adapter feels unusually hot, try a different adapter with matching voltage and amperage. Never substitute a random USB charger for the one that shipped with the unit.

Branch 4: Every eero in the House Is Blinking Red

Every unit red means the whole mesh has lost its uplink. In almost every case, the gateway is the one that actually failed. The leaves are just reporting the same thing they see: no internet, no point staying connected.

This branch is faster to work through than it looks. There are only four real possibilities.

Possibility 1: The gateway itself is the problem

The gateway is the single point of failure for the entire mesh. If it can't reach the internet, nothing else can.

Start here. Unplug the gateway, wait 60 seconds, plug it back in. Watch the LED.

If it goes white within two minutes and the leaves follow, you're done. If it stays red, move to the next possibility.

Possibility 2: The WAN link is broken

Check the Ethernet cable between the modem or ONT and the gateway. This is the most overlooked cable in the house.

Reseat both ends. Try a different cable. Confirm it's in the WAN port on the gateway and the LAN port on the modem.

A failing Ethernet cable can pass some traffic and fail on others, which makes the symptom feel random. Swap it and rule it out.

Possibility 3: The modem or ONT is down

Even if the modem lights look fine, the device may be in a stuck state. Power-cycle it in the correct order, which is covered in detail further down.

On cable, give the modem a full five minutes to lock its downstream and upstream channels. Rushing this step is a common mistake.

Possibility 4: The ISP is down

Call your provider or check their status page. If there's a regional outage, no amount of local troubleshooting will help.

Ask for an estimated restoration time. If they can't give one, ask whether the issue is at the node level or the headend. The answer tells you roughly how long you're waiting.

The eero cloud outage nobody thinks about

Here's one people miss. eero relies on Amazon's cloud services for account authentication, remote management, and some app features. In rare cases, a large-scale Amazon Web Services disruption can knock out app functionality even when your local network is technically fine.

If your devices still have internet but the eero app won't load, check Amazon's service health dashboard. If everything is down including internet, an AWS issue is unlikely to be the sole cause.

A quick reset test

If you've ruled out all four possibilities and every unit is still red, try this. Unplug every eero in the house, wait two minutes, then plug the gateway in first. Let it settle before powering the leaves.

This forces a clean mesh reformation from the top down. It fixes a surprising number of stubborn cases where one node was holding the mesh in a bad state.

Branch 5: It Started Right After a Power Cut, Move, or Firmware Update

The timing of when the blinking red started is the most useful clue you have. Three events cause a disproportionate share of these failures, and each one has a different fix.

After a power cut

Brownouts and surges can leave network gear in a confused state even when nothing is physically damaged. The modem may boot faster than the gateway, or vice versa, and the handshake never completes.

The fix is the full power-cycle sequence, done slowly. Cut power to the modem and the gateway. Wait a full 60 seconds.

Bring the modem up first, let it settle, then the gateway.

If this happens often in your area, consider a small uninterruptible power supply for the modem and gateway. Even a modest 600VA unit keeps both running through short outages and prevents the boot-order mess entirely.

After a move

Moving is the single most common reason an eero setup breaks. New address, new ISP, new modem, and often a new account. Every one of those is a chance for a mismatch.

Start by confirming the new ISP works at all. Plug a laptop directly into the modem with Ethernet and see if it gets online. If it doesn't, the problem is not eero.

If it does, the likely culprits are a MAC address lock, a missing PPPoE login, or a VLAN requirement on the new line. All three are covered in Branch 2.

One more thing on moves. If you moved the eero units themselves, give the mesh a few hours to re-learn the layout. Nodes that performed well in a two-story house may need repositioning in an apartment with thick walls.

After a firmware update

eero pushes firmware automatically, usually overnight. If the update was interrupted by a power blip or an unplugged cable, the unit can get stuck cycling.

Give it 10 minutes before you touch anything. Firmware recovery sometimes takes longer than a normal boot.

If it's still cycling after 10 minutes, do a soft reset. Hold the reset button for about 7 seconds, then release. That's long enough to trigger a soft reset but not long enough for a factory reset.

Soft reset vs. factory reset timing

The difference between 7 seconds and 15 seconds is the difference between a fix and a rebuild. Count carefully.

What to check in the app after recovery

Once the network is back, open the eero app and confirm three things. The firmware version should be current. Every node should show online.

And the speed test should return normal numbers.

If the firmware version is stale, let the system update on its own overnight. Don't force it. Interrupted updates are what got you here in the first place.

The Correct Power-Cycle Order: Modem, Then Gateway, Then Leaves

The order matters more than most people realize. A modem that boots before the gateway expects a device to be waiting for it. A gateway that boots first may give up before the modem is ready.

Doing this sequence in the right order solves a huge share of blinking red cases on the first try.

The standard sequence

1. Unplug the modem or ONT from power.
2. Unplug the gateway eero from power.
3. Leave the leaf nodes plugged in.
4. Wait 60 full seconds.
5. Plug the modem or ONT back in.
6. Wait for its lights to lock. Cable: up to 5 minutes. Fiber: 1 to 2 minutes.
7. Plug the gateway eero back in.
8. Wait up to 2 minutes for it to reach white.
9. Leaves should rejoin automatically within 5 minutes.

If a leaf doesn't rejoin, unplug that one leaf, wait 30 seconds, and plug it back in. Don't reboot the whole network for one straggler.

Variations by connection type

Different connection types have different timing quirks. The order stays the same, but the waits change.

If you're on fiber and the ONT has a red LOS light after the reboot, stop. That's a physical line fault, not a boot-order issue. Call your provider.

Wired backhaul changes things

If your leaves are connected by Ethernet backhaul, they may not need to be rebooted at all. They'll re-establish their link once the gateway is back online.

If a wired leaf doesn't recover, check the switch it's connected to. Managed switches with STP or IGMP snooping settings can block eero traffic in ways that look exactly like a hardware fault.

What if the sequence doesn't work

If you've done the full sequence twice and the gateway is still red, the problem isn't boot order. Move to the next diagnostic branch: modem lights, ISP outage, or configuration.

One more trick worth knowing. On some cable setups, unplugging the coax from the modem for 60 seconds and plugging it back in forces a fresh channel scan. Do this only if you're comfortable with the connection, and never overtighten the connector.

Build a habit around it

Write the sequence on a sticky note and stick it inside the modem cabinet. When the network goes down at 11pm, you won't want to look it up.

The whole process takes about 8 minutes end to end. Rushing it produces worse results than doing it once, properly.

Soft Reset, Factory Reset, and When Each One Is Warranted

Here's the part most guides get wrong. eero doesn't publish a formal "soft reset" the way some router brands do. What people mean by that phrase is usually a restart from the eero app.

The app has a restart option under the device settings. Tapping it reboots that unit cleanly, keeps your account link, and preserves every network setting. It's the right first move when a node misbehaves.

The physical reset button is a different animal entirely. eero's official documentation describes one behavior: hold the button for about 15 seconds until the LED flashes red, then release. That's a factory reset.

What a factory reset actually does

It wipes the unit. Network credentials, node pairing, and local configuration all go. The eero then shows up in the app as a new device waiting to be set up.

If you reset the gateway, you're resetting the whole network. Every leaf will need to rejoin, and every device in your home will need to reconnect. That's a 30 to 60 minute job on a typical setup.

If you reset a leaf, only that node needs re-adding. That's a five minute job. This is why identifying the gateway matters so much.

The reset decision table

The mistake that costs people an evening

Factory resetting the gateway to fix a modem problem. It happens constantly, and it turns a 10 minute fix into a full network rebuild.

The eero was reporting a problem accurately. Resetting it erased your configuration without touching the actual cause.

Our rule of thumb: never factory reset until you've confirmed the modem, the cable, and the ISP are all healthy. If any of those three are suspect, fix them first.

Resetting a used or inherited eero

If you picked up an eero secondhand, or you're taking one from a previous home, it needs a factory reset before it'll join your network. There's no way around it.

Hold the reset button for 15 seconds until the LED flashes red. Release. Wait for the unit to cycle, then add it in the app.

It'll appear as an unconfigured device ready to pair.

If the previous owner never removed it from their account, you may hit a wall. In that case, contact eero support with the serial number. They can release it.

One warning about resets and ISP-managed gear

Some apartments and rental properties include eero hardware as part of the lease or the building's internet package. If that's your situation, resetting the gateway may break a configuration the building manager set up.

Ask before you reset. It's a two minute phone call that saves a lot of awkwardness.

Cable and Connection Checks Most People Skip

Physical layer problems cause a huge share of stubborn red lights. People jump to software and settings because cables feel boring. But a cable that worked yesterday can fail today, and the symptom looks identical to an ISP outage.

Work through these checks before you call anyone. They take ten minutes and rule out the most common culprits.

Ethernet, Coax, and the WAN Port

The Ethernet run between your modem and gateway is the single most important cable in the house. Everything rides on it.

Unplug both ends. Look at the plastic clip on the connector. If it's cracked or missing, the cable will work intermittently, which is the worst kind of failure.

Plug it back in until you hear a click. Then give the cable a gentle tug. If it slides out, it wasn't seated.

Which port is the WAN port?

On eero models with multiple ports, any port can technically carry WAN traffic, but the setup expects the one connected during installation. If you've rearranged cables, confirm which port the modem cable is in.

On the eero Max 7, you get 2.5 GbE and 10 GbE ports. On the eero Pro 6E, there are two 2.5 GbE ports. On the eero 6 and 6+, the ports are gigabit.

If you're paying for a multi-gigabit plan and the eero is connected through a gigabit port, you're capped. That's not a blinking red cause, but it's worth knowing.

Cable length and category

Cat5e handles gigabit at runs up to 100 meters, roughly 328 feet. Cat6 and Cat6a handle higher speeds over the same distance.

Most homes never come close to that limit. But if you've run a cable through a wall, a crawlspace, and a garage, it's worth measuring. Long runs also pick up more interference from power lines.

Never run Ethernet parallel to mains wiring for any distance. Cross at right angles if you must. This is basic electrical practice, and it matters for signal integrity.

Coax checks for cable internet

Coax connectors should be finger-tight plus a quarter turn with a wrench. Overtightening damages the center conductor.

Check for splitters. A splitter feeding your modem and three TV boxes can degrade the signal enough to cause intermittent dropouts. Try connecting the modem directly to the wall plate and see if the problem disappears.

Look for kinks, staples through the cable, or chewed sections. Coax is more fragile than it looks.

MoCA and the hidden conflict

MoCA adapters push internet over your existing coax wiring. They're great for extending networks in older homes. But MoCA signals can interfere with cable modem channels if the right filter isn't installed.

If you use MoCA and you've recently added or moved an adapter, that's worth suspecting. A MoCA filter at the point of entry usually resolves it.

The switch question

If you've got wired backhaul running through a network switch, that switch is now part of your critical path. An unmanaged gigabit switch is the safe choice.

Managed switches with spanning tree protocol or IGMP snooping enabled can block eero traffic. The symptom looks exactly like a failed node. If a wired leaf won't come online, bypass the switch and connect directly to the gateway to test.

Double NAT, PPPoE, and ISP Credentials

These three configuration issues produce identical symptoms and require different fixes. Let's take them one at a time.

Double NAT happens when two devices on your network are both trying to route. Usually that's your ISP's combo modem-router and your eero. Two routers, one job.

The fix is bridge mode. Either put the combo unit into bridge mode, or replace it with a plain modem. Bridge mode tells the combo device to stop routing and just pass traffic through.

Signs of double NAT include devices that can't reach each other, gaming services that won't connect, and VPNs that drop constantly. It doesn't always cause a red light, but it can.

PPPoE in plain English

PPPoE is a login method some ISPs use. Your connection requires a username and password before it'll activate.

AT&T Fiber, CenturyLink, and several UK providers use it. If your ISP requires PPPoE and the credentials aren't entered in the eero app, the gateway will never reach the internet.

You enter these during setup, or later in the app under advanced settings. If you don't have the credentials, your ISP can provide them. They're usually printed on your original install paperwork.

VLAN tagging explained simply

VLAN tagging is a way of labeling traffic so the ISP's equipment knows which service it belongs to. Some fiber providers require a specific VLAN ID on the WAN connection.

If that ID isn't set, the eero's traffic arrives unlabeled and gets dropped. You'll see a red light with a perfectly healthy ONT.

Google Fiber and a handful of regional providers have used this. Ask your ISP directly: "Does my connection require a VLAN ID, and if so, what is it?"

MAC address locks

Every network device has a MAC address, a unique hardware identifier. Some ISPs register the MAC address of the equipment they installed and refuse to serve anything else.

Swap in an eero and the connection won't authenticate. The fix is a phone call. Ask the ISP to release the old MAC address or register the new one.

Many ISPs will do this instantly. Some charge a small fee. Either way, it's a five minute call once you know what to ask for.

The configuration checklist

Is It Your ISP? How to Confirm an Outage in Minutes

ISP outages are the most common cause of a red light that won't clear. Confirming one takes about three minutes if you know where to look.

Start with the eero app. It aggregates outage reports across its user base and often names the affected provider. If you see an outage banner, stop troubleshooting and wait.

Check the provider's own status page

Every major ISP runs a status page. Comcast, Spectrum, Cox, AT&T, Verizon, BT, Virgin Media, and Sky all publish live outage maps.

Enter your postcode or ZIP code. If your area shows an outage, you have your answer. Note the estimated restoration time if one is listed.

Be aware that status pages lag. An outage can be live for 20 minutes before it appears. If everything else points to an ISP problem, trust your evidence over a clean status page.

The direct-connection test

This is the most conclusive test you can run. Take a laptop and an Ethernet cable. Plug the laptop directly into the modem or ONT.

If the laptop gets online, your internet connection is fine and the problem is with the eero or its configuration. If the laptop gets nothing, the problem is upstream of your equipment.

This test cuts the diagnosis in half. It's worth the two minutes every time.

What to ask when you call

Have these four questions ready. They get you past the scripted first tier of support much faster.

• Is there an outage affecting my address right now?
• Does my account require PPPoE credentials or a VLAN ID?
• Is there a MAC address lock on my account?
• What signal levels is my modem reporting?

That last question matters on cable. Downstream signal-to-noise ratio and upstream power levels tell a technician whether the line itself is degrading. A modem running at the edge of spec will drop connection under load.

Reading modem signal levels yourself

Most cable modems expose a diagnostic page at a local address like 192.168.100.1 or 192.168.0.1. You can view downstream power, downstream SNR, and upstream power without calling anyone.

Healthy downstream power usually sits between roughly -7 and +7 dBmV. Downstream SNR should be above 30 dB, ideally higher. Upstream power typically sits between 35 and 50 dBmV.

If your upstream power is climbing toward 51 dBmV or higher, the modem is straining to be heard. That's a line problem, and no router swap will fix it.

When it's an Amazon-side issue

Rarely, the problem is neither your ISP nor your hardware. Amazon Web Services disruptions can affect eero account features and app functionality.

If your devices still have working internet but the eero app won't load or shows errors, that's a clue. Check AWS service health before you start unplugging things.

Common Mistakes That Make Blinking Red Worse

Most of the damage in these situations is self-inflicted. Here are the moves that turn a short outage into a long evening.

Factory resetting before you've checked the modem

This is the big one. The eero was reporting a problem accurately. Resetting it destroys your configuration and leaves the real fault untouched.

Always check modem lights and run the direct-connection test first. Reset is the last resort, not the first.

Rebooting everything at once

Unplugging every device simultaneously and plugging them all back in creates a race condition. The modem, gateway, and leaves all boot at different speeds and may never sync properly.

Sequence matters. Modem first, wait, then gateway, then leaves if needed.

Not waiting long enough

Cable modems can take five minutes to lock their channels. People give them 30 seconds, declare them dead, and start unplugging things again.

Set a timer. Patience resolves more red lights than any button press.

Assuming a red light means dead hardware

eero units are reliable. Aggregate user reports show most units running for years without failure. A red light is a connection report, not a death sentence.

Don't buy a replacement until you've ruled out the modem, the cable, and the ISP.

Turning off the status LED

It's a nice feature for bedrooms. It's a terrible idea for the gateway. With the LED off, you lose your only at-a-glance diagnostic tool.

If you've disabled it, turn it back on for the gateway at least. Keep it off on the leaf in the guest room if you like.

Adding new nodes during an outage

Adding a node while the network is down rarely works, and it can leave the new node in a half-configured state. Fix the existing problem first, then expand.

Hiding units in cabinets and behind TVs

eero units need airflow and clear space. A gateway crammed behind a TV in a closed cabinet runs hot. Heat causes instability, and instability looks like a connection fault.

Keep at least a few inches of clearance on all sides. Don't stack anything on top.

Using the wrong power adapter

Every eero ships with a specific adapter. Substituting a random USB charger with lower amperage causes brownouts under load, which can trigger reboots.

If you've lost the original, match the voltage and amperage printed on the unit exactly.

Resetting the wrong device

People reset a leaf thinking it's the gateway, or vice versa. Label your units in the app before you need to.

When to Call eero Support vs. Your ISP

Knowing who to call saves an hour of hold music. The dividing line is simple. eero owns everything from the gateway inward. Your ISP owns everything from the modem outward.

Call eero support when

The modem lights are healthy and the direct-connection test works, but the eero still won't come online. That points at eero hardware, firmware, or account configuration.

Also call eero if a node fails to re-add after multiple attempts. Or if a unit is stuck in a boot loop that a reset won't clear.

eero support can pull remote diagnostics from your network with your permission. That's faster than describing symptoms over the phone. Have your account email and the device serial numbers handy.

Warranty coverage is typically 12 months from purchase, with longer terms on some models. If a unit is genuinely faulty, that's the path to a replacement.

Call your ISP when

The modem or ONT shows fault lights. The direct-connection test fails. Signal levels are out of spec.

Or you need PPPoE credentials, a VLAN ID, or a MAC address released.

Anything involving the physical line, the provisioning, or the account belongs to them. No amount of eero troubleshooting touches those.

What eero support will ask you

Expect a few standard questions. Which unit is affected, gateway or leaf? What's the LED doing right now?

Have you power-cycled in the correct order? Is the firmware current?

Having answers ready cuts the call time significantly. So does a photo of the LED pattern, if you can grab one.

When to escalate

If a first-tier agent runs you through a script you've already completed, ask for a supervisor or a tier-two technician. Be polite and specific. Explain what you've already tested and what the results were.

Mentioning that you've run a direct-connection test and checked signal levels signals that you're not a novice caller. It usually moves you up the queue.

The one case where you call both

If the ISP says the line is fine and eero says the hardware is fine, you're in a stalemate. That's when you call the ISP first and ask for a truck roll to verify signal levels at the demarcation point.

Once the ISP confirms clean signal at the wall, you have documented evidence for eero. That paper trail is what turns a support loop into a resolution.

How to Stop It From Happening Again

Blinking red is a symptom, not a disease. Once the current outage is fixed, a few habits will keep it from coming back so often.

Put the modem and gateway on a UPS

Power blips are the number one trigger. A brief brownout can leave your modem and gateway booting in the wrong order, which is exactly the mess we covered earlier.

A small uninterruptible power supply solves this. Even a 600VA unit keeps a modem and a gateway running through short outages. You get clean shutdowns and a much better shot at a clean recovery.

Put the UPS on the modem and the gateway. Leaves can reboot on their own without breaking anything.

Learn the power-cycle order by heart

Modem first, wait for lights, then gateway. That's the whole sequence.

The reason it works is simple. The gateway expects an internet connection to be waiting when it boots. If it wakes up to nothing, it may give up and sit in a retry loop.

Write it on a sticky note inside the cabinet. Muscle memory beats memory.

Keep the gateway LED on

We mentioned this earlier, but it belongs in the prevention list too. Turning off the LED on the gateway removes your fastest diagnostic tool.

Turn it off on bedroom nodes if you like. Leave the gateway visible.

Label everything in the app

Give each node a name that matches where it sits. "Kitchen," "Office," "Upstairs Hall." Takes two minutes, saves twenty the next time something breaks.

You'll know instantly whether the problem is the gateway or a leaf. That single fact changes the whole troubleshooting path.

Don't hide nodes in cabinets

Airflow matters. eero units that run hot become unstable. Instability shows up as random dropouts and, occasionally, a red light.

Keep a few inches of clearance. Don't stack books or cables on top. If you must hide a node, use an open shelf instead of a closed door.

Document your ISP credentials

Write down your PPPoE username and password, your VLAN ID if you have one, and your ISP's support number. Keep them with the modem.

If you ever need to reconfigure the gateway, or you swap hardware, you'll have everything in one place. No more digging through old emails at midnight.

Consider a backup connection

If your household depends on the internet for work, a backup is worth thinking about. Some eero models support failover through a secondary connection.

A 5G home internet plan or a mobile hotspot can serve as a fallback. It won't match your primary speed, but it keeps the lights on during an outage.

This is a bigger investment. For most homes, it's overkill. For remote workers and small businesses, it pays for itself the first time the cable goes down.

Check for firmware updates periodically

eero updates automatically, but it's worth confirming the version in the app every few months. If a unit is stuck on old firmware, it may be failing updates silently.

A manual reboot often clears a stuck update. If it doesn't, a soft reset usually does the trick.

Watch your modem signal levels

If you're on cable, log into your modem's diagnostic page once a month. Note the downstream power, SNR, and upstream power.

A slow drift in those numbers tells you the line is degrading. You can call your ISP before a total failure, which is much easier than calling during one.

eero Model Differences: Max 7, Pro 6E, 6+, 6, and Beacon

The LED behavior is consistent across the lineup, but the hardware behind it varies a lot. Knowing your model helps when you're diagnosing ports, backhaul, and speed caps.

The current lineup as of 2026

Two things jump out from that table. The Beacon has no Ethernet ports at all, so it can only work as a wireless leaf. And the PoE 6 is designed for ceiling or wall mounting with power over Ethernet, which makes it a pro-install option rather than a plug-and-play one.

Why the model matters for troubleshooting

If your gateway is an eero 6 or 6+, its Ethernet ports are gigabit. That's fine for most plans, but if you're on a multi-gig fiber tier, you're capped at 1 Gbps.

If you've got an eero Max 7, you can use the 10 GbE port for the WAN link and the 2.5 GbE port for a wired leaf or a switch. Getting those swapped by mistake is a common source of confusion.

The Beacon is the one that catches people off guard. If you're trying to run Ethernet backhaul to a Beacon, it won't work. There's no port.

eero Built-in and Echo devices

Some Echo devices act as eero extenders when paired with a compatible network. They add a bit of coverage but no new Ethernet ports.

If you've got an Echo Dot or Echo Pop doubling as an extender, treat it like a Beacon. Wireless only, and it depends entirely on the gateway.

Regional Setup Differences in the US, UK, and EU

The blinking red symptom is universal. The underlying causes shift depending on where you live and which ISP you're on.

United States

Cable dominates. Comcast Xfinity, Spectrum, Cox, and Optimum all use coax and DOCSIS modems. That means you're dealing with channel bonding, signal levels, and splitter issues.

Fiber is growing fast. AT&T Fiber, Verizon Fios, Google Fiber, and CenturyLink all use ONTs, and several require PPPoE or VLAN tagging.

US homes are also more likely to have a modem-router combo from the ISP. Double NAT is a frequent problem here.

United Kingdom

BT, EE, Sky, and Vodafone run on the Openreach network, which is mostly FTTP or FTTC. PPPoE is common.

Virgin Media runs its own HFC network on coax, which behaves more like a US cable setup.

UK homes often have a master socket or an Openreach modem, and the eero sits behind it. If the Openreach box has a red light, the problem is on the line, not the eero.

European Union and beyond

Germany's Deutsche Telekom, France's Orange, and Vodafone across Europe all use PPPoE for many connections. VLAN tagging shows up more often here than in the US.

Power runs at 230V and 50 Hz, so a US power adapter won't work. Make sure you're using the adapter that shipped with your regional unit.

Wi-Fi rules differ too. The 6 GHz band and DFS channels have different restrictions in different countries. That affects which channels your eero can use, though it rarely causes a red light.

What to ask your ISP no matter where you are

The questions are the same everywhere. Do I need PPPoE? Is there a VLAN ID?

Is there a MAC address lock? What are my modem signal levels?

Write those four down. They cover the majority of region-specific setup issues.

Safety, Warranty, and Compliance Notes

A few things are worth knowing before you start poking at hardware. None of them are dramatic, but they'll keep you out of trouble.

Don't open the eero case

There are no user-serviceable parts inside. Opening the case voids the warranty and won't reveal anything useful.

If a unit is genuinely dead, the fix is a replacement, not a repair.

Use the right power adapter

Match the voltage and amperage printed on the original adapter. A lower-amperage substitute can cause brownouts under load, which look like random reboots.

Never use a generic charger with unknown specs. The eero draws more current than a phone charger typically provides.

Fiber safety

If you have an ONT, the fiber connector emits invisible laser light. Never look into the end of a fiber cable or a connector.

The light is infrared and you can't see it. It can still damage your eyes. This is a real hazard, not a theoretical one.

Regulatory compliance

eero units sold in the US carry FCC Part 15 authorization. European units carry CE marking. UK units carry UKCA.

Wi-Fi Alliance certification covers interoperability, and WPA3 support is standard across the current lineup. Cable modems carry CableLabs certification for DOCSIS interoperability.

Thread border router features are certified by the Thread Group. Matter support comes through the Connectivity Standards Alliance.

Warranty coverage

The standard eero warranty is 12 months from purchase. Some models and bundles carry longer terms.

Keep your receipt. Warranty claims go through eero support, and they'll ask for the serial number and proof of purchase.

Account and privacy

Your eero network is tied to an Amazon account. Whoever controls that account controls the network.

Use a strong password and two-factor authentication. If you sell or give away an eero, remove it from your account first. Otherwise the new owner can't set it up, and you're still linked to their network.

eero Plus and subscriptions

eero Plus adds security features, ad blocking, and a VPN. It's optional. It has no bearing on whether your network works, but it does change what appears in the app.

If you cancel eero Plus, some app screens will look different. That's not a fault.

Frequently Asked Questions

How long does an eero blinking red usually last?

It lasts until the underlying connection issue is fixed. If the cause is a brief ISP blip, it may clear in a few minutes on its own. If the cause is a modem fault, a bad cable, or a missing ISP credential, it stays red until you address it.

Does blinking red mean my eero is broken?

No. Blinking red means no internet connection, not a hardware failure. The eero is working correctly and reporting accurately.

A genuinely dead unit usually goes dark or flickers rather than blinking red on a steady loop.

Can I fix blinking red without calling my ISP?

Sometimes. If the cause is a loose cable, a bad boot order, or a stuck node, you can fix it yourself in minutes. If the cause is an outage, a MAC lock, or missing PPPoE credentials, you'll need to call your provider.

What's the difference between blinking red and solid red?

Blinking red means no internet connection. The unit is healthy and retrying. Solid red means the unit itself hit an error it can't work through, which often points to a boot failure or a hardware fault.

Different symptoms, different fixes.

Will a factory reset fix a blinking red light?

Usually not, and it can make things worse. A factory reset wipes your network configuration. If the actual problem is the modem, the cable, or the ISP, you'll rebuild your network and still see a red light.

Always rule out the modem and ISP first.

Why does my eero blink red after a power outage?

Power outages often cause the modem and gateway to boot in the wrong order. The gateway wakes up before the modem is ready, gives up, and sits in a retry loop. Power-cycling in the correct order, modem first and then gateway, usually clears it.