How to Fix “WiFi Connected But No Internet” (2026)

Full signal bars, “Connected,” and nothing loads. It’s one of the most common networking problems there is — and the reason it’s so frustrating is that people start trying fixes at random before working out where the break actually is.

There are only three possible culprits: your device, your router, or your ISP. Two minutes of checking tells you which one, and that turns a guessing game into a short list. Start there.

Key Takeaway:
“Connected” only means your device reached the router. It says nothing about whether the router reached the internet. That gap is the entire problem.

Step 0: Find Out Where the Break Is

Do these three checks before touching any settings. They take two minutes and eliminate most of the fixes below.

Try a second device on the same Wi-Fi. If it’s also offline, your device isn’t the problem — skip straight to the router and ISP fixes.
Turn Wi-Fi off on your phone and use mobile data. If sites load, the internet is fine and the fault is inside your home.
Check your router’s lights. The internet or WAN light should be solid, not off, red, or flashing. That single light usually tells you whether your ISP link is up.

What You Found	Where the Problem Is
Only one device affected	That device — go to Section B
Every device affected, WAN light OK	Your router — Section A
Every device affected, WAN light off or red	Your ISP — Section C
Some sites load, others don’t	DNS — Section B, fixes 3 and 4
Apps work but browsers don’t	DNS or a captive portal — Section D

Section A: Every Device Is Offline

A1. Power-cycle in the right order

This resolves the large majority of cases, but the order matters and most people get it wrong.

Unplug both the modem and router from power.
Wait a full 30 seconds — this clears the hardware state rather than just rebooting.
Plug in the modem first. Wait until its lights settle, usually one to two minutes.
Only then plug in the router.

The modem has to establish its link with your ISP before the router can request an address. Powering them up together is why “I already restarted it” often didn’t work. If you’re unsure which box is which, see router vs modem.

A2. Check the router’s WAN status

Log into the admin panel — usually 192.168.1.1 or 192.168.0.1 — and find the Internet or WAN section. If it shows no IP address, or 0.0.0.0, or “disconnected,” your router isn’t getting an address from your ISP. That’s Section C.

A3. Check the physical connections

Reseat the cable between modem and router, and the line coming into the property. Coax and DSL connections work loose more often than people expect, and a partially seated cable produces exactly this symptom.

A4. Look for DHCP exhaustion

If you have a lot of devices, the router can run out of addresses to hand out. New devices then connect to Wi-Fi but never receive an IP. A restart clears it; expanding the DHCP range in the router settings prevents it recurring.

Section B: Only One Device Is Offline

B1. Forget the network and rejoin

Clears a corrupted saved profile, which is a surprisingly common cause. Have the Wi-Fi password to hand before you do this.

Windows: Settings → Network → Wi-Fi → Manage known networks → Forget
Mac: System Settings → Wi-Fi → Details → Forget This Network
iPhone: Settings → Wi-Fi → (i) → Forget This Network
Android: Settings → Network → Wi-Fi → long-press network → Forget

B2. Release and renew your IP address

Forces a fresh address from the router, resolving conflicts and stale leases.

Windows — Command Prompt as administrator:

ipconfig /release
ipconfig /renew

Mac: System Settings → Network → Wi-Fi → Details → TCP/IP → Renew DHCP Lease.

B3. Flush the DNS cache

If some sites load and others don’t, stale DNS entries are a likely cause.

Windows: ipconfig /flushdns
Mac: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
iPhone/Android: toggle airplane mode, or restart the device

Full instructions per platform: How to Flush DNS Cache.

B4. Change your DNS servers

If your ISP’s resolver is failing, everything appears broken even though your connection is fine. Set DNS manually to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) and retest. See how to check your DNS settings, and if this turns out to be the cause, DNS server not responding goes deeper.

B5. Reset the network stack

On Windows, run these as administrator, then reboot:

netsh winsock reset
netsh int ip reset

On iPhone: Settings → General → Transfer or Reset → Reset → Reset Network Settings. On Android: Settings → System → Reset → Reset Wi-Fi, mobile & Bluetooth. Both wipe saved Wi-Fi passwords, so have them ready.

B6. Check your system clock

