Use ping -t to Troubleshoot Intermittent Wi-Fi Drops

Why Intermittent Drops Are Hard to Diagnose

Wi-Fi that drops for a second or two every few minutes is one of the most annoying networking problems to troubleshoot, because by the time you notice the disconnect and open a browser to check, the connection has already recovered. You need a tool that watches the link continuously and timestamps every failure, so you have hard data to look at instead of a vague feeling that "the internet keeps cutting out." The built-in ping command with the -t flag does exactly this, and it's already on every Windows machine.

Running a Continuous Ping Test

Open a Command Prompt (Win + R, type cmd, Enter) and run a continuous ping against your router's local IP address first. This isolates whether the problem is your Wi-Fi link itself or something further upstream.

ping -t 192.168.1.1

Replace 192.168.1.1 with your actual router's IP, which you can find by running ipconfig and reading the Default Gateway line. The -t flag tells ping to run indefinitely instead of stopping after four packets, which is what lets you leave it running in the background while you go about your day and catch drops as they happen.

Let it run for at least 20-30 minutes, ideally while you're using the connection normally. Every reply line is timestamped implicitly by its position in the scroll, but to get actual clock timestamps (much more useful for correlating drops with other events), pipe the output through a small loop instead:

for /l %i in () do @echo %time% & ping -n 1 192.168.1.1 | find "Reply" || echo DROPPED at %time%

This prints a timestamp on every packet and flags failures explicitly with "DROPPED" so you can scroll back and see exactly when and how often the link failed.

Isolating Router vs. ISP

Once you have a baseline against your router, run the same test against an external target to see if the problem extends past your local network:

ping -t 8.8.8.8

8.8.8.8 is Google's public DNS resolver and a reliable target because it responds to ICMP consistently and won't itself be flaky. Run this in a second Command Prompt window side-by-side with the router ping so you're watching both at once.

• Router ping drops, external ping also drops at the same moments: the problem is almost certainly your local Wi-Fi — router placement, interference, or a failing radio in your router/adapter.
• Router ping stays solid, external ping drops: your Wi-Fi link is fine and the issue is upstream — your ISP, your modem, or the WAN link between your router and the internet.
• Both drop, but external drops are more frequent or longer: you likely have two separate problems, or your ISP connection is the dominant contributor.

Reading the Results

When you stop the test with Ctrl + C, Windows prints summary statistics: packets sent, received, lost, and the percentage lost, plus round-trip time min/max/average. Any sustained packet loss above 1-2% on your local router ping indicates a real problem worth chasing further. Occasional single-packet timeouts are usually harmless (a missed beacon frame or brief retry), but repeated "Request timed out" runs lasting several seconds line up with actual disconnects you'd notice as lag or dropped calls.

Digging Deeper Once You've Localized the Problem

If the drops trace to your Wi-Fi link specifically, check the Windows Event Viewer (eventvwr.msc) under Applications and Services Logs → Microsoft → Windows → WLAN-AutoConfig → Operational for disconnect events around the same timestamps your ping test flagged — these often include a disconnect reason code that points to authentication failures, roaming between access points, or the driver dropping the association. If the drops trace upstream to your ISP, run pathping 8.8.8.8 to see which specific hop between you and the internet is introducing the loss, which is useful evidence to hand to your ISP's support line instead of just saying "my internet keeps cutting out."

Wrap-Up

A continuous ping test costs nothing and takes thirty seconds to start, but it turns a vague, hard-to-reproduce complaint into a timestamped log you can actually act on. Run it against your router and an external host side by side, let it soak for a while, and you'll know within the hour whether to reset your router, move it, or call your ISP.