What's going on

When your Google Wifi, Nest Wifi, or Nest Wifi Pro loses its internet connection mid-call, the primary node typically displays a solid yellow or pulsing orange status light. Unlike traditional routers with an entire row of dedicated diagnostic LEDs, Google devices condense their entire connection status into a single glow ring or front-facing LED.

Behind the scenes, the primary Google router acts as the WAN gateway for your entire mesh system. If it fails to acquire a Dynamic Host Configuration Protocol (DHCP) IP address from your Internet Service Provider (ISP), the WAN connection drops completely, isolating all downstream mesh points and connected client devices.

Symptoms people notice

• The primary Google point displays a persistent solid yellow, orange, or pulsing amber light.
• The Google Home app indicates the network is offline or that the WAN cable is unplugged.
• Connected devices report a strong Wi-Fi signal with "No Internet Connection."
• Ethernet ports on connected switches or client devices lose connectivity.
• The link LED on your ISP's optical network terminal (ONT) or cable modem turns off or blinks rapidly without establishing a solid link.

Likely causes

1. ISP MAC Address Binding: Cable modems frequently lock onto the hardware address (MAC) of the last connected router. If you swapped hardware or experienced a power blip, the modem may reject the Google router's WAN requests.
2. Ethernet Auto-Negotiation Failure: Google nodes auto-detect port speeds. A faulty Ethernet cable can prevent the router and modem from agreeing on a 1000Mbps link.
3. Double NAT / Subnet Conflict: If your ISP equipment is also acting as a router using the default 192.168.1.x space, it can block the primary Google point from properly routing WAN traffic.
4. Firmware Stack Freeze: A momentary cloud sync error or power anomaly can lock up the internal networking stack on the Google node.
5. Blown Ethernet PHY Chip: Physical hardware damage on the WAN port caused by lightning strikes or power surges over the copper Ethernet line.

Quick checks first

Before assuming your hardware is broken, perform these fast checks:

• Check the physical port: Ensure you plugged the modem cable into the dedicated WAN port (marked with a globe icon), not the LAN port (marked with <--->).
• Check for physical pin damage: Look inside the WAN port on the Google node with a flashlight. Look for bent, corroded, or missing gold contact pins.
• Bypass the router: Plug a laptop directly into your ISP modem with the same Ethernet cable. If the laptop doesn't get internet, the issue is with your modem or ISP, not the Google router. If you need broader hardware diagnostic steps, check our general router troubleshooting guides.

When it's a real hardware fault

If direct laptop testing proves your ISP modem is outputting normal internet, but your primary Google puck persistently fails to illuminate its link lights with multiple known-good cables, the WAN Ethernet controller (PHY) may be dead. Power spikes traveling down outdoor coaxial or fiber lines often claim router WAN ports while leaving the rest of the board running.

On older Google Wifi (AC1200) models, you can test if the hardware is fully dead by setting up a secondary puck as your primary router. If the secondary unit connects instantly to the modem, the original puck's WAN port has suffered a hardware failure.

Soft resets vs board/panel work

Google's mesh networking hardware is ultrasonically welded and sealed. There are no user-serviceable internal components, accessible serial ports, or socketed chips inside.

• Soft Resets & App Recovery: Soft resets, app-level network restarts, and factory restores using the hardware button clear 95% of standard WAN assignment and DHCP lease errors.
• Board-Level Repairs: Attempting to pry open a Google puck to repair an Ethernet port or motherboard circuit generally results in destroyed plastic housings and damaged internal Wi-Fi antennas. If the WAN port suffers a true electrical burnout, replacing the individual node is far safer and more cost-effective.

Next steps

If clean reboots and factory resets do not fix the yellow light, explore our dedicated Google brand hardware resource page for specific model quirks. If you decide it's time to upgrade your home network after a hardware failure, browse our objective hardware breakdowns in the LML Repair reviews section.