dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
734
share rss forum feed

zer0c123

join:2005-05-29
San Francisco, CA

1 edit

[Connectivity] Constant Ping Spikes, San Francisco, CA

Since the weekend of November 3rd, I have noticed latency spikes in my online games on a wired connection. I'm located in San Francisco, CA 94134 zip code and had comcast internet since 2010 and never had latency issues. Maybe late night service outages, but it's usually cleared up in a few hours.

I am using a Linksys WRT54G router and Motorola SB6120 cable modem. The cable connection comes into my home and is split 3 ways. 2 TVs and the other for internet. Basic cable TV and high speed internet.

The lag spikes are pretty random, but I would say they occur every minute or two. Whenever I notice gameplay lag, I check my in-game ping and see that it had gone from green to red or sometimes green to yellow. It lasts for 1-2 secons and goes back up to green. To rule of the PS3 games, I tried a game on PC, such as counter strike. One good thing is that counter-strike shows the numbers for pings. In this game, I see my ping go all over the place from 12 ms and slowly go up 100 ms, then back down to like 80, 60, etc. I have tried power cycling the equipment, removing router, swap splitters, remove splitter, swap coax cables, and swap ethernet cables. Nothing has worked.

In terms of internet browsing and streaming, the issues are not too noticeable. On a few occasions, I will get a message saying the webpage failed to load, but I hit refresh to load it backup. I don't believe that I have seen issues in streaming netflex. Cable television doesn't seem to have any issues, except for one thing I noticed. I have a new HDTV and one old CRT tv. Lately on the CRT, local channel 2 looks slightly fuzzy to me. It seems like there are angled wavy lines across the screen. The picture is still viewable, but it's not as clear compared to the others channels, which are fine. I'm wondering if it's comcast's network upgrade for the analog to digital causing these latency issues. For last month or two, certain channels have been displaying a message that comcast is going end analog signals and start converting it to digital.

Pings, tracerts and modem logs are below. Based on the information, is there anything that indicates that this is a problem on comcasts end or my cable modem?

tracert for www.comcast.net: and google. I ran it a few times around 6 pm-10pm today until I got a result that was worth noting.

Tracing route to www.google.com [2001:4860:4001:803::1012]
over a maximum of 30 hops:
1 38 ms 27 ms 27 ms 2001:558:6045:db::1
2 10 ms * 14 ms te-8-4-ur01.sfmission.ca.sfba.comcast.net [2001:558:82:309::1]
3 13 ms 25 ms 10 ms te-1-12-0-0-ar01.sfsutro.ca.sfba.comcast.net [2001:558:80:2::1]
4 13 ms 21 ms 21 ms he-1-8-0-0-cr01.sanjose.ca.ibone.comcast.net [2001:558:0:f6f9::1]
5 11 ms 11 ms 12 ms pos-0-5-0-0-pe01.529bryant.ca.ibone.comcast.net [2001:558:0:f600::2]
6 64 ms 12 ms 11 ms 2001:559::386
7 14 ms 20 ms 15 ms 2001:4860::1:0:21
8 14 ms 13 ms 14 ms 2001:4860:0:1::1b7
9 12 ms 12 ms 13 ms nuq04s09-in-x12.1e100.net [2001:4860:4001:803::1012]

Trace complete.
tracert www.comcast.net
Tracing route to a1526.dscg.akamai.net [2001:559:0:42::6011:a4b0]
over a maximum of 30 hops:
1 29 ms 23 ms 10 ms 2001:558:6045:db::1
2 9 ms 9 ms 10 ms te-8-4-ur01.sfmission.ca.sfba.comcast.net [2001:558:82:309::1]
3 12 ms 10 ms 42 ms te-1-10-0-3-ar01.sfsutro.ca.sfba.comcast.net [2001:558:80:c5::1]
4 13 ms 20 ms 22 ms he-1-6-0-0-cr01.sanjose.ca.ibone.comcast.net [2001:558:0:f6a7::1]
5 21 ms 21 ms 22 ms pos-2-14-0-0-cr01.losangeles.ca.ibone.comcast.net [2001:558:0:f56e::2]
6 63 ms 57 ms 57 ms he-0-11-0-0-cr01.dallas.tx.ibone.comcast.net [2001:558:0:f5c9::2]
7 56 ms 53 ms 54 ms pos-0-3-0-0-pe01.1950stemmons.tx.ibone.comcast.net [2001:558:0:f5a6::2]
8 65 ms 51 ms 51 ms 2001:559:0:42::6011:a4b0

