Before you start
- A computer
Method 1 Run a ping test
-
Step 1: Open Terminal
Right-click Start > Terminal (Mac: open Terminal).
-
Step 2: Ping 100 times
Run the command below. It sends 100 packets to Cloudflare’s DNS server.
-
Step 3: Read the result
At the end, look for Lost = X (Y% loss). 0% is ideal; above 1–2% causes noticeable problems in games and calls.
ping -n 100 1.1.1.1 (Windows)
ping -c 100 1.1.1.1 (Mac/Linux)Method 2 Find where the loss happens
-
Step 1: Ping your router
Run ping -n 100 192.168.1.1 (your router’s address). Loss here means a Wi-Fi or cable problem inside your home.
-
Step 2: Run pathping
On Windows, run pathping 1.1.1.1. After about 5 minutes it shows loss for each hop. Loss that starts at your provider’s first hop and continues to the end points to them.
pathping 1.1.1.1Common causes and fixes
- Wi-Fi interference or weak signal: use Ethernet or 5 GHz, change channel.
- Bad cable or port: swap them.
- Overloaded connection: stop big uploads/downloads; enable QoS.
- Line faults: report to your provider with pathping results.
Troubleshooting
Ping shows “Request timed out” for everything
The target may block ping or your connection is down. Try 8.8.8.8 and check your internet.
Loss only in the evening
Congestion at your provider during peak hours. Log results and contact them.
Frequently asked questions
What is acceptable packet loss?
0% on a wired connection. Under 1% is usually unnoticeable; 2%+ causes problems.
Can a VPN fix packet loss?
Rarely. Only if your provider’s route is the problem; usually it adds a hop.
Summary
Run ping -n 100 1.1.1.1 to measure loss, ping your router to check your home network, and use pathping to see where loss starts. Fix Wi-Fi and cables at home, and report line loss to your provider.
