When the router admin page says connected but devices have no internet, the likely causes are DNS, WAN routing, stale leases, provider provisioning, modem handoff, firmware or router services stuck internally.
Start by proving the scope: one app, one device, one adapter, one printer path or the whole network. That comparison decides whether the fix belongs in Windows, iPhone settings, router WAN, AirPrint discovery or app cache.
Start with what still works
A router admin page that says connected can be misleading. It may mean the router has a WAN IP, sees the modem, or believes the provider session is active. It does not always prove devices can resolve DNS, pass traffic through NAT, receive clean DHCP leases or reach websites. That is why every phone and laptop can say no internet while the router dashboard still looks cheerful. The router is reporting one layer of the connection, not the whole journey from device to website.
The right fix is to check what connected actually means inside the router. Look at WAN IP, gateway, DNS and system logs, then test whether devices can reach the router, whether they receive good IP settings and whether DNS is failing. Restarting the router may help, but if the pattern repeats, you need to find whether the stuck layer is WAN, DNS, DHCP, firewall or provider handoff.
Quick diagnosis table
Try these fixes in order
Use this order so you solve the likely cause before resetting settings or replacing hardware.
- 01
Check the full WAN block
Do not stop at the word connected. Look for WAN IP, gateway and DNS. If one is missing, the dashboard is hiding the useful part.
- 02
Test DNS from one device
If direct IP tests work but websites fail, DNS is the likely break. Try a reliable DNS resolver on the router as a controlled test.
- 03
Renew DHCP leases
Devices may have stale local settings even if the router is online. Disconnect and reconnect one device or restart DHCP from the router if your model allows it.
- 04
Restart modem first, router second
A clean upstream restart can rebuild the WAN path. Let the modem or ONT fully stabilize before powering the router.
- 05
Check router logs
Look for WAN drops, DNS errors, DHCP failures, overheating, memory warnings or repeated service restarts.
- 06
Update firmware
A router can show connected while internal services are stuck. Firmware updates often fix stability, DNS proxy and DHCP bugs.
- 07
Disable custom rules briefly
Pause VPN client mode, ad-block DNS, custom firewall rules or parental controls. Retest one device before restoring rules.
- 08
Factory reset only after saving settings
If the router repeatedly says connected while no device can use the internet, reset may help, but export settings or write them down first.
- 09
Confirm the fix after a restart
After the issue appears fixed, restart the device once and test again. A fix that survives restart is much more useful than one that only works until the next sleep, app update or router refresh.
Detailed checks
The dashboard is a shortcut, not proof
Router apps simplify status because most people do not want to read WAN details. That simplicity can hide the exact failed layer.
- A real diagnosis needs WAN IP, gateway, DNS and device lease information.
DNS proxy can fail inside the router
Many routers act as a DNS relay. Devices ask the router, and the router asks outside DNS. If that relay gets stuck, devices fail while WAN still says connected.
- Changing DNS or restarting the DNS service can reveal the issue.
Provider handoff can look connected but not route
Sometimes the router has an address but the provider path is not passing traffic correctly. This can happen with stale provisioning or partial outages.
- A direct modem test or provider support check separates router failure from upstream failure.
The repeat pattern matters
If this happens every night, after heavy streaming or after several days of uptime, look for firmware, heat, memory or scheduled provider lease renewal.
- The timing can tell you more than the front light.
Why the first successful test is not enough
Home network and device problems can look fixed for a few minutes, then return when the app refreshes, the device sleeps or the router renews a lease.
- That is why a second test matters. It catches temporary fixes before you publish the problem as solved in your own notes.
Mistakes to avoid
Do not assume connected means every service path is working.
Do not skip VPN, DNS, proxy, driver or local discovery checks.
Do not change several settings together. One clean test gives better evidence.
FAQ
Why does my router say connected but there is no internet?
Because connected may only mean the router has a WAN link or address. DNS, routing, DHCP or provider authorization can still be broken.
Check WAN IP, gateway and DNS instead of trusting the label alone.
Is this a modem problem?
It can be, especially if the router cannot pass traffic after a modem-first restart or direct modem test fails.
If direct modem works, the router settings or services are more likely.
Can DNS cause all devices to fail?
Yes. If the router DNS proxy fails or the provider DNS is bad, every device may look offline.
Try a router-level DNS change and test again.
Should I factory reset the router?
Not first. Resetting erases useful settings and can create more work.
Check WAN details, DNS, DHCP, firmware and custom rules first.
Why does rebooting fix it temporarily?
A reboot restarts router services and renews leases. If the issue returns, something is getting stuck again.
Check logs, firmware, heat and scheduled lease renewal timing.
Can parental controls cause this?
Yes. Bad rules or security filters can block traffic broadly or by device.
Pause them briefly and retest one device.
What if only one device has no internet?
Then the router is probably not fully broken. Check that device's IP, DNS, VPN and saved network settings.
All-device failure points higher up the network.
When should I call the provider?
Call when WAN status looks wrong, direct modem testing fails or the router has a valid WAN IP but no traffic passes after basic checks.
Use precise wording: router says connected, but no devices can reach the internet.
How do I keep it from happening again?
Update firmware, improve router ventilation, remove unstable custom rules and track when the failure happens.
If it repeats under light use after updates, hardware replacement may be reasonable.
Outside references
- ASUS Support
Model-specific router firmware and WAN troubleshooting reference.
- TP-Link Support
Official router support reference for WAN, DHCP and firmware checks.