Ping spikes over wired network

Toggle sidebar Toggle sidebar
X

xtrememudder89

Prominent
Mar 20, 2017
2
0
510
I keep getting lag spikes in games like CS:GO over my wired connection. The spikes aren't just limited to that game, they happen in others too. I have no idea what's wrong or if I should be contacting my ISP or not.

I'm on a desktop using a wired connection to the motherboard Ethernet jack.
Here are two trace routes and a ping-t.
-----------------------------------------------
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 159 ms 14 ms 10.170.16.1
3 27 ms 12 ms 12 ms gateway2-b4-1414-sth3blocal1.str.ptd.net [207.44.122.221]
4 17 ms 15 ms 14 ms gateway2-be12-nyc22str.nyc.ptd.net [207.44.122.97]
5 34 ms 12 ms 16 ms pni-google.nyc.ptd.net [207.44.112.2]
6 12 ms 13 ms 13 ms 108.170.248.1
7 13 ms 13 ms 14 ms 108.170.235.81
8 65 ms 173 ms 14 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.
-----------------------------------------------
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 74 ms 4 ms 4 ms 192.168.0.1
2 15 ms 10 ms 10 ms 10.170.16.1
3 13 ms 13 ms 12 ms gateway2-b4-1414-sth3blocal1.str.ptd.net [207.44.122.221]
4 16 ms 16 ms 17 ms gateway2-be12-nyc22str.nyc.ptd.net [207.44.122.97]
5 114 ms 13 ms 12 ms pni-google.nyc.ptd.net [207.44.112.2]
6 15 ms 15 ms 15 ms 108.170.248.1
7 213 ms 182 ms 159 ms 108.170.235.81
8 14 ms 11 ms 11 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.
-----------------------------------------------
ping www.google.com -t

Pinging www.google.com [204.186.55.242] with 32 bytes of data:
Reply from 204.186.55.242: bytes=32 time=9ms TTL=60
Reply from 204.186.55.242: bytes=32 time=10ms TTL=60
Reply from 204.186.55.242: bytes=32 time=9ms TTL=60
Reply from 204.186.55.242: bytes=32 time=8ms TTL=60
Reply from 204.186.55.242: bytes=32 time=11ms TTL=60
Reply from 204.186.55.242: bytes=32 time=9ms TTL=60
Reply from 204.186.55.242: bytes=32 time=9ms TTL=60
Reply from 204.186.55.242: bytes=32 time=53ms TTL=60
Reply from 204.186.55.242: bytes=32 time=15ms TTL=60
Reply from 204.186.55.242: bytes=32 time=9ms TTL=60
Reply from 204.186.55.242: bytes=32 time=17ms TTL=60
Reply from 204.186.55.242: bytes=32 time=901ms TTL=60
Reply from 204.186.55.242: bytes=32 time=81ms TTL=60
Reply from 204.186.55.242: bytes=32 time=8ms TTL=60
Reply from 204.186.55.242: bytes=32 time=10ms TTL=60
Reply from 204.186.55.242: bytes=32 time=10ms TTL=60
Reply from 204.186.55.242: bytes=32 time=255ms TTL=60
Reply from 204.186.55.242: bytes=32 time=230ms TTL=60
Reply from 204.186.55.242: bytes=32 time=9ms TTL=60
Reply from 204.186.55.242: bytes=32 time=8ms TTL=60
Reply from 204.186.55.242: bytes=32 time=9ms TTL=60
Reply from 204.186.55.242: bytes=32 time=9ms TTL=60
Reply from 204.186.55.242: bytes=32 time=18ms TTL=60
Reply from 204.186.55.242: bytes=32 time=8ms TTL=60
Reply from 204.186.55.242: bytes=32 time=8ms TTL=60
Reply from 204.186.55.242: bytes=32 time=8ms TTL=60
Reply from 204.186.55.242: bytes=32 time=9ms TTL=60
Reply from 204.186.55.242: bytes=32 time=45ms TTL=60
Reply from 204.186.55.242: bytes=32 time=8ms TTL=60
Reply from 204.186.55.242: bytes=32 time=130ms TTL=60
Reply from 204.186.55.242: bytes=32 time=18ms TTL=60
Reply from 204.186.55.242: bytes=32 time=9ms TTL=60
Reply from 204.186.55.242: bytes=32 time=9ms TTL=60
Reply from 204.186.55.242: bytes=32 time=11ms TTL=60
Reply from 204.186.55.242: bytes=32 time=94ms TTL=60
Reply from 204.186.55.242: bytes=32 time=9ms TTL=60
Reply from 204.186.55.242: bytes=32 time=16ms TTL=60
Reply from 204.186.55.242: bytes=32 time=8ms TTL=60
Reply from 204.186.55.242: bytes=32 time=8ms TTL=60

