“Connected” only means your Android phone has joined the Wi-Fi network; it does not prove that the router can reach the internet. The failure can sit on the phone, the router, DNS, a captive portal, a proxy/VPN, an ISP connection or an access-control rule.
Use the checks below in order. The goal is to identify the failing layer before deleting saved networks or resetting anything.
Quick diagnosis: where does the failure start?
- Only this Android phone fails: focus on its saved Wi-Fi profile, Private DNS, VPN, proxy and network identity.
- Every device on the same Wi-Fi fails: focus on the router/modem, WAN link and ISP.
- Only one app or website fails: test other services before changing network settings.
- Mobile data works immediately: the fault is probably in the Wi-Fi path. If mobile data also fails, use the mobile data troubleshooting guide.
1. Toggle Wi-Fi, then restart the phone
Start with reversible steps. Turn Wi-Fi off and back on. If internet access does not return, restart the phone and reconnect. This can clear temporary radio, DHCP or routing state without deleting configuration.
2. Test the same Wi-Fi with another device
Connect another phone or laptop to the same network and open more than one site. If that device is also offline, changing Android settings is unlikely to fix the root cause. Check the router’s WAN/internet status and the ISP instead.
3. Forget the network and join it again
If only the Android phone fails, forget that Wi-Fi network and reconnect with the correct password. This rebuilds one saved profile without wiping every Wi-Fi network and Bluetooth pairing on the device.
4. Check for a captive-portal sign-in page
Hotels, airports, cafés, schools and guest networks may let the phone associate with Wi-Fi before granting internet access. Open a browser and try a normal webpage. Complete any sign-in or terms page that appears before troubleshooting DNS.
5. Restart the router or modem if multiple devices are affected
A router can continue broadcasting Wi-Fi while its upstream internet connection is down. If several devices fail together, restart the network equipment according to its manufacturer’s instructions and wait for the WAN/internet connection to return.
6. Temporarily return Private DNS to Automatic
A custom Private DNS hostname can make a healthy Wi-Fi link look offline when that resolver cannot be reached from the current network. Temporarily set Private DNS to Automatic and retest. Google recommends leaving Private DNS enabled under normal conditions; this is a diagnostic step, not a recommendation to disable encrypted DNS permanently.
If this restores access, use our Private DNS server cannot be accessed guide. If Chrome specifically reports NXDOMAIN, follow the DNS_PROBE_FINISHED_NXDOMAIN checklist.
7. Disable VPN, firewall or DNS-filtering apps for one test
A VPN-based firewall, ad blocker or DNS changer can become the failing hop while Wi-Fi itself remains connected. Disconnect it briefly and test a trusted site. If access returns, repair that configuration rather than leaving the protection disabled. Our Android DNS changer guide explains which DNS layer different methods change.
8. Check the Wi-Fi proxy setting
Android supports a proxy per saved Wi-Fi network. Unless your school, workplace or network administrator requires one, an old manual proxy can block browsing. Open the connected network’s advanced settings and verify that its proxy configuration is appropriate.
9. Check randomized MAC address if the router uses device allowlists or parental controls
This is easy to miss on managed home, school and workplace networks. Google documents that Android 10 and newer devices expose a randomized MAC address for a Wi-Fi network in addition to the phone’s hardware Wi-Fi MAC address. Google also advises including both addresses when configuring parental controls.
If your router grants internet access by MAC address, check the connected network’s details and compare the randomized MAC with the address allowed by the router. Do not disable MAC randomization as a generic internet fix: it is a privacy feature. Change identity behavior only when you control the network or its administrator specifically requires it.
10. Test another trusted Wi-Fi network
If a second network works, the original router, ISP, DNS path or access policy is the stronger suspect. If several unrelated Wi-Fi networks fail on the same phone while mobile data works, a phone-side configuration becomes more likely.
11. Reset network settings only after you isolate the problem to the phone
Manufacturers use names such as Reset Wi-Fi, mobile & Bluetooth or Reset network settings. The reset can remove saved Wi-Fi networks and Bluetooth pairings, so record anything important first. A factory reset is not the next automatic step for a Wi-Fi-only failure.
If browsing works but Wi-Fi Calling does not
If websites and apps work normally but calls fail, the Wi-Fi internet connection is probably not the primary problem. Wi-Fi Calling also depends on carrier support, SIM/eSIM provisioning and calling preferences. Use the separate Wi-Fi Calling troubleshooting guide.
When the problem is probably not Android
If every device is offline, the router has no WAN connection, or the ISP reports an outage, changing Android DNS or app settings will not restore the upstream link. Likewise, if only one service fails while other sites work, investigate that service first.
For a broader decision tree covering Wi-Fi, mobile data, DNS, Bluetooth and hotspot failures, use our Android Internet & Network Connectivity Troubleshooting Hub.
Official Android sources
- Google Android Help: Fix internet connection problems on Android devices
- Google Android Help: Manage advanced network settings on Android
Last reviewed: September 22, 2026. Menu names and available network controls vary by Android version, manufacturer and network administrator.
1 comment
Corrections, useful experiences and focused questions are welcome. Keep discussion respectful and on topic.