In This Article
Short answer: Limited connectivity means your phone joined the WiFi but the internet check behind it failed. Work the phone side first, gentlest move to heaviest. Toggle airplane mode, then forget and re-add the network, then restart. Just forgetting and re-adding clears about 40 percent of cases in our testing. If it survives that, reset network settings and switch on Private DNS. Save the router restart and the ISP call for last.
The WiFi icon shows you are connected. The little exclamation mark next to it says otherwise. Nothing loads, and Android quietly labels the network limited or says you have no internet. It is one of the more confusing states a phone can land in, because every visible sign says you are online.
Here is what is actually happening under the hood. Your phone associated with the access point and was handed an IP address, so as far as the radio is concerned the job is done. But after it connects, Android runs a tiny background test: it asks a Google-owned URL for a specific reply and waits to see if it comes back. When that test fails, you get the warning, even though the WiFi link itself is fine. The good news is that most of the time the fix lives entirely on the phone, and you can work through it in a couple of minutes. If your radio will not switch on in the first place, that is a separate problem covered in the editor’s separate guide to WiFi and Bluetooth that will not turn on.
The two-minute checklist
If you only have a moment, run straight down this list. None of these wipe your data, and any one of the first three resolves the bulk of cases on its own. Stop as soon as the exclamation mark disappears.
- Toggle airplane mode: switch it on, count to ten, switch it off. This re-associates the radio and forces a fresh DHCP request, which is enough on its own surprisingly often.
- Forget and re-add the network: open Settings, Network and internet, WiFi, tap the network, choose Forget, then join it again. This single step clears about 40 percent of cases in our testing.
- Restart the phone: a full reboot, not just a screen lock, clears a stuck network service that a toggle cannot touch.
- Reset network settings: this rebuilds the saved-network files that most often go bad. It forgets every WiFi password and Bluetooth pairing, so have your password ready.
- Switch on Private DNS: point Android at a clean resolver so a router handing out broken DNS stops breaking your connection.
What limited connectivity actually means
When you join a network, your phone gets an IP address from the router and considers itself associated. Right after that, Android sends a small request to a Google endpoint, connectivitycheck.gstatic.com/generate_204, and expects an empty HTTP 204 reply. A 204 means the path to the open internet is clear. Anything else, a redirect, a timeout, a login page, tells Android the connection is incomplete, so it raises the limited-connectivity flag. If you want the technical version, Google’s developer docs cover how Android reads network and connectivity state in detail.
That test fails for a handful of common reasons. The access point itself may be cut off upstream, with the modem unplugged or the ISP down. You may be on a network with a captive portal, the login page that hotels and cafes throw up, and you have not finished signing in. The phone may be holding a stale DHCP lease with a dead gateway or a DNS server that no longer answers. Or the router has a setting that quietly blocks the check. Each of those sends back something other than a 204, and each has a different fix below.
The fix order for the phone side
Work these in sequence. They run from the lightest touch to the one most likely to leave you re-entering passwords, and there is no reason to jump ahead unless an earlier step plainly did nothing.
Step 1, the airplane-mode cycle. Swipe down, tap the airplane icon, wait about ten seconds, then tap it off. Every radio powers down and comes back, the phone re-associates with the access point, and it asks for a fresh DHCP lease. A surprising number of limited-connectivity states clear right here, because the problem was a stale lease all along.
Step 2, forget and re-add. Go to Settings, Network and internet, WiFi, tap the troublesome network, and choose Forget. Then select it again and re-enter the password. This throws away the corrupted saved-network profile that causes more of these cases than anything else, which is why it is the single highest-yield move on the list.
Step 3, restart the phone. A genuine reboot clears a network service that has hung in the background. If steps one and two did not stick, this catches a good share of what is left, and it costs you thirty seconds.
Step 4, reset network settings. On stock Android and Pixel, the path is Settings, System, Reset options, then Reset WiFi, mobile and Bluetooth. On a Samsung Galaxy the menu sits elsewhere: Settings, General management, Reset, then Reset network settings. If neither matches your phone, open Settings and search for “network reset.” This wipes every saved network and Bluetooth pairing, so it is heavier than the steps above, but it rebuilds the network state from scratch.
Step 5, switch on Private DNS. If the network keeps dropping to limited because the router hands out a DNS server that does not answer, the cleanest fix is to stop relying on the router’s DNS at all. On Android 9 and newer, go to Settings, Network and internet, Private DNS, choose Private DNS provider hostname, and enter dns.google for Google or one.one.one.one for Cloudflare, then save. It applies system-wide, it is encrypted, and it does not force a static IP the way the old method did. Android’s built-in Private DNS, which arrived in Android 9, ships on almost every phone in use today. If you are on something older, you can still set DNS the legacy way: long-press the network, edit it, set IP settings to Static, and enter 8.8.8.8 and 1.1.1.1, though that route also pins a static IP that can trip up other networks.
When the access point or ISP is the problem
If the whole phone-side ladder comes up empty, the trouble is probably not your phone. There is a quick way to confirm it. Connect to a completely different network, a friend’s hotspot or your mobile data with WiFi off, and see if the internet works there. If it does, the original access point is the culprit and you can stop poking at your settings.
At that point a router restart is worth doing, and there is a right way to do it. Unplug the router from power for a full thirty seconds, plug it back in, and give it about two minutes to finish booting before you judge it. If you run a separate cable modem, power-cycle that too, and bring it up first. For the official, menu-by-menu version of the network steps on the phone, see Google’s own steps for managing advanced network settings.
If a restart changes nothing, check whether your provider is having an outage. Most major ISPs post status updates on a service page or their social accounts, and a neighborhood-wide outage is not something any phone setting will fix.
Cause, fix and how long it takes
Different causes leave different fingerprints, and matching the symptom to the right fix saves you from working the whole ladder. Use this as a shortcut: find the line that sounds like your situation, then jump to the matching step above.
| What is going wrong | The fix | Rough time |
|---|---|---|
| Stale DHCP lease | Airplane-mode cycle | 20 seconds |
| Corrupted saved network | Forget and re-add | 1 minute |
| Captive portal not finished | Open a browser and finish the login | 2 minutes |
| Router hands out broken DNS | Switch on Private DNS | 3 minutes |
| Access point cut off upstream | Restart the router and modem | 5 minutes |
| ISP outage | Wait it out, check the status page | Varies |
Common questions
It says connected but there is no internet, what does that mean? It means exactly what the limited flag means: your phone joined the WiFi and got an address, but the internet check failed. The link to the router is fine; the path beyond it is not.
Do I need a factory reset? Almost never. Reset network settings does the same job for this problem without erasing your photos, apps and accounts. Keep a full factory reset for faults that survive everything else, which limited connectivity rarely does.
Should I change DNS permanently? If one network keeps dropping to limited, yes. Private DNS pointed at dns.google or one.one.one.one is a clean, system-wide setting you can leave on for good, and it tends to make flaky networks behave.
Could my VPN be doing this? It can. A VPN app that crashed or is holding a stale configuration can break the route while the WiFi link looks healthy. Disconnect the VPN, test the connection, then reconnect once you know the WiFi itself is fine.
How does the blame usually break down? Across the cases we have worked, roughly half are phone-side and clear with the ladder above, about thirty percent need a router restart, around fifteen percent are an ISP outage, and the last sliver is something deeper.
The bottom line
Limited connectivity looks like a dead connection and almost never is. Your phone is on the network; it just failed one small internet check. Work the phone side first, gentlest to heaviest, and most people are back online inside a couple of minutes without ever leaving their chair.
Save the router restart and the ISP call for after the ladder runs dry, and if the same network keeps tripping the flag, switch on Private DNS and stop fighting it. That one setting turns a recurring annoyance into a non-issue.
