Intermittent connectivity almost always traces to one of four layers: physical (cable, port, PoE), radio (Wi-Fi interference, weak signal), local network (DHCP, DNS, overloaded router), or ISP (line errors, CGNAT). Run a continuous ping to 1.1.1.1 and your gateway simultaneously, note when each fails, and fix the layer that drops first.
Symptoms
- Web pages load fine, then stall for 5-30 seconds before recovering without user action
- Video calls freeze or drop every few minutes while file downloads continue slowly
- Wi-Fi icon shows full signal but ping to gateway times out sporadically
- Speedtest results swing wildly between full-line speed and under 5 Mbps
- Devices reconnect to Wi-Fi repeatedly, visible as brief network icon flashes
Common Causes
Wi-Fi channel congestion and co-channel interference
Neighbouring access points on the same 2.4 GHz channel force airtime sharing and retransmissions. Symptoms cluster in evenings when household APs get busy.
Marginal or damaged Ethernet cabling
Bent RJ45 pins, kinked runs near power cables, or Cat5 pushed to gigabit lengths cause CRC errors and link renegotiation. Drops correlate with high throughput bursts.
Overheating or aging router hardware
Consumer routers running for years accumulate capacitor wear and thermal stress. NAT tables fill, radios lock up, and reboots temporarily mask the fault.
ISP line issues or CGNAT session resets
DOCSIS SNR margin loss, DSL retrains, or aggressive carrier-grade NAT timeouts kill long-lived TCP sessions. Modem event logs and traceroute hop 2-3 losses reveal it.
DNS resolver timeouts
When a configured DNS server responds slowly, browsing feels intermittent even though the link is healthy. Direct IP connections succeed while name lookups stall.
Step-by-Step Fix
- Run parallel pings to gateway, ISP, and public DNS
Open two terminals. Ping your gateway (usually 192.168.1.1) and 1.1.1.1 continuously. If gateway pings drop, the fault is inside your LAN or Wi-Fi. If only 1.1.1.1 drops, the issue is upstream at the ISP. - Check physical layer first: cables, ports, link lights
Reseat every Ethernet cable between modem, router, and switch. Swap suspect patch cables for known-good Cat6. Watch the port LEDs during a drop; a flickering link light points to a bad cable, port, or SFP long before software tools will. - Test wired vs wireless to isolate the radio
Connect a laptop by Ethernet and repeat the ping test. If wired is stable and Wi-Fi drops, the problem is radio-side. If both drop identically, skip ahead to router and WAN diagnostics. - Scan Wi-Fi and move to a clean channel
Use a scanner such as WiFi Analyzer on Android or the built-in wireless diagnostics on macOS. On 2.4 GHz stick to channels 1, 6, or 11. On 5 GHz pick a DFS-free channel with the fewest neighbours and set channel width to 40 MHz to reduce contention. - Update router firmware and factory-reset if needed
Log in to the router admin page and install the latest stable firmware from the manufacturer. If drops persist after updating, perform a factory reset and reconfigure from scratch rather than restoring a backup, which can carry the fault forward. - Review modem event logs for line errors
Access the modem's status page (often 192.168.100.1 for cable). Look for T3/T4 timeouts, uncorrectable codewords, or DSL retrains. Persistent line events are ISP territory; open a ticket with timestamps and log excerpts attached. - Switch DNS resolvers and clear the client cache
Set the router or client to 1.1.1.1 and 9.9.9.9. On Windows run ipconfig /flushdns; on macOS use sudo dscacheutil -flushcache. If the intermittent feel disappears, the original resolver was the culprit. - Reduce concurrent load and enable QoS
Cloud backups, 4K streams, and torrent clients saturate uplinks and starve interactive traffic. Pause them during testing. If drops vanish, enable QoS on the router and prioritise VoIP and video conferencing traffic.
Ping pattern to likely cause and next action
| Ping pattern | Likely cause | First action |
|---|---|---|
| Gateway drops, Wi-Fi only | Radio interference or weak signal | Change channel, move client closer to AP |
| Gateway drops, wired and Wi-Fi | Router hardware or firmware | Update firmware, then factory reset |
| Gateway stable, 1.1.1.1 drops | ISP or modem line issue | Check modem logs, open ISP ticket |
| High latency spikes under load | Bufferbloat or saturated uplink | Enable SQM/QoS on router |
| Random single-packet loss | Duplex mismatch or bad cable | Reseat cable, force auto-negotiation |
| Drops every ~24 hours | DHCP lease renewal glitch | Shorten lease, check for IP conflicts |
Prevention
- Reboot consumer routers on a monthly schedule to clear NAT tables and memory leaks
- Keep firmware current; subscribe to your vendor's security advisory list
- Label and date cable runs so degraded links are easy to spot and replace
- Log baseline ping and speedtest values monthly to catch slow degradation early
FAQ
How long should I run a ping test to catch intermittent drops?
Run ping continuously for at least 15 to 30 minutes, and ideally through a full work session. Short tests miss the pattern. Log the output to a file with a timestamp flag so you can correlate drops with events such as microwave use, VPN handshakes, or scheduled backups.
Does replacing the router always fix intermittent connectivity?
No. A new router only helps when the old one is genuinely faulty or thermally stressed. If the drops originate at the modem, ISP line, or in the wiring, a replacement router repeats the same behaviour within days. Diagnose the layer first, then decide on hardware.
Why does my connection feel unstable even though speedtests are fine?
Speedtests measure a short burst of throughput, not latency stability or packet loss. Bufferbloat, DNS delays, and brief microcuts pass a speedtest but ruin video calls and gaming. Use a latency-under-load test such as Waveform Bufferbloat to see the real picture.
Book a network diagnostic session with our IT support team to trace persistent drops end to end.