If your Orbi still shows Wi‑Fi but loses internet every time the modem restarts, the WAN handoff is the problem, not the mesh radios. Start with the safest recovery sequence: power the modem fully off. Bring it fully online first, then start the Orbi router. After that, bring satellites back. If that does not work, check the Orbi status page to tell whether you have no WAN IP, a DNS problem, or an upstream modem/ISP failure.
What this symptom usually means
This usually means the local Orbi network is still alive while the internet side has not recovered cleanly after the modem reboot. Phones and laptops can stay connected to the Orbi SSID, but the router is no longer getting a working path to the modem or the ISP.
That split is why the failure feels odd. Wi‑Fi stays up, so devices look connected. But traffic stops at the WAN side of the Orbi router. In practice, the cause is often the modem-to-Orbi handoff, not the satellites.
A common case is a modem restart that is too quick. The modem may still hold the old router state. When the Orbi asks for a new lease or link, the modem does not answer cleanly right away.
Before you start
- Make sure you can reach the Orbi admin page or app before you change anything.
- Know whether your modem is a plain modem, a modem-router combo, or an ISP gateway. The behavior after a restart can be different in each setup.
- If your Orbi is connected through another router, a gateway, or a mesh satellite with Ethernet backhaul, note that path first so you can check the right cable and port.
- If you plan to test cables, have a known-good Ethernet cable ready.
- Check your ISP’s current guidance if the modem has a special provisioning step, bridge mode, or passthrough setting. Those details can vary by model and service plan, so the exact current instructions should come from the ISP or modem maker rather than memory.
The fastest restart order to try
- Unplug power from the modem and the Orbi router. If the satellites have separate power, leave them off too.
- Wait long enough for the modem to fully shut down. A longer power-off can clear stale state that survives a quick restart.
- Power on the modem only.
- Wait until the modem shows that it is fully online, not just powered on.
- Power on the Orbi router.
- Wait for the Orbi router to finish booting and request internet access.
- Turn on the satellites after the router has a working WAN connection, if they do not rejoin on their own.
If the internet comes back only after a longer modem power-off, that points to stale modem state, DHCP lease handoff, or MAC learning. That is a useful clue, but it is not a permanent fix if the failure returns every time.
How to read the Orbi status page
The Orbi status page tells you where the break is. Use it to separate a lost WAN address from a browsing problem.
If the WAN side shows disconnected or no IP, the Orbi did not get a usable address from the modem or ISP. That usually points to DHCP lease handoff, MAC address learning, bridge mode or passthrough behavior, or the modem not passing traffic after reboot.
If the Orbi shows a WAN IP but websites still do not load, the internet path may be up while name lookup is failing, the ISP is having trouble upstream, or the modem is only partially recovered. In that case, DNS can be the symptom, but it is not the first thing I would blame.
If the Ethernet link looks alive but traffic still fails, think about a cable, port, or link negotiation problem. The modem and Orbi may not be renegotiating cleanly after power loss, so the link looks connected even though the WAN path is unusable.
The practical split is simple: Wi‑Fi connected with no WAN IP means the handoff failed. WAN IP with no browsing means the problem is farther upstream or in name resolution. No clean Ethernet link means you should check the cable and port before changing settings.
When the modem, cable, or settings are the real blocker
If the Orbi loses internet after a modem restart only on the WAN side, look at the modem path before you blame the mesh. The usual blockers are DHCP lease handoff, MAC learning, bridge mode, passthrough, double NAT, or a cable and port problem.
DHCP lease handoff matters because the modem or ISP gateway may not hand the Orbi a fresh lease right away. MAC learning can make that worse if the modem remembers the last device on its port and delays or rejects the next one for a while. That is one reason a longer power-off sometimes works when a quick reboot does not.
Bridge mode and passthrough can also change what happens after a restart. Some modem-router combos behave differently once they lose power, so the same Orbi setup can reconnect cleanly in one case and stall in another. If the modem is already routing and the Orbi is also routing, double NAT can add another layer of trouble after reboot.
A cable problem can look exactly like an ISP outage. Check the Ethernet cable between the modem and the Orbi router first, then try a known-good cable. If the modem has more than one LAN port, try a different port too. If a port negotiates slowly or fails to come back cleanly after restart, the Orbi may show a dead WAN even though the modem itself is powered on.
If the problem started only after a reboot and nothing else changed, I would test the cable before touching Orbi settings. Then confirm the modem is in the mode you actually expect. A wrong assumption about bridge mode or passthrough can waste a lot of time and hide the real fault.
When to stop troubleshooting at home
Stop local troubleshooting when the same failure happens every time after a full modem restart, especially if it only happens with one modem model. That pattern usually points to a modem compatibility issue, an ISP-side lease or provisioning problem, or hardware that is no longer renegotiating cleanly.
If the modem needs an unusually long power-off before the Orbi can reconnect, treat that as a clue rather than a cure. It can clear stale state for a while, but if the symptom keeps returning, the underlying cause is still there.
Escalate to the ISP when the modem comes back online but the Orbi still cannot get a WAN IP, or when another router shows the same problem on the same modem. Replace the modem or the Ethernet cable when the issue follows the hardware, or when the WAN port will not link reliably after reboot.
If the Orbi admin page or app shows the WAN as disconnected every time after the modem restarts, and the clean restart order does not change that, the next step is usually ISP support or replacement hardware rather than more reboots.
Verify the fix
After you make one change, test the same failure mode again. Restart the modem. Wait for it to come fully online, then start the Orbi router. Confirm that the WAN status returns to connected.
Then open a website from a device that is still on the Orbi Wi‑Fi. If the page loads without needing a second reboot, the WAN handoff is working again.
If the problem only clears after a long modem power-off, repeat the test once more on a different day. If it keeps coming back with the same modem, that is a sign you need ISP help or different hardware, not another restart.
Frequently Asked Questions
Why does my Orbi stay connected to Wi‑Fi but lose the internet after the modem restarts?
Because the Wi‑Fi mesh can stay up while the WAN handoff fails. Your devices still see the Orbi, but the router may not get a fresh IP address, lease, or link from the modem after reboot. That leaves the local network active and the internet side broken.
Do I need to restart the modem and Orbi in a certain order?
Yes. Power down both, start the modem first, wait for it to fully come online, then start the Orbi router and satellites. That gives the modem time to clear old state before the Orbi asks for a new WAN lease. The order matters because it reduces stale handoff problems.
What if the Orbi gets a WAN IP but pages still won’t load?
That usually means the WAN link is up, but traffic still can’t pass cleanly. Check DNS, the modem’s mode, and the Ethernet cable next. The problem may be upstream or in the handoff rather than in Wi‑Fi, so the status page matters here.