"Connected, no internet" means exactly what it says, and once you read it literally, the fix gets much easier. Your device has a working wireless link to the router. The router, however, has no working route to the internet, or something in between (usually DNS) is broken. So the WiFi part of "WiFi connected but no internet" is fine. Your job is to find which link in the chain beyond it has failed: the router's connection to the modem, the modem's connection to your provider, or the address book (DNS) your device uses to find websites.

The fastest way to do that is to check whether the problem hits one device or all of them, then restart the right box in the right order. Here is the whole process.

The chain your traffic actually travels

Every web page you load crosses at least four links: your device to the router over WiFi, the router to the modem (sometimes the same box), the modem to your internet provider, and finally DNS, the service that translates "example.com" into a numeric address. "Connected" only describes the first link. Any of the other three can fail while your WiFi bars stay proudly full.

This is why rebooting your laptop five times accomplishes nothing when the actual failure is at your provider, and why the single most useful diagnostic question is the one in the next section.

One device or all devices?

Before touching anything, grab a second device (phone, tablet, anyone's) and check whether it can load a website on the same WiFi. Sixty seconds here saves you from fixing the wrong thing.

What you findWhere the problem lives
Only one device has no internetThat device: its network settings, DNS, or VPN
All devices on WiFi are downThe router, the modem, or your provider
WiFi devices down, wired computer worksThe router's wireless or routing side
Everything down, modem lights abnormalYour provider's line or the modem

Phones make this even easier: turn WiFi off on your phone and let it fall back to mobile data. If websites load on mobile data but not on WiFi, the problem is definitely in your home chain, not with the wider internet.

The fix, in order

  1. Check every device on the network. Establish whether this is a one-device problem or an everyone problem using the table above. Everything after this step depends on the answer.

  2. Restart the modem and router, in the right order. Unplug both from power. Wait 30 seconds. Plug in the modem first and wait until its indicator lights settle (usually one to two minutes). Then plug in the router and give it another two minutes. Powering the router before the modem is ready is how you end up "connected" to a router that never got an internet address itself.

  3. Look at the modem's lights while you wait. Most modems have an internet or online light. If it is off, blinking endlessly, or red after a full restart, the problem is between the modem and your provider. Check your provider's outage page or app on mobile data before doing anything else, because you cannot fix an outage from your living room.

  4. On a single affected device, forget and rejoin the network. In WiFi settings, tell the device to forget the network, then reconnect and re-enter the password. This rebuilds the stored configuration, which fixes a stale or broken address assignment more often than it has any right to.

  5. Turn off VPNs and "private DNS" features. A VPN whose server is down produces exactly this symptom: connected to WiFi, nothing loads. The same goes for private DNS or secure DNS settings pointed at a dead server. Disable them temporarily and retest before you blame anything else.

  6. Try a different DNS server. If pages will not load but video calls or some apps still work, DNS is the prime suspect. In your device's WiFi settings, set DNS manually to a well-known public resolver such as 1.1.1.1 or 8.8.8.8, then retest. If that fixes it, your provider's DNS was the problem, and you can keep the new setting permanently.

  7. Renew the device's network lease. Toggling airplane mode on and off (phones) or disconnecting and reconnecting the adapter (computers) forces the device to request a fresh address from the router. Devices that show "connected, no internet" after sleeping through the night often just need this nudge.

  8. Reboot the stubborn device. Yes, really. Network stacks on phones and laptops get into confused states that only a restart clears. It is boring advice because it works.

Do not reach for the router's reset pinhole as an early step. A factory reset erases your network name, password, and every custom setting, and it will not fix a provider outage or a modem problem. It is a last resort with a specific procedure, not a bigger version of a reboot.

If it keeps coming back

Fixing "no internet" once is nice. If you are redoing this dance every week, something upstream is genuinely unhealthy and deserves a real diagnosis.

A router that repeatedly loses its connection, needs constant reboots, or drops devices at random has its own set of causes, from overheating to ancient firmware to a failing power adapter. We cover that pattern separately in our guide to a router that keeps dropping WiFi, and it is worth reading before you buy new hardware out of frustration.

Also be honest about which problem you actually have. "No internet" and "internet so slow it feels broken" get treated the same by annoyed humans, but they have different culprits and different fixes. If pages load eventually, or video buffers but works, start instead with our breakdown of whether you have slow WiFi or a slow internet connection, because that path leads through speed tests rather than restarts.

If the router itself has become unstable at a deep level (settings corrupted, admin page unreachable, behavior that survives reboots), a factory reset done properly can be the right call. Do it deliberately: our walkthrough on how to factory reset a router covers what you need to write down first so you can rebuild your network afterward instead of improvising it.

Two special cases worth knowing

Two scenarios produce this exact message so reliably that they deserve their own paragraphs, because neither is fixed by anything above.

The first is the captive portal. Hotel, airport, cafe, and guest networks show "connected, no internet" until you have clicked through their login or terms page. Modern phones usually pop that page up automatically, but laptops often do not. The trick: open a browser and try to load any plain, non-secure page (a good habit is typing an address you know redirects, or just your router brand's site), which forces the portal to appear. Until you complete that page, the network deliberately blocks you, and no amount of rebooting negotiates with it.

The second is the router that restarted into a half-connected state. After a power blip, a router can come back up faster than the modem and give up on getting an internet address, then sit there happily serving WiFi with nothing behind it. The clue is timing: everything broke right after a storm, an outage, or someone vacuuming near the power strip. The ordered restart in step 2 exists precisely for this case, and it is why the order matters rather than being superstition.

If you can be bothered with one more diagnostic, log in to the router's admin page (the address is on the label underneath) and look at its internet or WAN status page. "Connected" with a public address there means the problem is DNS or device-side; "disconnected" or endless "acquiring" means the modem or provider side is the fault. One glance replaces three guesses.

When it's one computer being difficult

If the whole house is fine and one computer refuses to load anything, the usual suspects line up like this: a VPN or proxy left enabled, a manually set DNS server that no longer exists, security software intercepting traffic, or a broken network stack.

Work through them in that order. Check the VPN icon first. Then check whether DNS was set manually (switch it back to automatic or to a public resolver). Then temporarily disable third-party firewall or antivirus tools and retest. As a final move, both Windows and macOS offer a network settings reset; search for "network reset" in system settings. It reinstalls the network configuration and cures a remarkable share of mystery cases, at the small cost of re-entering your WiFi passwords.

Frequently asked questions

Why does my WiFi say connected but no internet?

Your device has a working wireless link to the router, but the router has no working path to the internet, or DNS is failing. The WiFi link and the internet connection are two separate things, and the status message is telling you which one broke.

Why do I have full WiFi bars but nothing loads?

Signal bars only measure the strength of the radio link between your device and the router. They say nothing about whether the router can reach your provider. Full bars with no internet is the classic sign the failure is upstream of your device.

Should I restart the router or the modem first?

Unplug both, then power the modem first and let its lights settle before plugging in the router. The router asks the modem for its internet connection during startup, so the modem needs to be ready first. If they share one box, a single restart covers it.

Why does only one device say no internet?

That device's own configuration is broken: a stale address, a manually set DNS server, or a VPN or security app intercepting traffic. Forget the network and rejoin, disable VPN features, and restart the device. The rest of the network is innocent.

Will changing DNS to 8.8.8.8 or 1.1.1.1 fix it?

Only if DNS was the broken link, which is common but not universal. It is a two-minute test: set it, retest, and keep it if pages start loading. If nothing changes, set DNS back to automatic and keep working down the checklist.

Does "connected but no internet" mean my provider is down?

Sometimes. If every device is affected and the modem's internet light will not come on after a proper restart, an outage or line problem is likely. Confirm on your provider's status page over mobile data before spending more time on your own equipment.

The two-minute version for next time

Check a second device. If it works, fix the one broken device (forget network, kill the VPN, restart). If nothing works, restart modem then router in that order, and read the modem's lights. No internet light after that means it is your provider's problem, and your only remaining job is reporting it and making coffee. Everything else in this guide is just those three moves with the reasoning attached.