If the router still shows a local connection but the internet dies after the modem is restarted, the problem is usually in the modem-to-router handoff, not Wi‑Fi. Let the modem finish coming back online first. Then renew the router’s WAN session. If that fails, check DHCP, PPPoE, MAC binding, or passthrough issues on the WAN side. If the modem never becomes stable again, or the router only works after repeated resets, you may need ISP support.
Why the internet drops even though the router still looks online
The short version is that your local network can stay up while the upstream connection is down. Devices may still join the router’s Wi‑Fi and get a local address. At the same time, the router’s WAN side may have no live path to the ISP. A modem connects your home to the provider’s network, while the router builds the Wi‑Fi network your devices use.
After a modem restart, the modem has to boot and re-establish the line before the router can get a fresh WAN lease or session. If the router reaches that point too early, it can keep a stale WAN state. The inside network still looks healthy, but the outside connection is dead. In practice, that can show up as a router that still lights up normally, local devices that still connect, and no internet beyond the router.
The common causes are:
- Modem boot timing: the router asks for service before the modem is fully ready.
- DHCP: the router does not get a fresh WAN address.
- PPPoE: the router does not re-authenticate cleanly after the modem comes back.
- MAC binding: the ISP or modem expects the same WAN device identity as before.
- IP passthrough or bridge behavior: the modem hands off internet service in a way that can get stuck until the WAN side is renewed again.
A dropped connection, where the internet cuts out completely and comes back on its own or after a restart, usually points to the modem or connection side rather than the wireless side. That is why the modem and router status pages matter more here than the Wi‑Fi indicator.
Before you start
Check the modem and router admin pages before you change anything. You want to know whether the modem is online, whether the router has a WAN address, and whether the WAN type is DHCP, PPPoE, or passthrough.
On the modem status page, look for a normal online state. If the modem still shows booting, ranging, syncing, searching, or any other unfinished state, stop there and wait. Spectrum’s guidance notes that if a light stays in an unusual state for more than 10 to 15 minutes after a full power cycle, that is a sign to move on to the next steps.
On the router status page, check these fields if they exist:
- WAN or Internet status
- WAN IP address
- Gateway
- DNS servers
- Connection type, such as
DHCPorPPPoE
Those pages usually tell you where the break is. If the modem is online but the router has no WAN IP, the router never got a lease. If the router shows PPPoE connected locally but there is still no internet, the session may not have re-authenticated. If the WAN IP only returns after a manual reconnect, MAC binding or passthrough behavior is a likely suspect. If the router says the WAN is up but browsing still fails, DNS or ISP provisioning may be the real problem.
Do not start by factory-resetting either device. That makes diagnosis harder and can erase the settings you need to compare later.
Fastest recovery sequence
The safest fix is to wait for the modem to fully recover, then ask the router for a fresh WAN connection. That order matters because the router cannot renew a session against a modem that is still booting. If the modem never settles, stop there and call your provider instead of repeating resets.
- Wait for the modem to finish coming back online.
Leave both devices alone until the modem shows a stable online state on its lights or status page. If the modem is still changing status, keep waiting rather than rebooting again.
- Renew or reconnect the router’s WAN session.
Open the router’s WAN or Internet page and use the reconnect control if it has one. The label varies by model. Look for Reconnect, Renew, Release/Renew, Connect, or Disconnect/Connect.
WAN / Internet / StatusIf the router gets a new WAN IP, gateway, and DNS values, the handoff has been restored. If nothing changes, the router may be holding a stale lease or the modem may not be presenting a live WAN path yet.
- If the reconnect does not work, restart only the router.
Power off the router, wait a short moment, and bring it back up after the modem is already stable. This is the least disruptive restart when the modem is known good. If that restores internet, the problem was most likely a stale WAN session rather than a bad line.
- If you still have no internet, power-cycle both devices in the correct order.
Turn off the router first, then the modem. Wait until the modem is fully off. Turn the modem back on and let it come fully online. Only after that should you turn the router back on.
If the problem returns every time the modem is restarted, the failure is probably not random. That points to a WAN configuration issue, firmware behavior, or ISP provisioning problem rather than a one-time boot timing glitch.
What to change for your connection type
The fix depends on how the router gets internet service from the modem. Start with the connection type, then match the router settings to it. If you are not sure which mode you have, check the modem and router status pages first.
For DHCP, the router should be set to obtain its WAN address automatically. If there is a DHCP renew or release/renew option, use it after the modem is fully online. If the router keeps the old address, shows no lease, or comes back with no gateway, the WAN lease was not rebuilt cleanly.
For PPPoE, check the login details on the router. The username, password, and service settings have to match what the ISP expects. If the modem reboot breaks the session and it does not come back, the router may be failing to re-authenticate. If the credentials are correct but the session still will not return, the ISP may need to refresh the account or provisioning side.
For MAC binding, the upstream device may be remembering the first WAN device it saw. That can happen after a router swap, a MAC clone change, or a passthrough setup. Keep the WAN MAC setting consistent with how the service was originally set up. If you do not know whether MAC cloning is required, check the router’s WAN page and your ISP’s setup notes before changing it.
For IP passthrough or bridge mode, the modem is not routing in the normal way, so the router depends on a clean handoff. If the modem restarts and the passthrough lease does not follow cleanly, the router can still look alive locally while the public side stays dead. In that case, the usual repair is to renew or reconnect the router WAN after the modem is fully online. If that still fails, a modem reboot after it is stable may be needed, but only if your ISP’s setup expects that flow.
Do not switch between bridge mode and routed mode unless you know that is the intended service design for your line.
When firmware or ISP provisioning problems mean you need provider support
If the modem is fully synced, the router WAN settings are correct, and the connection still dies after every modem reboot, the remaining problem is often on the ISP side or in the device firmware. At that point, more resets usually will not help.
Call the ISP if you see any of these patterns:
- The modem never reaches a normal online state.
- The router does not get a WAN IP even after a correct reconnect.
- PPPoE fails even though the login details have not changed.
- The connection only returns after a long delay that changes from one restart to the next.
- The issue started after a firmware update or after the ISP pushed a new configuration.
Have this ready when you call: the modem model, the router model, the connection type, the exact WAN status you see, whether the modem comes online by itself, and whether a manual WAN renew helps. If you can, note the light behavior on both devices and how long the modem takes to become ready after a restart. That gives support something concrete to compare against line status and provisioning.
Verify the fix
The fix is working when the router shows a live WAN status, a valid gateway, and DNS servers after the modem has been restarted. Test a web page from a device connected to the router and make sure the internet works without another reconnect.
If the router only works right after a manual WAN renew, but fails again after the next modem restart, the handoff is still unstable. That usually means the modem boot timing, WAN session type, or ISP provisioning still needs attention.
If the modem status page and the router WAN page both look normal but internet access is still unreliable, the next step is provider support rather than more resets.
Conclusion
If the modem keeps restarting cleanly but the router loses internet every time, focus on the WAN handoff, not the Wi‑Fi. Check the modem and router status pages first, then involve your ISP if the WAN session will not stay up.
Frequently Asked Questions
Should I reboot the router first or the modem first?
If you need a full recovery, power off the router first, then the modem, and bring the modem fully online before turning the router back on. If you only need to recover from one modem restart, wait for the modem to finish booting and then renew the router’s WAN connection.
Why does my Wi‑Fi still work when the internet is gone?
Because Wi‑Fi and internet are different layers. Your devices can still connect to the router locally while the router’s WAN session to the ISP is dead. That usually points to DHCP, PPPoE, MAC binding, or passthrough timing, not a wireless fault.
What should I check first on the router status page?
Check the WAN or Internet section first. Look for a WAN IP address, gateway, DNS servers, and the connection type. If the WAN IP is missing, private, or only comes back after a manual reconnect, the break is upstream of the router’s local network.
Sources
- Router and Modem Troubleshooting: Quick Fixes That Work (spectrum.com)