Observation
A short ping log to the gateway and a public IP.
Random Disconnects and Packet Loss
Use this flow when the network drops at random or shows packet loss and you need to separate WAN instability from Wi-Fi problems and cable or power issues. Start with timing and path evidence before reboot loops erase the pattern.
Safety first: document the pattern before repeated reboots erase it, and do not replace hardware until you know whether wired and wireless fail together.
What this flow is for
This flow is for intermittent networking faults that come and go, so you can isolate WAN, Wi-Fi, and physical-layer issues before you start swapping gear or flattening the setup.
First safe checks
- Run a continuous ping to the gateway and a public IP.
- Check whether wired and wireless devices fail at the same time.
- Inspect power, heat, and cable condition on the network path.
- Note whether the issue follows one device, one port, one AP, or the whole network.
- Use timing and path evidence before rebooting or replacing hardware.
Evidence requests
Ask for the smallest missing proof
Photo or screen
A note describing whether wired and wireless clients drop together or separately.
Change log
A quick note or photo on cable, port, LED, heat, or power conditions.
Likely causes
Most likely problem buckets
WAN instability
If gateway pings stay clean while the public path drops, the WAN side becomes more likely.
Wi-Fi issue
If only wireless devices fail, radio conditions and association behavior matter more than the ISP path.
Cable or port fault
Intermittent link problems often show up on one cable, switch port, or powered device.
Power or heat issue
Thermal and power instability can look like random packet loss when the hardware path is struggling.
Next safe steps
Take one step at a time
ACT-NET-010
Run continuous ping tests to the gateway and a public IP before rebooting.
ACT-NET-001
Record modem, router, or switch LED state while the problem is active.
ACT-NET-011
Inspect cables, heat, and power while comparing wired and wireless failure timing.
ACT-NET-013
Isolate one wired client, one AP, or one port to narrow the failing segment.
Best follow-up ask
Do wired and wireless devices drop at the same time, and what does a continuous ping to the gateway versus a public IP show?
When to stop and hand off
The issue requires longer log capture, cable replacement, firmware rollback, or provider engagement to keep moving.
Support links
Follow the pattern you can prove
If the problem settles into full outages, room-based weak signal, or single-device reachability, move into the closest guide instead of treating every drop as packet loss.
Open Wi-Fi problems Open outage-recovery path