Local
Check whether the device has an IP address and can reach the router.
When the device says Wi-Fi is connected but nothing loads, isolate modem signal, router handoff, IP address, DNS, captive portals, and device settings.
This is the classic false comfort problem: the device sees the router, but the router may not have a clean route out. That means modem status, DNS, IP address, and captive portals matter as much as the password.
How to approach it: Treat the path in order: device to router, router to modem, modem to provider, provider to the site or app.
The Wi-Fi icon only proves the local connection. It does not prove the internet path is alive.
Check whether the device has an IP address and can reach the router.
Confirm other devices and wired connections before changing settings.
Look for modem sync, app outages, and account service issues.
Test DNS, captive portals, VPNs, and security filters.
Start with the closest symptom, then move to router, device, DNS, VPN, or provider steps when the pattern points there.
Use this when the no internet pattern is the one you can actually observe.
Use this when the no internet pattern is the one you can actually observe.
Use this when the no internet pattern is the one you can actually observe.
Use this when the no internet pattern is the one you can actually observe.
Use this when the no internet pattern is the one you can actually observe.
Use this when the no internet pattern is the one you can actually observe.
Check whether the device has an IP address and can reach the router.
Confirm other devices and wired connections before changing settings.
Look for modem sync, app outages, and account service issues.
Test DNS, captive portals, VPNs, and security filters.
Short answers for the moment before a reset, equipment swap, or provider call.