Why Your Wi-Fi Keeps Dropping: A Layer-by-Layer Diagnostic Checklist

Troubleshoot the client, radio, router, ISP, and DNS layers without random rebooting.

Treat “the Wi-Fi is down” as an observation, not a diagnosis
A disconnect can originate in the device, the wireless link, the router, the modem, the internet service, or even DNS. Rebooting everything sometimes hides the fault, but it also erases useful evidence. A faster approach is to isolate one layer at a time.

1. Define the blast radius
   When the problem occurs, check a second device immediately. If one laptop fails while a phone remains online, investigate the laptop. If every wireless device fails but an Ethernet-connected device works, focus on Wi-Fi. If both wired and wireless devices lose internet, move upstream to the router, modem, or ISP.

2. Separate association from internet access
   Look at the network status. Is the device disconnected from the SSID, connected with “no internet,” or connected normally while only one app fails? These states point in different directions. Failure to join suggests authentication, signal, or adapter trouble. “No internet” suggests routing, DHCP, WAN, or ISP trouble. One broken app may be an application or DNS issue.

3. Measure the radio conditions
   Record signal strength at the failure location. Test beside the router, then where the dropouts usually happen. Walls, metal cabinets, mirrors, neighboring access points, cordless devices, and poorly placed mesh nodes can reduce stability. On dual-band networks, 5 GHz is usually faster at short range while 2.4 GHz reaches farther but is often more congested.

4. Check addressing and reachability
   On a computer, confirm that the device has a plausible local IP address and default gateway. Test the gateway first, then a public IP address, then a domain name. If the gateway fails, the local network is the problem. If the public IP works but the domain fails, DNS is the likely layer. If the gateway works but the public IP fails, look at the WAN or ISP connection.

5. Correlate failures with time
   Write down the exact time of two or three drops. Check router uptime and system logs for WAN renewals, reboots, authentication failures, overheating, or repeated channel changes. Patterns matter: evening-only drops can point to congestion; failures under heavy upload can point to bufferbloat or a weak link; hourly drops can reveal lease or firmware behavior.

6. Change one variable
   Update the device’s Wi-Fi driver and the router firmware, but do not change five settings simultaneously. Test a different band, cable, device, or DNS resolver one at a time. Keep a small log of the change and result. Controlled tests turn frustration into evidence.

Know when to escalate
If the modem shows repeated loss of sync, signal levels are outside the provider’s accepted range, the router reboots under load, or the problem survives a known-good device and cable, collect model numbers, timestamps, and screenshots. An online tech-support specialist can use that evidence to narrow the fault before you replace hardware or wait on an ISP visit.

A reusable checklist
The order is simple: scope the failure, identify the connection state, test local reachability, test internet reachability, test DNS, correlate logs, and change one variable. That method works because it follows the network path instead of guessing.