Ping statistics for 204.186.55.242:
Packets: Sent = 39, Received = 39, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 901ms, Average = 53ms
 
Solution
B
The problems start in hop1 this means it is either your PC or your router. Try another device and ping the router to see if it also has issues.

These are hard to find router you could see if there is newer firmware. If it is your PC it can be many things. One of the most common if you have killer chipset is that network accelerator software
Sort by date Sort by votes
B

bill001g

Titan
Aug 9, 2012
28,318
2,754
125,640
It does not tell much when the problem is intermittent. The tracert may or may not be valid if the problem does not occur constantly.

If the tracert is correct there is a problem in google network which of course you and your ISP can do nothing about.

What you want to do is run constant ping commands from a number of CMD windows the hops in the trace. Hop 1, hop 2 and then the final hop is best. Hop1 is your router, hop 2 is the first ISP router. These 2 locations are the easist to get fixed You can continue doning more hops but once you get outside your ISP network how can you get it fixed. It is not like you can call google they will think your a hacker even if you could somehow find a number to googles tech support group.
 
Upvote 1 Downvote
X

xtrememudder89

Prominent
Mar 20, 2017
2
0
510


Okay I ran 3 simultaneous ping windows and got this.

http://imgur.com/a/J8UuT

What do you think?

Different test in text
ping 192.168.0.1 -t

Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=35ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=3ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=56ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=84ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=181ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=168ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=187ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=150ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=224ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=67ms TTL=64
Reply from 192.168.0.1: bytes=32 time=13ms TTL=64
Reply from 192.168.0.1: bytes=32 time=64ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=58ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=66ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=49ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=40ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=35ms TTL=64
Reply from 192.168.0.1: bytes=32 time=28ms TTL=64
Reply from 192.168.0.1: bytes=32 time=25ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=16ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=10ms TTL=64

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

10.170.16.1 -t

