Community Forum

Unreasonably high ping and or huge ping spikes

Highlighted
New Poster

Unreasonably high ping and or huge ping spikes

All games are basically unplayable with either 800+ ping or constant rubberbanding depending on the game being played.  Below are the results of a tracerout and the 2nd and 3rd hops are pretty bad.  Is that an issue on my end and or is there anything I can do?

 

 

C:\WINDOWS\system32>tracert 75.75.75.75

Tracing route to cdns01.comcast.net [75.75.75.75]
over a maximum of 30 hops:

1 1 ms 8 ms 1 ms 192.168.1.1
2 1808 ms 19 ms 17 ms 96.120.88.85
3 1791 ms 18 ms 19 ms po-302-1210-rur02.sfgeary.ca.sfba.comcast.net [162.151.31.89]
4 13 ms 16 ms 43 ms be-313-rar01.hayward.ca.sfba.comcast.net [162.151.79.93]
5 18 ms 14 ms 18 ms be-1-ur04-d.sanjose.ca.sfba.comcast.net [68.85.154.157]
6 14 ms 16 ms 18 ms dns-sw02.sanjose.ca.sfba.comcast.net [68.85.86.30]
7 15 ms 15 ms 19 ms cdns01.comcast.net [75.75.75.75]

Trace complete.

Highlighted
Regular Contributor

Re: Unreasonably high ping and or huge ping spikes

From what I can tell, traceroute (tracert) on windows uses ICMP echo request packets whereas traceroute on *nix systems use UDP.   This matters because ICMP packets are considered low priority packets on a network; i.e., can be dropped if things are really bad or delayed.   This is not the case with UDP packets.

 

Traceroute is going to send three packets to each router along the path to your destination.   The times you see printed for each line is the round trip time (rtt) for each packet.   

 

What I see in your output is:

  - The first router, 192.168.1.1, i.e. *your* router was slow to respond to the second packet.   It really should not take 8 ms to get a response from your local router.   A gigabit link will typically report sub ms times reaching the first router.   Based on your times, I'd think you're using wifi.    Here's what I see using a 1Gb connected device:

 

avalanche:~/ $ traceroute 75.75.75.75

traceroute to 75.75.75.75 (75.75.75.75), 64 hops max, 52 byte packets

 1  zone0 (192.168.64.1)  0.970 ms  0.326 ms  0.287 ms

 2  96.120.96.121 (96.120.96.121)  8.445 ms  8.330 ms  8.523 ms

 3  96.110.232.89 (96.110.232.89)  9.079 ms  8.308 ms  9.482 ms

 4  be-1-ar01.sandy.ut.utah.comcast.net (162.151.49.137)  10.501 ms  9.141 ms  9.338 ms

 5  68.87.170.14 (68.87.170.14)  8.552 ms  8.763 ms  9.583 ms

 6  dns-sw02.sandy.ut.utah.comcast.net (68.87.170.30)  8.378 ms  11.969 ms  9.220 ms

 7  cdns01.comcast.net (75.75.75.75)  9.179 ms  13.068 ms  8.458 ms

avalanche:~ /

 

And here's wifi:

element: 10:35:31 > traceroute 75.75.75.75

traceroute to 75.75.75.75 (75.75.75.75), 64 hops max, 52 byte packets

 1  zone0 (192.168.64.1)  2.492 ms  1.857 ms  1.494 ms

 2  96.120.96.121 (96.120.96.121)  11.959 ms  10.572 ms  9.838 ms

 3  96.110.232.89 (96.110.232.89)  9.989 ms  10.985 ms  10.234 ms

 4  be-1-ar01.sandy.ut.utah.comcast.net (162.151.49.137)  10.964 ms  11.912 ms  11.231 ms

 5  68.87.170.14 (68.87.170.14)  11.236 ms  10.871 ms  10.291 ms

 6  dns-sw02.sandy.ut.utah.comcast.net (68.87.170.30)  12.089 ms  10.852 ms  10.312 ms

 7  cdns01.comcast.net (75.75.75.75)  10.751 ms  16.171 ms  9.976 ms

element: 10:35:37 > 

 

 - Next, the first packet between your system and the first comcast router (96.120.88.85) has a *huge* latency relative to the other packets.    The same is true for the next router (162.151.31.89).  The rest of the router hops have very reasonable times for all packets.

 

I would start looking at your home wifi.   Having 8 ms rtt suggests there's some traffic or possibly congestion on your wifi.     I would test with a wired connection and if things look good there then it's more evidence there's a problem on wifi.    If you still see 1-2 s (1000 - 2000 ms) rtt then I would look to using UDP packets instead of ICMP and see where that goes.

Highlighted
Expert

Re: Unreasonably high ping and or huge ping spikes


@bmcheung wrote:

All games are basically unplayable with either 800+ ping or constant rubberbanding depending on the game being played.  Below are the results of a tracerout and the 2nd and 3rd hops are pretty bad.  Is that an issue on my end and or is there anything I can do?

 

 

C:\WINDOWS\system32>tracert 75.75.75.75

Tracing route to cdns01.comcast.net [75.75.75.75]
over a maximum of 30 hops:

1 1 ms 8 ms 1 ms 192.168.1.1
2 1808 ms 19 ms 17 ms 96.120.88.85
3 1791 ms 18 ms 19 ms po-302-1210-rur02.sfgeary.ca.sfba.comcast.net [162.151.31.89]
4 13 ms 16 ms 43 ms be-313-rar01.hayward.ca.sfba.comcast.net [162.151.79.93]
5 18 ms 14 ms 18 ms be-1-ur04-d.sanjose.ca.sfba.comcast.net [68.85.154.157]
6 14 ms 16 ms 18 ms dns-sw02.sanjose.ca.sfba.comcast.net [68.85.86.30]
7 15 ms 15 ms 19 ms cdns01.comcast.net [75.75.75.75]

Trace complete.


There is nothing wrong with your trace output. Those 2 ping spikes that you see do not carry through to the farther upstream hops or to the destination server so they are likely to be just an aberration. Bear in mind that this is NOT to say that you are not experiencing a problem, but that trace doesn't confirm anything. Those routers may have just been too busy forwarding real traffic so they rate limited / deprioritized the ICMP ping packets.

 

http://customer.xfinity.com/help-and-support/internet/run-traceroute-command/

 

https://www.nanog.org/meetings/nanog47/presentations/Sunday/RAS_Traceroute_N47_Sun.pdf



I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!