If Wi-Fi keeps disconnecting, first determine whether the device leaves the wireless network or stays connected while internet access fails. Then check whether the same event affects one device, one location or the whole home. Those observations are more useful than changing a router setting because a drop happens every hour.
A browser speed test can describe a tested connection while it is available. It cannot, by itself, identify a wireless disassociation, read a driver’s disconnect reason or prove that an ISP caused a drop. Use this guide to collect that missing context before applying a fix.
If a Ring doorbell went offline immediately after a router, network-name or password change, follow our Ring Wi-Fi reconnection instructions. Moving a retained device to new credentials is a different task from diagnosing random disconnections on an unchanged network.
1. Record what disconnects
When the problem happens, note the Wi-Fi icon or network status before reconnecting. Is the network still selected? Does the device say it has no internet? Does an Ethernet-connected device continue working? Does only one app fail while other websites load?
| What happens | What to compare next |
|---|---|
| One device leaves Wi-Fi while other devices stay connected | That device’s adapter, saved network and connection records |
| Several Wi-Fi devices drop, but Ethernet remains healthy | The access point, wireless settings and radio environment |
| Wi-Fi stays connected, but wired and wireless internet fail | Shared router, modem/ONT and provider service status |
| The issue occurs while moving between rooms | Coverage and transitions between access points |
| Only one app fails | The application, account or destination service |
A regular interval is worth recording, but is not proof of a DHCP lease problem. A night-time pattern does not prove overheating, interference or congestion. Keep the timing and compare another device before selecting a theory.
2. Compare the same device near the router
Use the affected laptop or phone in its normal location, then near the router. Keep the same activity running and record whether a real disconnect occurs. If possible, compare that laptop on Ethernet through the router. This changes the local access path while retaining the device and much of the upstream connection.
For location differences, the Wi-Fi room comparison can organize repeatable browser measurements. It does not measure signal strength or scan channels. A browser result captured after reconnection may look normal even though the earlier disconnect was real.
If the phone switches to mobile data when Wi-Fi fails, it can hide the outage. Record which connection the phone actually used for a comparison and avoid drawing a conclusion from a second device that silently changed networks. On a metered plan, keep test traffic limited.
3. Look for a recorded disconnect reason
Windows: generate the wireless network report
Microsoft documents a built-in report for recent wireless sessions. On your own Windows PC, open Command Prompt as administrator and run this reporting command:
netsh wlan show wlanreportOpen the HTML file at the path Windows displays. Compare the incident time with the session timeline and disconnect reasons. The Microsoft wireless-report guide explains the sections and its recent-event coverage. The report can include device, user and network identifiers; share relevant details privately with support rather than posting the complete archive publicly.
A recorded reason is a starting point, not always the final cause. Correlate it with another device and the application symptom. Do not copy network-reset commands from an unrelated guide just because the report contains a warning.
Mac: use Wireless Diagnostics
On a Mac that is joined to the affected network, hold Option while selecting the Wi-Fi menu, then choose Open Wireless Diagnostics and follow the prompts. Apple’s Wireless Diagnostics guide explains the analysis and notes that it does not change network settings. Record relevant findings alongside the incident time; review a diagnostic archive for private information before sharing it.
4. Apply a fix that matches the evidence
If only one device disconnects
Check for supported operating-system and adapter updates from the device manufacturer. Note whether the problem began immediately after an update. Follow the manufacturer’s troubleshooting process rather than installing a driver from an unfamiliar download site.
If the saved connection seems to be the issue, forgetting and rejoining the network can be a controlled comparison, provided you know the credentials and have permission to change that device’s connection. Microsoft includes device-side options in its Windows Wi-Fi troubleshooting guide. On a work or school device, ask IT before altering managed profiles.
A battery-only pattern makes power behavior worth investigating, but does not justify claiming that all Windows adapters use the same default. Compare plugged-in and battery operation, then consult the device’s current power/adapter guidance. Some systems do not expose the older Power Management tab. Change one supported option at a time and record how to restore it.
If the problem follows a room or movement
Improve access-point placement or the connection between mesh nodes before adding equipment. Compare a stationary test with a moving one. A device that works beside one access point but drops between two needs a coverage or transition investigation; enabling a feature with “roaming” in its name is not a universal remedy.
For a broader coverage problem, use the Wi-Fi dead-zone guide. Keep any radio or channel decisions tied to measurements and your router’s documentation. A wider channel or a newer Wi-Fi standard is not automatically more reliable in every environment.
If several wireless devices drop together
Check router/access-point firmware and documented configuration. Back up settings before a deliberate change, and preserve modern authentication and encryption. Apple’s recommended router settings explain why consistent, secure configuration matters. Turning off Wi-Fi security is not an acceptable troubleshooting shortcut.
Also check ordinary physical conditions: a loose power connector, blocked ventilation or an unstable access-point backhaul can deserve attention. A warm device or its age alone does not establish a hardware fault. Arrange one restart according to the manufacturer’s process when a temporary interruption is acceptable, then observe rather than repeatedly rebooting.
If wired internet fails at the same time
Record the router and modem/ONT indicators and check the provider’s incident page using an alternate connection if available. If service remains down, contact the provider with the times and devices affected. Use the slow-internet troubleshooting workflow once connectivity returns if performance is also reduced.
5. Keep a short incident log
| Time | Device and room | Wi-Fi disconnected or internet unavailable? | Other device / Ethernet result | Recorded event or one change |
|---|---|---|---|---|
| — | — | — | — | — |
| — | — | — | — | — |
For timing variation without an actual Wi-Fi disconnect, the HTTP connection-stability tool answers a narrower question. For a sudden site-wide slowdown, follow the slow-internet diagnosis instead of assuming every pause is a wireless drop.
Reviewed 27 October 2026. The examples are diagnostic patterns and blank logs. No failure rates, hardware lifespan rule or measured success percentage is claimed.