Ping Spikes Every Few Seconds

[dolphinman12345]

This issue has persisted for quite a while, and has become exceedingly frustrating.
When I'm playing online games my ping spikes every few seconds, and I rubber-band like crazy.

I'm connected via ethernet, but tried a wireless adapter.
I've started in safe mode with networking.
Someone else in the house has fine connection so I know it's not the network itself.
I've pinged google from cmd and tried various speed tests, so I know it's not packet loss.
Network drivers are up to date and working properly.

Any advice?

I'll post a ping test here.

ping www.google.com -t

Pinging www.google.com [216.58.217.68] with 32 bytes of data:
Reply from 216.58.217.68: bytes=32 time=261ms TTL=49
Reply from 216.58.217.68: bytes=32 time=34ms TTL=49
Reply from 216.58.217.68: bytes=32 time=84ms TTL=49
Reply from 216.58.217.68: bytes=32 time=24ms TTL=49
Reply from 216.58.217.68: bytes=32 time=31ms TTL=49
Reply from 216.58.217.68: bytes=32 time=28ms TTL=49
Reply from 216.58.217.68: bytes=32 time=46ms TTL=49
Reply from 216.58.217.68: bytes=32 time=27ms TTL=49
Reply from 216.58.217.68: bytes=32 time=56ms TTL=49
Reply from 216.58.217.68: bytes=32 time=30ms TTL=49
Reply from 216.58.217.68: bytes=32 time=53ms TTL=49
Reply from 216.58.217.68: bytes=32 time=32ms TTL=49
Reply from 216.58.217.68: bytes=32 time=38ms TTL=49
Reply from 216.58.217.68: bytes=32 time=43ms TTL=49
Reply from 216.58.217.68: bytes=32 time=49ms TTL=49
Reply from 216.58.217.68: bytes=32 time=404ms TTL=49
Reply from 216.58.217.68: bytes=32 time=100ms TTL=49
Reply from 216.58.217.68: bytes=32 time=267ms TTL=49
Reply from 216.58.217.68: bytes=32 time=46ms TTL=49
Reply from 216.58.217.68: bytes=32 time=109ms TTL=49
Reply from 216.58.217.68: bytes=32 time=27ms TTL=49
Reply from 216.58.217.68: bytes=32 time=30ms TTL=49
Reply from 216.58.217.68: bytes=32 time=31ms TTL=49
Reply from 216.58.217.68: bytes=32 time=25ms TTL=49
Reply from 216.58.217.68: bytes=32 time=22ms TTL=49
Reply from 216.58.217.68: bytes=32 time=28ms TTL=49
Reply from 216.58.217.68: bytes=32 time=25ms TTL=49
Reply from 216.58.217.68: bytes=32 time=23ms TTL=49
Reply from 216.58.217.68: bytes=32 time=30ms TTL=49
Reply from 216.58.217.68: bytes=32 time=21ms TTL=49
Reply from 216.58.217.68: bytes=32 time=294ms TTL=49
Reply from 216.58.217.68: bytes=32 time=27ms TTL=49
Reply from 216.58.217.68: bytes=32 time=187ms TTL=49
Reply from 216.58.217.68: bytes=32 time=30ms TTL=49
Reply from 216.58.217.68: bytes=32 time=111ms TTL=49
Reply from 216.58.217.68: bytes=32 time=21ms TTL=49
Reply from 216.58.217.68: bytes=32 time=28ms TTL=49
Reply from 216.58.217.68: bytes=32 time=25ms TTL=49
Reply from 216.58.217.68: bytes=32 time=28ms TTL=49
Reply from 216.58.217.68: bytes=32 time=79ms TTL=49
Reply from 216.58.217.68: bytes=32 time=30ms TTL=49
Reply from 216.58.217.68: bytes=32 time=22ms TTL=49
Reply from 216.58.217.68: bytes=32 time=23ms TTL=49
Reply from 216.58.217.68: bytes=32 time=27ms TTL=49
Reply from 216.58.217.68: bytes=32 time=41ms TTL=49
Reply from 216.58.217.68: bytes=32 time=24ms TTL=49
Reply from 216.58.217.68: bytes=32 time=26ms TTL=49
Reply from 216.58.217.68: bytes=32 time=384ms TTL=49
Reply from 216.58.217.68: bytes=32 time=25ms TTL=49
Reply from 216.58.217.68: bytes=32 time=251ms TTL=49
Reply from 216.58.217.68: bytes=32 time=86ms TTL=49
Reply from 216.58.217.68: bytes=32 time=137ms TTL=49
Reply from 216.58.217.68: bytes=32 time=27ms TTL=49
Reply from 216.58.217.68: bytes=32 time=61ms TTL=49
Reply from 216.58.217.68: bytes=32 time=30ms TTL=49
Reply from 216.58.217.68: bytes=32 time=27ms TTL=49
Reply from 216.58.217.68: bytes=32 time=29ms TTL=49
Reply from 216.58.217.68: bytes=32 time=24ms TTL=49
Reply from 216.58.217.68: bytes=32 time=61ms TTL=49
Reply from 216.58.217.68: bytes=32 time=31ms TTL=49
Reply from 216.58.217.68: bytes=32 time=28ms TTL=49
Reply from 216.58.217.68: bytes=32 time=31ms TTL=49
Reply from 216.58.217.68: bytes=32 time=351ms TTL=49
Reply from 216.58.217.68: bytes=32 time=25ms TTL=49
Reply from 216.58.217.68: bytes=32 time=235ms TTL=49
Reply from 216.58.217.68: bytes=32 time=24ms TTL=49
Reply from 216.58.217.68: bytes=32 time=95ms TTL=49
Reply from 216.58.217.68: bytes=32 time=25ms TTL=49
Reply from 216.58.217.68: bytes=32 time=26ms TTL=49
Reply from 216.58.217.68: bytes=32 time=29ms TTL=49
Reply from 216.58.217.68: bytes=32 time=24ms TTL=49
Reply from 216.58.217.68: bytes=32 time=28ms TTL=49
Reply from 216.58.217.68: bytes=32 time=47ms TTL=49
Reply from 216.58.217.68: bytes=32 time=23ms TTL=49
Reply from 216.58.217.68: bytes=32 time=27ms TTL=49
Reply from 216.58.217.68: bytes=32 time=26ms TTL=49
Reply from 216.58.217.68: bytes=32 time=29ms TTL=49
Reply from 216.58.217.68: bytes=32 time=74ms TTL=49
Reply from 216.58.217.68: bytes=32 time=23ms TTL=49
Reply from 216.58.217.68: bytes=32 time=430ms TTL=49
Reply from 216.58.217.68: bytes=32 time=39ms TTL=49
Reply from 216.58.217.68: bytes=32 time=325ms TTL=49
Reply from 216.58.217.68: bytes=32 time=27ms TTL=49
Reply from 216.58.217.68: bytes=32 time=250ms TTL=49
Reply from 216.58.217.68: bytes=32 time=91ms TTL=49
Reply from 216.58.217.68: bytes=32 time=50ms TTL=49
Reply from 216.58.217.68: bytes=32 time=28ms TTL=49
Reply from 216.58.217.68: bytes=32 time=26ms TTL=49

