What you will achieve

Detect packet loss and latency problems using built-in ping and tracert on Windows, and interpret results without guesswork.

1) Baseline ping to your router

Open Command Prompt or PowerShell.
Run ipconfig and note the Default Gateway (e.g. 192.168.1.1).
Ping it continuously: ping 192.168.1.1 -t. Press Ctrl + C to stop.
Loss to the gateway points to local Wi‑Fi, cable, or switch issues — not your ISP.

2) Ping an external host with count

ping 1.1.1.1 -n 100
ping google.com -n 100

Check the summary: Lost = 0 (0% loss) is healthy. Sporadic loss above 1–2% causes VoIP and gaming issues.
Compare IP (1.1.1.1) vs name (google.com) — if IP works but name fails, suspect DNS not packet loss.

3) Trace the route with tracert

tracert 1.1.1.1

Each hop shows latency to routers along the path. High latency or timeouts on hop 2–3 often mean ISP or VPN issues.
Run during problem hours and again when the network feels fine to compare.

4) Extended diagnostics

pathping 1.1.1.1

pathping combines traceroute with per-hop loss statistics — slower but useful for intermittent loss.

5) Continuous ping log to file

ping 1.1.1.1 -t > C:\Temp\ping-log.txt

Correlate timestamps with when VoIP or gaming stuttered.

6) MTU issues

ping google.com -f -l 1472

Reduce -l size until packets pass without fragmentation needed — VPN tunnels often need lower MTU.

7) Pathping interpretation

Loss shown at final hop only often means destination ICMP rate limiting, not real loss.
Loss at intermediate hop may be normal if that router deprioritises ICMP — compare multiple targets.

8) Test with PowerShell Test-Connection

Test-Connection 1.1.1.1 -Count 50 -Quiet
1..50 | ForEach-Object { (Test-Connection 8.8.8.8 -Count 1).ResponseTime }

Build simple latency arrays for logging during intermittent faults.

Verification checklist

Save ping and pathping outputs to dated files during fault and during clean periods — comparison beats one-off tests when chasing intermittent ISP issues.

Reboot once after changes that affect services, drivers, or firmware.
Confirm the original problem is resolved under normal daily use, not only immediately after the fix.
Note date, Windows version (Settings → System → About), and what changed in your personal runbook for next time.