Explore the guide library · Windows diagnostic tools
Capture the time, affected devices and failing stage before a restart erases useful clues.
Intermittent outages are difficult to diagnose when the only description is “the internet stopped again.” A compact incident log can show whether the problem follows one device, one application or the whole connection.
Use a repeatable record
| Field | Useful entry |
|---|---|
| Time | Start, end and time zone |
| Scope | Devices and applications affected |
| Connection | Wired, wireless or cellular fallback |
| Visible state | Exact error and relevant indicator |
| Recovery | Returned by itself or after a named action |
Compare without changing everything
During the next incident, check one other device if it is convenient. Try one ordinary public destination and the affected application. Record whether Wi-Fi disconnected entirely or remained associated without usable internet access.
Save targeted diagnostics
Windows’ wireless report can help associate connection events with the incident time. A relevant connection test can add another observation. Collect only what helps answer the current question; a large unreviewed diagnostic archive is harder to interpret and may expose private information.
Record changes honestly
If you restart the router, reconnect the adapter or pause a download, note the time and action. Recovery after a restart is an observation, not proof that the router hardware caused the outage. Several services may recover during the same interval.
Look for a pattern
- Only after the laptop wakes.
- Only while a large upload runs.
- All devices at the same evening time.
- One application while normal browsing continues.
Send the relevant records through the provider’s or administrator’s private support channel. Exclude passwords, complete browsing history and unrelated account details.
After a repair, keep recording for the period in which failures previously occurred. The absence of the recurring symptom under comparable conditions is stronger evidence than one successful speed test immediately after a restart. A concise log also prevents the next support conversation from starting from zero.
Sources and editorial notes
Sources checked 8–9 October 2026. Independent guidance and original illustrations; product comparisons use published specifications rather than hands-on benchmarks. Check the exact model, revision and regional documentation before changing settings.
- Microsoft: analyzing the wireless network report
- Microsoft: Test-NetConnection diagnostics
- Microsoft: Windows connectivity-status detection