An easily-missed one. If your device’s date and time are significantly wrong, HTTPS certificate validation fails and virtually every site refuses to load — while the connection itself is perfectly healthy. Set time to update automatically.

B7. Check for VPN or proxy leftovers

A VPN that crashed can leave a kill switch active, blocking all traffic by design until it reconnects. Old proxy settings do the same. Fully quit the VPN app, and check your system proxy settings are off.

B8. Disable and re-enable the adapter

Windows: Device Manager → Network Adapters → right-click your Wi-Fi adapter → Disable, wait ten seconds, Enable. If it keeps dropping, update the adapter driver — a genuinely common cause after Windows updates.

Section C: It’s Your ISP

If the router shows no WAN address after a proper power-cycle, the problem is outside your house and nothing you change will fix it.

Check for an outage on your provider’s status page or app, using mobile data.
Check your account — service suspensions for billing produce exactly this symptom.
Call them, and say specifically: “My router shows no WAN IP address after a power cycle.” That phrasing skips several tiers of scripted troubleshooting.
Ask if they can see your modem on their end. If they can’t, it’s a line or hardware fault and they’ll need to send someone.

Section D: Odd Cases Worth Knowing

Captive portal never appeared. On hotel, café, airport or campus Wi-Fi you must accept a login page first. If it didn’t pop up, browse to http://neverssl.com — an HTTP site forces the portal to appear, where HTTPS sites silently fail.
IP address conflict. Two devices assigned the same address, usually from a manual static IP clashing with the DHCP range. Release and renew, or remove the static assignment.
MAC filtering. If the router has an allow-list, a new device connects to Wi-Fi and gets nothing. Check the router’s access control settings.
Antivirus or firewall. Some security suites block all traffic after an update. Temporarily disable to test, then re-enable.
IPv6 misconfiguration. A partly-working IPv6 setup can cause devices to prefer a broken route. Disabling IPv6 on the adapter is a valid diagnostic — see IPv6 explained.
Wi-Fi extender or mesh node offline. The extender still broadcasts its network while having lost its own link upstream, so you connect successfully to a dead end.

Windows Users: A Note

If Windows specifically shows “No Internet, Secured” next to your network name, that’s the same underlying problem with a Windows-specific label — and it has a few causes unique to Windows. We cover those separately in How to Fix “No Internet, Secured” on Windows.

Stopping It Happening Again

Update your router firmware. Stability fixes land here, and most routers never update themselves.
Set DNS at the router to a reliable public resolver, so every device inherits it.
Replace ageing hardware. Routers degrade; one that needs weekly restarts is telling you something.
Reduce interference. Move the router away from microwaves and cordless phones, and use the 5GHz band where you can.
Don’t set static IPs inside the DHCP range — reserve addresses in the router instead.

Frequently Asked Questions

Why does it say connected if there’s no internet?

Because those are two separate things. “Connected” confirms your device successfully joined the router’s network. Whether the router can reach the wider internet is a completely different link, and your device can’t see it.

Why does restarting the router fix it so often?

It clears stale DHCP leases, resets the NAT translation table, forces a fresh address from your ISP, and flushes the router’s own DNS cache — several likely causes at once.

Only one device is affected. Why?

Almost always something local to it: a corrupted network profile, a stale DHCP lease, an IP conflict, wrong DNS, or a VPN kill switch still active. Work through Section B.

Some websites load and others don’t. What’s that?

Classic DNS failure. Your connection is fine; name resolution isn’t. Flush your DNS cache and switch to a public resolver — see how DNS works.

How do I know if it’s my ISP?

Check the router’s WAN status. No IP address there after a proper power-cycle means your router never got one from your provider, and that’s their side of the line.

Should I reset my router to factory defaults?

Only as a last resort. It wipes your Wi-Fi name, password and every custom setting. Try everything else first, and note your settings before you do it.

Could my VPN be causing this?

Yes, and it’s easy to miss. A kill switch blocks all traffic when the tunnel drops — that’s its job. If the app crashed, the block can persist. Fully quit the VPN and retest.

It works on mobile data but not Wi-Fi. What does that mean?

It confirms your phone is fine and the internet is fine. The fault is your Wi-Fi network — router or ISP. Start at Section A.