Tracing route to a1526.dscg.akamai.net [2001:559:0:301::6011:6d6a]over a maximum of 30 hops:
1 23 ms 47 ms 27 ms 2001:558:6045:db::1
2 10 ms 11 ms 10 ms te-8-4-ur01.sfmission.ca.sfba.comcast.net [2001:558:82:309::1]
3 14 ms 13 ms 9 ms te-1-12-0-0-ar01.sfsutro.ca.sfba.comcast.net [2001:558:80:2::1]
4 22 ms 21 ms 21 ms he-1-8-0-0-cr01.sanjose.ca.ibone.comcast.net [2001:558:0:f6f9::1]
5 12 ms 11 ms 12 ms pos-0-0-0-0-pe01.529bryant.ca.ibone.comcast.net[2001:558:0:f59e::2]
6 169 ms 171 ms 202 ms 2001:559::16
7 11 ms 12 ms 11 ms 2001:559:0:301::6011:6d6a

tracert www.google.com

Tracing route to www.google.com [2001:4860:4001:801::1012] over a maximum of 30 hops:
1 20 ms 27 ms 27 ms 2001:558:6045:db::1
2 9 ms 10 ms 8 ms te-8-4-ur01.sfmission.ca.sfba.comcast.net [2001:558:82:309::1]
3 11 ms 13 ms 13 ms te-1-12-0-0-ar01.sfsutro.ca.sfba.comcast.net [2001:558:80:2::1]
4 15 ms 21 ms 21 ms he-1-7-0-0-cr01.sanjose.ca.ibone.comcast.net [2001:558:0:f6a6::1]
5 12 ms 11 ms 13 ms pos-0-7-0-0-pe01.529bryant.ca.ibone.comcast.net[2001:558:0:f632::2]
6 12 ms 11 ms 12 ms 2001:559::386
7 14 ms 15 ms 14 ms 2001:4860::1:0:21
8 13 ms 13 ms 14 ms 2001:4860:0:1::1af
9 12 ms 13 ms 14 ms nuq04s07-in-x12.1e100.net [2001:4860:4001:801::1012]

comcast.net
Tracing route to a1526.dscg.akamai.net [2001:559:0:301::6011:6d6a] over a maximum of 30 hops:
1 23 ms 47 ms 27 ms 2001:558:6045:db::1
2 10 ms 11 ms 10 ms te-8-4-ur01.sfmission.ca.sfba.comcast.net [2001:558:82:309::1]
3 14 ms 13 ms 9 ms te-1-12-0-0-ar01.sfsutro.ca.sfba.comcast.net [2001:558:80:2::1]
4 22 ms 21 ms 21 ms he-1-8-0-0-cr01.sanjose.ca.ibone.comcast.net [2001:558:0:f6f9::1]
5 12 ms 11 ms 12 ms pos-0-0-0-0-pe01.529bryant.ca.ibone.comcast.net[2001:558:0:f59e::2]
6 169 ms 171 ms 202 ms 2001:559::16
7 11 ms 12 ms 11 ms 2001:559:0:301::6011:6d6a

Trace complete.

I pinged google and let it run for a few minutes. The log is just too long post, but here is the summary.

There were a few lines that displayed request timeouts.

Ping statistics for 2001:4860:4001:801::1011:
Packets: Sent = 1417, Received = 1405, Lost = 12 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 401ms, Average = 13ms

Reply from 173.194.79.99: bytes=32 time=35ms TTL=46
Reply from 173.194.79.99: bytes=32 time=34ms TTL=46
Reply from 173.194.79.99: bytes=32 time=50ms TTL=46
Request timed out.

I think this test was with the router still connected.
Ping statistics for 173.194.79.99:
Packets: Sent = 2529, Received = 2508, Lost = 21 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 106ms, Average = 34ms
Control-C

Modem Signal Screenshot
»i.imgur.com/ukkWz.png




modem info:

Model Name: SB6120
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.6-SCM00-NOSH
Boot Version: PSPU-Boot 1.0.0.4m1
Hardware Version: 3.0
Firmware Build Time: Apr 17 2012 15:09:37