Pinging 10.170.16.1 with 32 bytes of data:
Reply from 10.170.16.1: bytes=32 time=9ms TTL=254
Reply from 10.170.16.1: bytes=32 time=9ms TTL=254
Reply from 10.170.16.1: bytes=32 time=124ms TTL=254
Reply from 10.170.16.1: bytes=32 time=9ms TTL=254
Request timed out.
Reply from 10.170.16.1: bytes=32 time=9ms TTL=254
Reply from 10.170.16.1: bytes=32 time=7ms TTL=254
Reply from 10.170.16.1: bytes=32 time=15ms TTL=254
Reply from 10.170.16.1: bytes=32 time=70ms TTL=254
Reply from 10.170.16.1: bytes=32 time=8ms TTL=254
Reply from 10.170.16.1: bytes=32 time=7ms TTL=254
Reply from 10.170.16.1: bytes=32 time=6ms TTL=254
Reply from 10.170.16.1: bytes=32 time=9ms TTL=254
Reply from 10.170.16.1: bytes=32 time=39ms TTL=254
Reply from 10.170.16.1: bytes=32 time=15ms TTL=254
Reply from 10.170.16.1: bytes=32 time=7ms TTL=254
Reply from 10.170.16.1: bytes=32 time=6ms TTL=254
Reply from 10.170.16.1: bytes=32 time=10ms TTL=254
Reply from 10.170.16.1: bytes=32 time=7ms TTL=254
Reply from 10.170.16.1: bytes=32 time=7ms TTL=254
Reply from 10.170.16.1: bytes=32 time=154ms TTL=254
Reply from 10.170.16.1: bytes=32 time=6ms TTL=254
Reply from 10.170.16.1: bytes=32 time=7ms TTL=254
Reply from 10.170.16.1: bytes=32 time=6ms TTL=254
Reply from 10.170.16.1: bytes=32 time=7ms TTL=254
Reply from 10.170.16.1: bytes=32 time=93ms TTL=254
Reply from 10.170.16.1: bytes=32 time=7ms TTL=254
Reply from 10.170.16.1: bytes=32 time=6ms TTL=254
Reply from 10.170.16.1: bytes=32 time=14ms TTL=254
Reply from 10.170.16.1: bytes=32 time=6ms TTL=254
Reply from 10.170.16.1: bytes=32 time=7ms TTL=254
Reply from 10.170.16.1: bytes=32 time=7ms TTL=254
Reply from 10.170.16.1: bytes=32 time=135ms TTL=254
Reply from 10.170.16.1: bytes=32 time=15ms TTL=254
Reply from 10.170.16.1: bytes=32 time=7ms TTL=254
Reply from 10.170.16.1: bytes=32 time=11ms TTL=254
Reply from 10.170.16.1: bytes=32 time=7ms TTL=254
Reply from 10.170.16.1: bytes=32 time=106ms TTL=254
Reply from 10.170.16.1: bytes=32 time=7ms TTL=254
Reply from 10.170.16.1: bytes=32 time=7ms TTL=254
Reply from 10.170.16.1: bytes=32 time=12ms TTL=254
Reply from 10.170.16.1: bytes=32 time=7ms TTL=254
Reply from 10.170.16.1: bytes=32 time=8ms TTL=254
Reply from 10.170.16.1: bytes=32 time=8ms TTL=254
Reply from 10.170.16.1: bytes=32 time=156ms TTL=254
Reply from 10.170.16.1: bytes=32 time=8ms TTL=254
Reply from 10.170.16.1: bytes=32 time=7ms TTL=254
Reply from 10.170.16.1: bytes=32 time=8ms TTL=254
Reply from 10.170.16.1: bytes=32 time=8ms TTL=254
Reply from 10.170.16.1: bytes=32 time=165ms TTL=254
Reply from 10.170.16.1: bytes=32 time=6ms TTL=254
Reply from 10.170.16.1: bytes=32 time=8ms TTL=254
Reply from 10.170.16.1: bytes=32 time=11ms TTL=254
Reply from 10.170.16.1: bytes=32 time=13ms TTL=254
Reply from 10.170.16.1: bytes=32 time=17ms TTL=254
Reply from 10.170.16.1: bytes=32 time=6ms TTL=254
Reply from 10.170.16.1: bytes=32 time=7ms TTL=254
Reply from 10.170.16.1: bytes=32 time=11ms TTL=254
Reply from 10.170.16.1: bytes=32 time=8ms TTL=254
Reply from 10.170.16.1: bytes=32 time=10ms TTL=254
Reply from 10.170.16.1: bytes=32 time=7ms TTL=254
Reply from 10.170.16.1: bytes=32 time=169ms TTL=254
Reply from 10.170.16.1: bytes=32 time=7ms TTL=254
Reply from 10.170.16.1: bytes=32 time=8ms TTL=254

Ping statistics for 10.170.16.1:
Packets: Sent = 64, Received = 63, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 169ms, Average = 26ms

