Access point loses internet after router reboot: 3 checks
By Daniel Brooks Published 13 min read
On this page (8 sections)
- The short version
- Why the access point disconnects from internet after router reboot
- Check 1: whether the access point itself is still working
- How to verify DHCP and IP lease status on the AP and router
- What to check on router settings that block AP internet after restart
- Common mistakes and myths when the internet drops after a reboot
- How to get a stable connection that survives the next reboot
- Questions people still ask
In short: When an access point loses internet after a router reboot, the cause is usually a stale IP address, a DHCP lease the AP never renewed, or a router setting that changed on restart. Work through three checks in order: the AP's own link status, the DHCP lease on both devices, then the router's settings.
Part of our guide on spotting speed test timeouts
The Wi-Fi bars lie to you – here are the three checks that tell you which of the three devices actually broke.
| First check | AP link and ping status |
|---|---|
| Second check | DHCP lease on both devices |
| Third check | Router firewall and LAN settings |
| Typical cause | Stale or conflicting DHCP lease |
| Boot order | Router first, then AP |
| Test tool | ping and the router admin page |
The short version
- Check in order: AP link status, then DHCP leases, then router settings – each check rules out one layer.
- If devices can ping the AP but not the router, the AP is fine and the problem is upstream.
- Most cases are a DHCP issue: the AP kept its old lease or grabbed a new IP the router blocks.
- A static IP set on the AP that collides with the router's new DHCP range is a classic silent failure.
- Reboot the AP after the router finishes booting, not at the same time.
Why the access point disconnects from internet after router reboot
An access point does not connect to the internet itself. It is a bridge: it takes Wi-Fi traffic from your devices and passes it, over one Ethernet cable, to the router. When the router reboots, that bridge keeps standing – but everything on the other side of it changes, and the AP often does not notice.
Three things can go wrong during a router restart, and each lives at a different layer. The router itself may come back in a bad state. The DHCP server inside it may hand out addresses in a way the AP does not expect. Or a router setting – firewall, VLAN, MAC filtering – may load differently after the reboot than before it.
The trick is that all three look identical to you. Your phone shows the Wi-Fi name, signal bars full, yet pages will not load. That is because the AP is still broadcasting and still connected to your device; only the path from the AP onwards has broken. So the symptom never tells you the layer.
That is why guesswork wastes hours. People reboot the AP, re-pair devices, even factory-reset the AP, when the actual fault sits in the router's DHCP pool. The three checks in this article split the problem cleanly: check one clears or blames the access point, check two clears or blames DHCP, and check three covers whatever the router does to the connection after it restarts. We go through data flow in home network step by step elsewhere on the site.
| What you see | Most likely layer | Check that confirms it |
|---|---|---|
| Devices connect to Wi-Fi but no pages load | Path beyond the AP | Check 1: ping the router from a connected device |
| Router admin page unreachable from Wi-Fi but works on cable | AP-to-router link or DHCP | Check 2: compare DHCP leases |
| Works on cable, dead on Wi-Fi, every time after a reboot | Router setting loading wrong | Check 3: firewall, MAC filter, VLAN settings |
Check 1: whether the access point itself is still working
Start by separating the access point from everything behind it. Connect a phone or laptop to the AP's Wi-Fi, then try to reach two different targets: the AP's own admin address and the router's admin address. The AP admin page is usually something like 192.168.1.2 and the router something like 192.168.1.1, but check the labels or your notes.
If you can open the AP's own settings page over Wi-Fi, the AP is alive, its Wi-Fi radio works, and your device has an IP address. That already rules out a dead AP. If you cannot reach it either, the AP itself has hung – a power cycle of the AP alone will usually fix that, and the problem was never the router reboot at all.
Next, ping the router. On Windows, open Command Prompt and type ping 192.168.1.1 with your router's actual address. On Mac or Linux, the same command runs in Terminal. A reply means the path from your device through the AP to the router is intact. Timeouts mean the AP has lost its link to the router, or your device lost its IP. If that sounds like your situation, read up on steps to recover wifi network next.
Run the same ping from a device plugged into the router by cable if you have one. Cable working while Wi-Fi fails strongly suggests the AP side. Both failing points at the router. This single test, done in two minutes, halves the search space – and it is why it comes first.
One more quick look: most APs have a status or system page showing whether the wired uplink is connected. A lit Ethernet indicator on the AP and an 'uplink connected' status means the physical link survived the reboot.
- Join the AP's Wi-Fi network on your phone or laptop.
- Open the AP's admin page in a browser; if it loads, the AP is alive.
- Ping the router's IP address and note whether you get replies.
- Repeat the ping from a cabled device to compare the two results.
- Write down which targets answered – you will need it for check 2.
How to verify DHCP and IP lease status on the AP and router
DHCP is the service that hands out IP addresses. After a reboot, a router's DHCP server can come back with a different address pool, a fresh lease table, or a restarted lease timer – and the access point, which often holds an address for hours or days, may not ask for a new one. This mismatch is the single most common cause of an AP losing internet after a router restart. People in this spot often ask about nest wifi pro 5ghz speed low as well.
Look at both ends. On the router's admin page, find the DHCP client list or 'attached devices'. Check whether the AP appears there at all, and what address it shows. On the AP's admin page, find its network or LAN settings and see what address it believes it has. The two must match.
Three mismatches tell three different stories. If the AP lists an address the router does not show, the AP's lease expired and it never renewed – force a renewal from the AP's own settings, or power cycle the AP now that the router is up. If the AP holds an address outside the router's DHCP pool, someone set a static IP on the AP and the router's reboot changed the pool range around it.
The nastiest version is a duplicate: the router hands its own new address to something else that the AP was using as a static assignment, and traffic stops. A static IP is fine, but only if it sits outside the DHCP pool – for example pool from 192.168.1.100 upwards, AP fixed at 192.168.1.10. If the pool starts at .2 instead, collisions are a matter of time. The other half of this decision is stabilizing internet connection.
Fix it properly rather than rebooting every time. Give the AP either a static address outside the pool or a DHCP reservation in the router, so the router always gives the AP the same address. Then the boot order stops mattering, because the AP's address never changes however many times the router restarts.
| What the leases show | Meaning | Fix |
|---|---|---|
| AP has an address the router's list does not show | Lease expired and was never renewed | Renew from the AP settings or power cycle the AP |
| AP address falls outside the router's DHCP pool | Static IP set before the pool changed | Move the static address outside the pool, or add a reservation |
| Two devices share one address in the router list | Duplicate assignment after reboot | Reserve unique addresses; reboot the conflicting device |
What to check on router settings that block AP internet after restart
If the AP is alive and its DHCP lease is correct but the internet still will not flow, the remaining suspect is the router's own configuration. Some routers rebuild parts of their configuration at boot, and a setting that loaded correctly before can load differently after a restart – especially if the router itself was rebooted after a firmware update or a factory reset rather than a simple power cycle.
Work through the short list below. You do not need to change anything yet; you only need to confirm each setting is the same as before the reboot. Screenshots taken while things worked are gold here, because 'same as before' is otherwise hard to remember. If that sounds like your situation, read up on safety of public cafe wifi next.
Start with MAC filtering and access control, since those list specific devices and a reboot can re-scan the network before the AP has re-registered. Then check guest network or VLAN isolation, which can silently put the AP's Wi-Fi clients on an isolated segment with no internet route. Finally check the firewall or 'block new devices' rules, which some routers enable by default after an update.
- MAC filtering or access control: is the AP's MAC address still on the allowed list?
- Guest network or AP isolation: are Wi-Fi clients accidentally placed on an isolated segment?
- Firewall and new-device blocking: did a rule appear that was not there before the reboot?
- DNS settings: did the router fall back to default DNS servers that are not responding?
- Firmware state: did the reboot follow an update that reset settings to defaults?
Common mistakes and myths when the internet drops after a reboot
Most of the wasted time on this problem comes from fixing the wrong layer. The myths below come up again and again in forums, and each one sends you away from the actual fault.
The deeper mistake is testing with the wrong device. Testing on a device connected by cable tells you about the router; testing on Wi-Fi tells you about the AP. People mix the two results together and conclude nothing. Always know which device you are testing from and how it is connected before you read the result.
| Myth | Fact |
|---|---|
| Full Wi-Fi bars mean internet is working | Bars only show the link between device and AP – the break is usually beyond it |
| Rebooting the AP fixes a DHCP problem | It may renew the lease once, but the fault returns on the next router reboot |
| A stronger signal or new AP is needed | Signal strength is irrelevant when the Ethernet path or lease is broken |
| The router reboot caused the fault | The reboot often only reveals a setting or lease that was fragile all along |
How to get a stable connection that survives the next reboot
Once the three checks have named the culprit, the permanent fix takes minutes. For a DHCP cause, give the AP a DHCP reservation in the router or a static address outside the pool, then power cycle the AP once. For a boot-order cause, adopt a fixed sequence: router fully up first, wait two minutes, then the AP, then any mesh satellites.
For a router-setting cause, write down the correct configuration and take screenshots, so the next reboot has a reference point. Households and small offices that add devices often find it worth keeping a simple note of every fixed address on the network – one sheet, five lines, and future faults turn into lookups instead of investigations.
A related upgrade is a mesh Wi-Fi system, where the 'access points' are managed by the same controller as the router and re-register automatically after restarts. If your current setup is a standalone AP bolted onto a separate router, and the reboots keep biting, replacing the pair with a managed mesh set removes the whole class of problem rather than patching it. It is an expense, not a necessity – only go there if the checks in this article keep landing on the same fragile seam.
Whatever hardware you keep, the routine that prevents repeats is the same: fixed addresses for network equipment, a known boot order, and a screenshot of the router settings while everything works. Ten minutes of setup buys you a network that comes back cleanly on its own after every power cut, update and reboot.
- Assign a DHCP reservation or an out-of-pool static IP to the access point.
- Power cycle the AP so it takes the new address.
- Set a boot order habit: router first, AP two minutes later.
- Screenshot the router's key settings while the network works.
- Re-test with a planned reboot – if the internet survives, the fix is done.
Questions people still ask
Why does my Wi-Fi connect but say no internet after a router restart?
Your device still has a working link to the access point, so the Wi-Fi symbol shows normally. The break sits between the AP and the wider internet, most often a DHCP lease the AP did not renew after the router came back. The three checks in this article pinpoint which layer dropped.
Should I reboot the access point or the router first?
Router first, and wait until it has fully finished booting – usually two minutes with all lights settled – then reboot the AP. If the AP asks for its IP address before the router's DHCP server is ready, you can end up with the exact failure you are trying to fix.
How do I know if the problem is DHCP and not the access point?
If you can open the AP's own admin page over Wi-Fi, the AP is alive. Then compare the address it holds with the router's DHCP client list: a missing, stale or out-of-range address on the AP side means DHCP is the culprit, not the hardware.
Can a firmware update on the router cause this every time?
Yes. Some updates reset settings to defaults or change how the firewall and DHCP behave at boot, so the fault repeats after every restart. Check the router's firmware page for a newer version, and compare your settings against screenshots taken when the network last worked.
Is a static IP on the access point always the answer?
It is a good answer only when the address sits outside the router's DHCP pool, or better, when the router has a DHCP reservation for the AP. A static address inside the pool works until the router hands that address to another device after a reboot, and then the connection dies again.
When should I just replace the access point or router?
Only after the three checks point repeatedly at the same hardware with no setting to fix it. Hardware that hangs at every reboot, or firmware whose settings shuffle on restart, is worth replacing – but most cases in this situation turn out to be a lease or setting, not broken equipment.