Troubleshooting

Why Does My Wi-Fi Keep Disconnecting?

Distinguish a lost Wi-Fi connection from missing internet or one failing app. Compare devices, Ethernet and event records before changing settings.

A page failing to load does not prove that Wi-Fi disconnected. During the fault, check whether the device remains associated with its usual network, whether multiple internet services fail, and whether another device is affected at the same time. Working Ethernet is useful evidence, not proof that every part of the internet connection is always healthy. One affected device does not automatically establish a faulty driver.

Identify which connection fails

The Wi-Fi network disappears or the device disconnects: record the network, access point, band and time. Association, authentication and coverage are hypotheses to check, not conclusions from a single icon.
Wi-Fi remains connected but internet access fails: compare local access with external services. IP configuration, DNS, the access point uplink or the path upstream may need investigation. Treat failed website-name resolution separately from losing the radio connection.
Only one app or website fails: compare another service and the affected service’s official status. An application error does not establish a Wi-Fi disconnection.
On a phone, verify that the comparison actually uses Wi-Fi. Automatic cellular fallback can conceal the fault. Choose suitable trials without interrupting necessary communications.

Preserve evidence before restarting

Record onset and duration, device and operating system, adapter and driver version, network name, band or access point when visible, location, movement, sleep/resume and your own traffic. Save router events and uptime using its documented procedure before restarting. Correlate timestamps; an old or warm router is not a diagnosis by itself. Do not delete profiles, drivers or network settings before gathering this information.

Compare one condition at a time

The same period and services on another Wi-Fi device help distinguish a client case from a shared problem. Check the access point used; two clients on different mesh nodes are not an identical comparison.
The same client and network near the access point versus the usual location help investigate coverage. Improvement does not prove a particular interference source or hardware defect.
Compare Ethernet and Wi-Fi during the same incident. If Ethernet fails too, also examine the local network, cable/switch, router, upstream connection and service. Do not immediately attribute it to the modem or provider.
Compare the same client stationary versus moving between mesh nodes, or before and after resume, and correlate logs. A node’s uplink may fail while the client still shows connected Wi-Fi. A fixed time alone does not identify the cause.

On Windows, netsh wlan show wlanreport in an authorized administrator command prompt creates an HTML report of recent sessions, disconnect reasons and adapter details; open the location it displays. On Mac, hold Option, click the Wi-Fi menu and choose Open Wireless Diagnostics, then follow the assistant. This analysis does not change network settings. Reports may contain private names and identifiers. Any ping comparison must use the connection’s actual gateway; a missing ICMP reply alone proves neither a router fault nor a DNS failure. VMAXCHECK’s M-Lab NDT measures to a particular server, not a previous disconnection. Run it between comparisons because it generates traffic.

Choose an evidence-based change you can undo

Compare system, driver and firmware versions with official guidance for the actual model. Save settings and follow the manufacturer’s update procedure, allowing for disruption. A newer version is not a guaranteed fix.
For coverage or mesh evidence, check placement and node uplinks using the manufacturer’s guidance. Do not split bands as a blanket repair: Apple recommends one name across bands and consistent settings. A supported band trial needs a purpose and a way to restore the previous configuration.
For a repeatable link with sleep or power, use the device documentation. Power options vary and affect battery life; do not disable all of them or force missing options through the registry. Preserve protections and managed-network requirements.
After saving events, a documented restart can be a trial. It interrupts other users and calls; one good result afterward does not establish the original cause. Factory resets, network resets, DNS changes and disabled security are not universal repairs.

Change one thing and repeat with comparable location, client, services and observation duration. Give device or network support timestamps, versions, Wi-Fi state, access point and before/after comparisons. If several services also fail over Ethernet, include local and upstream observations for the provider. Remove credentials, tokens and private identifiers before sharing logs. Evidence narrows an investigation without guaranteeing a diagnosis or permanent stability.