ping 8.8.8.8 -t

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=12ms TTL=56
Reply from 8.8.8.8: bytes=32 time=10ms TTL=56
Reply from 8.8.8.8: bytes=32 time=10ms TTL=56
Reply from 8.8.8.8: bytes=32 time=17ms TTL=56
Reply from 8.8.8.8: bytes=32 time=11ms TTL=56
Reply from 8.8.8.8: bytes=32 time=153ms TTL=56
Reply from 8.8.8.8: bytes=32 time=106ms TTL=56
Reply from 8.8.8.8: bytes=32 time=41ms TTL=56
Reply from 8.8.8.8: bytes=32 time=100ms TTL=56
Reply from 8.8.8.8: bytes=32 time=11ms TTL=56
Reply from 8.8.8.8: bytes=32 time=214ms TTL=56
Reply from 8.8.8.8: bytes=32 time=13ms TTL=56
Reply from 8.8.8.8: bytes=32 time=27ms TTL=56
Reply from 8.8.8.8: bytes=32 time=11ms TTL=56
Reply from 8.8.8.8: bytes=32 time=80ms TTL=56
Reply from 8.8.8.8: bytes=32 time=26ms TTL=56
Reply from 8.8.8.8: bytes=32 time=58ms TTL=56
Reply from 8.8.8.8: bytes=32 time=21ms TTL=56
Reply from 8.8.8.8: bytes=32 time=64ms TTL=56
Reply from 8.8.8.8: bytes=32 time=10ms TTL=56
Reply from 8.8.8.8: bytes=32 time=59ms TTL=56
Reply from 8.8.8.8: bytes=32 time=11ms TTL=56
Reply from 8.8.8.8: bytes=32 time=86ms TTL=56
Reply from 8.8.8.8: bytes=32 time=11ms TTL=56
Request timed out.
Reply from 8.8.8.8: bytes=32 time=10ms TTL=56
Reply from 8.8.8.8: bytes=32 time=11ms TTL=56
Reply from 8.8.8.8: bytes=32 time=18ms TTL=56
Reply from 8.8.8.8: bytes=32 time=17ms TTL=56
Reply from 8.8.8.8: bytes=32 time=12ms TTL=56
Reply from 8.8.8.8: bytes=32 time=11ms TTL=56
Reply from 8.8.8.8: bytes=32 time=14ms TTL=56
Reply from 8.8.8.8: bytes=32 time=11ms TTL=56
Reply from 8.8.8.8: bytes=32 time=20ms TTL=56
Reply from 8.8.8.8: bytes=32 time=13ms TTL=56
Reply from 8.8.8.8: bytes=32 time=95ms TTL=56
Reply from 8.8.8.8: bytes=32 time=11ms TTL=56
Reply from 8.8.8.8: bytes=32 time=12ms TTL=56
Reply from 8.8.8.8: bytes=32 time=20ms TTL=56
Reply from 8.8.8.8: bytes=32 time=12ms TTL=56
Reply from 8.8.8.8: bytes=32 time=94ms TTL=56
Reply from 8.8.8.8: bytes=32 time=10ms TTL=56
Reply from 8.8.8.8: bytes=32 time=11ms TTL=56
Reply from 8.8.8.8: bytes=32 time=11ms TTL=56
Reply from 8.8.8.8: bytes=32 time=10ms TTL=56
Reply from 8.8.8.8: bytes=32 time=10ms TTL=56
Reply from 8.8.8.8: bytes=32 time=13ms TTL=56
Reply from 8.8.8.8: bytes=32 time=140ms TTL=56
Reply from 8.8.8.8: bytes=32 time=13ms TTL=56
Reply from 8.8.8.8: bytes=32 time=11ms TTL=56
Reply from 8.8.8.8: bytes=32 time=13ms TTL=56
Reply from 8.8.8.8: bytes=32 time=13ms TTL=56
Reply from 8.8.8.8: bytes=32 time=134ms TTL=56
Reply from 8.8.8.8: bytes=32 time=13ms TTL=56
Reply from 8.8.8.8: bytes=32 time=10ms TTL=56
Reply from 8.8.8.8: bytes=32 time=11ms TTL=56
Reply from 8.8.8.8: bytes=32 time=9ms TTL=56
Reply from 8.8.8.8: bytes=32 time=11ms TTL=56
Reply from 8.8.8.8: bytes=32 time=10ms TTL=56
Reply from 8.8.8.8: bytes=32 time=168ms TTL=56
Reply from 8.8.8.8: bytes=32 time=10ms TTL=56
Reply from 8.8.8.8: bytes=32 time=13ms TTL=56
Reply from 8.8.8.8: bytes=32 time=20ms TTL=56
Reply from 8.8.8.8: bytes=32 time=11ms TTL=56
Reply from 8.8.8.8: bytes=32 time=11ms TTL=56

Ping statistics for 8.8.8.8:
Packets: Sent = 65, Received = 64, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 214ms, Average = 34ms
 
Upvote 0 Downvote
B

bill001g

Titan
Aug 9, 2012
28,318
2,754
125,640
The problems start in hop1 this means it is either your PC or your router. Try another device and ping the router to see if it also has issues.

These are hard to find router you could see if there is newer firmware. If it is your PC it can be many things. One of the most common if you have killer chipset is that network accelerator software
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom