Wi-Fi Connected But No Internet? How to Fix It
Full signal bars and still nothing loads. In most cases this is not a broken line — it is a router that has hung, a stale IP lease, or a DNS setting that stopped resolving. A proper power-cycle clears roughly 60% of these; switching your DNS to 1.1.1.1 or 8.8.8.8 fixes most of what is left. Before you touch anything, find out which layer is actually broken so you fix the right box.
First, find out which layer is broken
Three things sit between you and a web page: your device, your router, and your ISP. Fixing the wrong one is how people waste an hour. Sort it in two checks.
- Is it one device or all of them? Try two or three other devices on the same Wi-Fi, and put a phone on cellular data (turn its Wi-Fi off) to confirm the phone itself works. If only one device is affected, this is not a router or ISP problem at all — skip to the single-device guide.
- Is the line even up? Look at the modem’s Internet/WAN light. Solid is good — the modem has a signal and the fault is on your side. Off, blinking, or red points at the ISP.
Before you change a setting, confirm what is actually failing — run the Network Test. Watch the latency step: if it measures a real ping to a server, packets are reaching the internet and your problem is local configuration, not a dead connection. If latency never resolves, nothing is getting out — go straight to the reboot and outage checks below.
Fix 1 — Power-cycle the modem and router the right way
This is the highest-value single move and it clears the majority of cases, because most "no internet" states are just a memory or state glitch in the router that a clean restart wipes. Do it properly — a rushed toggle leaves the stale state intact.
- Unplug both the modem and the router from power (pull the plug — don’t rely on a switch you are not sure about).
- Wait at least 30 seconds so the internal memory fully discharges and the cached state that caused the hang is actually cleared.
- Plug the modem back in first. Wait 60–120 seconds for its lights to stabilize.
- Then power the router, wait for it to come up, and reconnect your devices.
Order matters: the router needs a live modem to sync against. Rebooting during a peak-hour slowdown can also clear transient ISP-side congestion on its own.
Fix 2 — Switch your DNS to 1.1.1.1 or 8.8.8.8
If the reboot did not do it, DNS is the most likely remaining culprit. DNS is the service that turnsexample.com into an address your device can reach; when it fails, everything "loads" forever even though the connection is live. Point the device at a fast public resolver.
Windows 11
Settings → Network & internet → Wi-Fi (or Ethernet) → click your connected network → Edit next to "DNS server assignment" → switch toManual → toggle IPv4 on → Preferred DNS 1.1.1.1, Alternate 1.0.0.1 (or Google 8.8.8.8 / 8.8.4.4) →Save.
macOS
Apple menu → System Settings → Network → select the active Wi-Fi or Ethernet connection → Details… → DNS tab → click +and add 1.1.1.1, then 1.0.0.1 → OK → Apply. A restart may be needed for it to take full effect.
The whole network at once (router)
Log into the router admin page (commonly 192.168.1.1 or 192.168.0.1) → findWAN / Internet / DHCP settings → change DNS from Automatic to Manual→ enter 1.1.1.1 and 1.0.0.1 → Save → reboot the router. Many routers cache old DNS responses, so the reboot is what makes the change stick network-wide.
Flush the local cache while you are at it
- Windows: open Command Prompt as administrator and run
ipconfig /flushdns— it confirms "Successfully flushed the DNS Resolver Cache." - macOS: in Terminal run
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder— both commands are needed, one clears the resolver, the other restarts the mDNS service.
Fix 3 — Clear an IP or DHCP conflict
When the router’s lease table gets corrupted or its address pool is exhausted, it can hand out a duplicate IP — devices then fail to get online or drop at random. You do not need a full reboot to fix a single machine.
- Windows: Command Prompt →
ipconfig /releasethenipconfig /renew. This drops the current lease and requests a fresh one, usually in under a minute. - At the router: if the pool keeps exhausting, reserve static IPs outside the DHCP range for always-on devices (printers, NAS, cameras) so they stop colliding with the pool.
Fix 4 — Trigger a stuck captive portal
On hotel, airport, campus, or some ISP-provided networks, the login page is supposed to pop automatically — when it does not, you are "connected" with no internet until you sign in. Force it:
- Open a browser and go to a plain
http://address (not https) — an unencrypted request is far more likely to trigger the redirect than an app or an https site. - Toggle Wi-Fi off and on, or Forget this network and reconnect, to clear a cached "already authenticated" state.
- Temporarily disable any VPN — VPNs and some security apps intercept the exact probe traffic the portal needs to see.
Fix 5 — Rule out an ISP outage
If every device is down and the modem’s WAN light is off or red, stop troubleshooting your settings — the problem is upstream. Check Downdetector for your ISP, then its official status page or app for an estimated restoration time. A fast informal check in 2026 is to search "[ISP name] down" on X or Reddit for real-time local reports. There is nothing to fix on your end during an outage but wait.
Last resort — Windows 11 network reset and drivers
If DNS, DHCP, and a reboot all fail on a specific Windows PC, wipe its network stack. This is the nuclear option — it removes and reinstalls every adapter and clears your saved Wi-Fi passwords and VPN configs.
Settings → Network & Internet → Advanced network settings → More settings → Network reset → Reset now → confirm, then restart.
A corrupt Wi-Fi driver — common right after a Windows feature update — is a rarer but real cause. InDevice Manager → Network adapters, right-click the Wi-Fi adapter →Update driver → Search automatically; if that fails, Uninstall deviceand restart to let Windows reinstall a stock driver. While you are there, open the adapter’sPower Management tab and uncheck "Allow the computer to turn off this device to save power" — that setting quietly kills the radio and causes intermittent drops.
What does not actually work
"More bars means a better connection." Bars measure raw signal strength, not whether traffic is flowing. You can sit at full bars with zero internet if the fault is DNS, DHCP, or an outage — signal has nothing to do with any of them.
"Just restart the computer, it fixes everything." A device restart clears local state (it release/renews DHCP and flushes caches), which is useful — but it does nothing for a hung router or an ISP outage. Restarting the wrong box is the classic time-waster. Diagnose the layer first.
"Toggling Wi-Fi off and on fixes DNS." It can clear a stale captive-portal or association state, but it does not touch a broken DNS resolver setting. Conflating the two is how people skip the fix that would have actually worked.
When it is the ISP, not you
You have done your part once the modem’s WAN light is solid, one device works on the same network, and DNS is set to a public resolver. If the WAN light stays off or red, an outage tracker confirms a regional problem, or nothing you do restores service, the fault is on the line — call the ISP with the modem light status in hand rather than resetting anything else. If a specific device still fails while others are fine, the hardware is not the issue; that is a device-level problem covered in thesingle-device guide.
FAQ
What does "connected but no internet" actually mean?
Your device has a working link to the router — it got a Wi-Fi signal and an IP address — but traffic is not making it out to the wider internet. The break is somewhere past the router: a bad DNS setting, a stale IP lease, an unfinished captive-portal login, or an outage at the ISP. The Wi-Fi radio itself is fine, which is why the signal bars look full.
How do I know if it is my router or my ISP?
Check the modem’s Internet/WAN light. Solid means the modem has a signal from the ISP and the fault is likely on your side (DNS, DHCP, a hung router). Off, blinking, or red points upstream to the ISP. Cross-check by seeing whether every device is affected — if all of them are, and the WAN light is bad, it is almost certainly the ISP, not your settings.
How long should I unplug my router before restarting it?
At least 30 seconds. That is the commonly cited minimum for the capacitors and memory to fully discharge so the cached state that caused the hang is actually wiped, not just soft-reset. Plug the modem back in first, wait 60–120 seconds for its lights to settle, then power the router.
Will changing my DNS server fix "no internet"?
Often, yes — DNS failure is the single most common cause of a connected-but-no-internet state once you rule out an outage. Switching to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) and flushing the local DNS cache resolves it in many cases. It will not help if the real problem is a router hang or an ISP outage, so try the reboot first.
Why does one device show no internet but others are fine?
Then it is not a router or ISP problem — the fault is local to that one device. That is a different diagnosis entirely (band, VPN, driver, a stuck proxy). Work through the single-device guide instead of rebooting hardware that is serving everything else correctly.