Ping statistics for 216.58.217.68:
Packets: Sent = 88, Received = 88, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 21ms, Maximum = 430ms, Average = 75ms

 

[Ralston18]

Try another known working ethernet cable. Cat 5e.

Are you using an ethernet wall jack? Could be a faulty connection within or on the other end.

Any switches or hubs within your network?

Who manages the "house" router?

 

[dolphinman12345]

Try another known working ethernet cable. Cat 5e.

Are you using an ethernet wall jack? Could be a faulty connection within or on the other end.

Any switches or hubs within your network?

Who manages the "house" router?

Tried another ethernet cable, no dice.

My cable is directed routed to the router.

No hubs or switches.

I'm the one currently managing the router.

It seems I also jumped the gun on the ping test the other computer. I tested it again on that same other computer, and on a third computer, and the results were the same as mine. Which means that the issue within the network itself.

I'll try and look for a router firmware update, but after that I'm at a loss.

 

[Ralston18]

What that means is there is some common factor if multiple computers are affected.

The problem may not necessarily be within your network. There are other possibilities.

Originally a minor problem is getting worse ("exceedingly frustrating"). Some deteriorating physical connection or cable.

E.g., the connection from your ISP to modem or modem/router. Check those cables as well. Inside and outside.

Look for signs of damage, corrosion, bare metal showing, etc. on cables, connectors., Coax splitters are often the culprit especially any that are located outside and exposed to the elements. Likewise internal telephone jack ADSL splitters/filters (if applicable) can cause problems.

Also call your ISP. Ask them to run some tests from their end. May take a few calls/complaints.

 

[dolphinman12345]

What that means is there is some common factor if multiple computers are affected.

The problem may not necessarily be within your network. There are other possibilities.

Originally a minor problem is getting worse ("exceedingly frustrating"). Some deteriorating physical connection or cable.

E.g., the connection from your ISP to modem or modem/router. Check those cables as well. Inside and outside.

Look for signs of damage, corrosion, bare metal showing, etc. on cables, connectors., Coax splitters are often the culprit especially any that are located outside and exposed to the elements. Likewise internal telephone jack ADSL splitters/filters (if applicable) can cause problems.

Also call your ISP. Ask them to run some tests from their end. May take a few calls/complaints.

Just did a check up on all of the cables. All of them look new and in good condition. There is no visible damage or issue.
Gonna go give my ISP a call and post how it goes.

 

[Ralston18]

Agree.

However, consider starting to swap out those "new and in good condition" looking cables. One at a time.

Still may be flaw somewhere. Maybe a poor termination. Especially if the cables came from the ISP or with some device.

Such cables are often made as cheaply as possible sans any testing or meaningful QA.

 

[dolphinman12345]

Agree.

However, consider starting to swap out those "new and in good condition" looking cables. One at a time.

Still may be flaw somewhere. Maybe a poor termination. Especially if the cables came from the ISP or with some device.

Such cables are often made as cheaply as possible sans any testing or meaningful QA.

Just called em up. Got hooked up with Tier 3 tech support right of the bat, and they noticed something was wrong. They're sending a guy to take a look. Thanks for all the help.