High ping spikes to router local ip address

WhiteRenard

Honorable
Sep 25, 2012
38
0
10,540
Hello,

For a while now I've been having some serious high ping spikes when I was playing online and I blamed my ISP for it. They claimed nothing is wrong etc etc...
Today I ran Namebench to see if I could find a better DNS so maybe I can reduce these ping spikes and what grabbed my attention was my local ip address that was in the results and with an average ping of 215...

I ran -n 100 pings on 192.168.0.1 in CMD and saw random high ping spikes, as high as 600-700ms! I'm guessing this is what's been causing my ping spikes in the games as well.

I tried connecting the router with a LAN cable and the result was pretty much the same so I ruled out wireless interference.

I found out that whenever my router was connected (wired or wireless) BUT my phone line wasn't plugged in, I'd get normal pings but when I plug in the phone line, random ping spikes start.
We have 2 phone lines at home here and no phone is connected to the line that this router is using anywhere in the house.

Router firmware is also up to date. (TP-Link W8961ND)


Any ideas?
I'd really appreciate if you guys could help me out. :)


P.S. The phone cable is fine and healthy since I use it on another router (from another isp) and everything works fine.
 

BuddhaSkoota

Admirable


So, you're disconnecting the phone line from your modem/router and get low ping response? If not, please clarify.

Are you the only user in the house? Have you disconnected all wired and wireless devices and checked ping response? It could be an application that is accessing the Internet at periodic intervals (e.g. OS updater, antivirus, email, etc.).

Random high ping response doesn't necessarily indicate a problem. It could just mean there is network traffic on your LAN (wired or wireless).
 

WhiteRenard

Honorable
Sep 25, 2012
38
0
10,540


If I unplug the phone line from the back of my router, I got 1-2ms pings otherwise while connected I have random spikes.
I'm the only user connected to this router.
Here is an example:
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=190ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=3ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=3ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time<1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=3ms TTL=254
Reply from 192.168.0.1: bytes=32 time<1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=171ms TTL=254
Reply from 192.168.0.1: bytes=32 time=3ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=3ms TTL=254
Reply from 192.168.0.1: bytes=32 time=3ms TTL=254
Reply from 192.168.0.1: bytes=32 time=3ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time<1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time<1ms TTL=254
Reply from 192.168.0.1: bytes=32 time<1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time<1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=3ms TTL=254
Reply from 192.168.0.1: bytes=32 time=600ms TTL=254
Reply from 192.168.0.1: bytes=32 time<1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time<1ms TTL=254
Reply from 192.168.0.1: bytes=32 time<1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=4ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time<1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=3ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time<1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=4ms TTL=254
Reply from 192.168.0.1: bytes=32 time<1ms TTL=254
Reply from 192.168.0.1: bytes=32 time<1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=47ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254
Reply from 192.168.0.1: bytes=32 time=2ms TTL=254
Reply from 192.168.0.1: bytes=32 time=1ms TTL=254

Ping statistics for 192.168.0.1:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 600ms, Average = 11ms
 

Lim Bin

Reputable
Jul 23, 2015
2
0
4,510


Have you got the solution? I had same problem during gaming. SPike and lag with ping fluctuate from 30ms-200ms using TP-Link W8961ND which just installed recently. if you got the solution, please share it to me. Thanks!
 

WhiteRenard

Honorable
Sep 25, 2012
38
0
10,540


No, I never did figure it out. Since I have two phone lines and two separate connections, I'm just using my healthy one for gaming. The faulty one is just for browsing, downloading etc...

You mentioned your ping fluctuates between 30-200. Are you pinging your local router address? like 192.168.1.1? or something similar?

Cause my problem was with the router itself but it sounds like you're pinging an external ip address, a server since your lowest ping is 30. If that is the case, then your issue is different. Check your SNR ratio and Line attenuation in router status/settings. If nothing is wrong with that, contact your isp.