Why Is My WiFi Connected But No Internet? What's Actually Going On

You've seen it before: your device shows a strong WiFi signal, the network name is right, the password worked — but nothing loads. Websites time out, apps spin endlessly, and yet your device insists it's connected. This maddening situation is more common than most people realize, and it almost always has a logical explanation.

What "Connected But No Internet" Actually Means

When your device connects to WiFi, it's connecting to your local network — essentially your router. That's step one. Step two is your router connecting outward to the internet through your ISP (Internet Service Provider). These are two separate connections, and either one can fail independently.

When you see "connected, no internet," your device successfully completed step one but step two has broken down somewhere. The WiFi signal between your device and router is fine. The problem lives further down the chain.

Common Causes — and Where the Break Is Happening

1. The Problem Is With Your ISP

Your router may be working perfectly, but if your ISP is experiencing an outage or service disruption, no device in your home will reach the internet. This is one of the most frequent causes — and the one users have least control over.

How to check: Log into your router's admin page (typically accessed via 192.168.1.1 or 192.168.0.1 in a browser). If it shows a WAN or internet connection error, the issue is upstream from your router.

2. Your Router Needs a Restart

Routers run continuously and can accumulate memory issues, stalled processes, or temporary configuration errors over time. A simple power cycle — unplugging the router for 30 seconds and plugging it back in — clears these states and re-establishes the connection with your ISP.

The same applies to your modem if it's a separate device from your router. Restart modem first, wait 60 seconds, then restart the router.

3. DNS Resolution Failure

Your device might have a valid internet connection but fail to translate domain names (like google.com) into IP addresses. This is a DNS (Domain Name System) failure. The connection technically exists; the translation layer is broken.

Symptom: websites by name fail, but apps or services that use direct IP addresses might still work.

Common fix: Manually switch your DNS server to a public option like 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) in your device's network settings.

4. IP Address Conflict or DHCP Failure

When you connect to WiFi, your router assigns your device a local IP address via DHCP (Dynamic Host Configuration Protocol). If this process fails — or if two devices end up with the same IP address — connectivity breaks down even though the WiFi signal is fine.

Signs of this: your device shows an IP address starting with 169.254.x.x, which is a self-assigned fallback address indicating DHCP didn't complete successfully.

Fix: Forgetting the network and reconnecting, or releasing and renewing your IP address through your OS network settings, usually resolves this.

5. Device-Specific Software or Driver Issues

Sometimes the problem is isolated to one device. If other devices on the same network work fine, the issue is almost certainly with that specific device — its network adapter drivers, OS network stack, or a software conflict.

This is more common after OS updates, especially on Windows, where network adapter drivers occasionally need updating or a network settings reset.

Windows users: Running the built-in Network Troubleshooter or using the netsh winsock reset command in an elevated Command Prompt resolves many of these cases.

6. Router Firmware or Configuration Issues

Routers run their own operating system called firmware. Outdated or corrupted firmware can cause erratic behavior, including losing the ability to route internet traffic while still broadcasting a local WiFi signal.

Checking for firmware updates through your router's admin panel is good periodic maintenance regardless of whether you're experiencing issues.

The Variables That Determine What's Actually Wrong 🔍

No single fix works for everyone because the cause depends heavily on:

How Different Setups Experience This Differently

A household with a combined modem/router unit from their ISP has fewer components to troubleshoot but less control over each. A user with a separate modem and router has more variables to isolate — but more ability to pinpoint exactly where the break is happening.

Someone using a Windows laptop will have different diagnostic tools and common failure points than someone on macOS, Android, or iOS. Mobile devices, for example, often resolve these issues automatically by switching to mobile data — masking the problem rather than fixing it.

Users on older routers (5+ years) may find that what looks like a connectivity issue is actually hardware degradation — particularly in the WAN port or the router's ability to maintain a stable DHCP lease.

And in apartment buildings or dense WiFi environments, IP conflicts are meaningfully more common than in single-family homes, simply because more devices and networks are competing in close proximity.

Working Through It Systematically 🛠️

The most efficient approach is to narrow down where the break is:

1. Check if all devices are affected or just one
2. Restart modem (if separate), then router
3. Check your ISP's outage status page or contact support
4. If one device: forget and reconnect to the network, update drivers, or reset network settings
5. Check for an unusual IP address (the 169.254.x.x indicator)
6. Try changing DNS settings on the affected device

Each step eliminates a layer — ISP, router, DHCP, or device — so you're not guessing.

The fix that takes 30 seconds for one person might not apply at all to another, depending on which layer has actually broken down in their specific setup.