US Cable Support > Comcast HSI > High Pings in Chicago

High Pings in Chicago

Post some tracerts and a linequality test. It may be them working in your area, the tracerts and linequality test will help to determine if the problem is on comcast's side.

reply to VacantLot
Does this help?

C:\Documents and Settings\Ron>tracert www.broadbandreports.com

Tracing route to broadbandreports.com [209.123.109.175]
over a maximum of 30 hops:

1 14 ms 13 ms 29 ms 12-211-128-1.client.attbi.com [12.211.128.1]
2 15 ms 26 ms 13 ms 12.244.108.81
3 13 ms 26 ms 12 ms 12.244.68.30
4 177 ms 176 ms 176 ms 12.244.72.242
5 172 ms 166 ms 174 ms gbr1-p50.cgcil.ip.att.net [12.123.5.74]
6 184 ms 186 ms 175 ms tbr1-p013502.cgcil.ip.att.net [12.122.11.33]
7 181 ms 185 ms 182 ms tbr1-p012301.n54ny.ip.att.net [12.122.10.1]
8 192 ms 189 ms 200 ms gar1-p3100.nwrnj.ip.att.net [12.123.214.181]
9 194 ms 194 ms 191 ms att.ge-0-0-0.gbr1.nwr.nac.net [12.119.140.30]
10 201 ms 199 ms 198 ms 1189.at-0-0-0.gbr2.nwr.nac.net [209.123.11.78]
11 194 ms 192 ms 193 ms 0.so-0-3-0.gbr1.oct.nac.net [209.123.11.233]
12 203 ms 201 ms 205 ms 0095.gi-1-1.msfc1.oct.nac.net [64.21.102.2]
13 194 ms 188 ms 192 ms www.dslreports.com [209.123.109.175]

Trace complete.

It looks like it may be a peering issue between your area's headend router, and the AT&T backbone. I would suggest contacting both comcast and AT&T in this matter. You can email AT&T at help@ip.att.net
--
You want the truth? You can't handle the truth!

Big_D's right, you need to contact Comcast/AT&T and hope they do something. Getting your friend to also complain may also help. I'd also include that tracert so they know you've done your homework.

I also forgot WELCOME TO BBR!!!!
[text was edited by author 2003-08-07 23:17:03]

reply to VacantLot
Yep, I had this problem here in Buffalo Grove a month or so ago and as of this last weekend I am now having it again. Always 4th hop for me. It ping starts getting worse at around 8 pm and is usually over 200 ms by 9 pm. This continues through midnight often. I also used to get some packet loss as well. I have placed numerous calls to comcast and have hosted enough truck rolling techs to know them by name : \ I believe we need enough complaints to warrant an upgrade on their end.

My line quality tests are fine.

Here is one of the more favorable tracerts showing a similar trend - 1 hour ago the 4th hop was ~250 ms:

1 10 ms 18 ms 9 ms xxxxxx
2 23 ms 21 ms 22 ms 12.244.106.65
3 56 ms 10 ms 10 ms 12.244.68.57
4 155 ms 225 ms 146 ms 12.244.72.226
5 157 ms 182 ms 164 ms gbr1-p50.cgcil.ip.att.net 12.123.5.74]
6 162 ms 154 ms 155 ms tbr1-p013502.cgcil.ip.att.net [12.122.11.33]
7 166 ms 168 ms 187 ms tbr1-p013601.n54ny.ip.att.net [12.122.10.57]
8 174 ms 179 ms 179 ms tbr1-cl8.phlpa.ip.att.net [12.122.2.18]
9 209 ms 199 ms 175 ms gbr2-p10.phlpa.ip.att.net [12.122.12.102]
10 186 ms 170 ms 210 ms gar1-p370.phlpa.ip.att.net [12.123.137.25]
11 186 ms 217 ms 235 ms 12.118.191.18
12 * * * Request timed out.
13 195 ms 189 ms 195 ms www7.tomshardware.com [209.68.60.7]

Please keep us up to date on your progress with this problem.
[text was edited by author 2003-08-07 23:51:19]

reply to VacantLot
ASE is not reliable or accurate for me for gaming (BF 1942: Desert Combat). I show lower pings using the in game browser and after connecting, I get consistently lower ping times while playing.

reply to Nerdtalker
Just got offline with comcast support chat. Here is the transcipt.

Analyst > Please wait, while the problem is escalated to another analyst
Analyst > Auto return based on no CSR response.
Analyst > Thank you for contacting Comcast, my name is Eric. How may I help you?
ronhands > Eric i was chatting with sharon a minute ago and she had me power cycle my modem for 3 min. that is now done
ronhands > can i email you my tracert since the power cycle?
Analyst > will you post it into our chat instead
ronhands > chat is limited to only 1000 characters
Analyst > Eric_Jobes@cable.comcast.com
ronhands > I have sent it
Analyst > open a command prompt
Analyst > ping 12.244.72.242 -n 100
Analyst > when it is finished copy and paste the ending ping statistics
ronhands > do you really want all of this?
Analyst > not all
Analyst > just the end
ronhands > it will be done in a min
Analyst > OK
ronhands > is this going to ping that address 100 times?
Analyst > yes
Analyst > I'm going to escalate your issue to our NOC (Network Operations Center). Mainly I need to see the consitency of the trip times and how hight they spike. Sending 100 packets helps see if exactly what the router is doing
ronhands > ok, sent
ronhands > I've seen this as high as 500
Analyst > Good to know. I didn't get this last email.
ronhands > btw, this started happening about a week or so ago
Analyst > is it always the same router 12.244.72.242?
ronhands > i don't know what you mean?
ronhands > have you go the last email?
Analyst > when you perform tracert like the one you sent me. At 12.244.72.242 your trip times gor from about 15 ms to 170 ms
Analyst > no
Analyst > still have not got it
ronhands > Yes, that sound right
ronhands > sounds
ronhands > my last email was sent @ 10:51pm central time
ronhands > you should have it
Analyst > our work firewall sometimes delays mail which is why I origionally wanted you to post in the chat. Will you please post the ping stats (should be under 1000 characters) into the chat
ronhands > the reason i'm wanting this fixed is because i game a lot and these high pings suck.
ronhands > Reply from 12.244.72.242: bytes=32 time=158ms TTL=247 Reply from 12.244.72.242: bytes=32 time=170ms TTL=247 Reply from 12.244.72.242: bytes=32 time=160ms TTL=247 Reply from 12.244.72.242: bytes=32 time=167ms TTL=247 Reply from 12.244.72.242: bytes=32 time=159ms TTL=247 Reply from 12.244.72.242: bytes=32 time=165ms TTL=247 Reply from 12.244.72.242: bytes=32 time=161ms TTL=247 Ping statistics for 12.244.72.242: Packets: Sent = 100, Received = 99, Lost = 1 (1% loss), Approximate round trip times in milli-seconds: Minimum = 156ms, Maximum = 215ms, Average = 179ms
Analyst > thank you
ronhands > this is the last few lines
Analyst > that is what I needed. I will escalate your issue to our NOC (Network Operations Center)so they can reaserch why that network equipment is slowing you down. I'll have a ticket number for you in a moment if you want to wait for it
ronhands > yes, thanks
ronhands > btw, when is comcast rolling out the 3Mb/s service?
Analyst > Its out in Denver and Seattle now. We are slowing rolling it out to the rest of the country. I do not have an exact time schedule for different areas, but it will probably be done almost everywhere by the end of April 2004
ronhands > very nice
Analyst > Thank you for your patience, this ticket is going to take me a hwile (datebae moving slow) want me to email it when I have it?
ronhands > sure, ronhands@comcast.net
Analyst > You should have my email within 15 minutes
Analyst > in the mean time, is there anything else I can help you with?
ronhands > thanks, good night
Analyst > Thank you for choosing Comcast.

They said I have been handed over to NOC, we will see if it works.

rshands

btw, did you read where he stated 3Mb/s to be fully rolled out by April 2004? we will see about that too.

Not sure about the 3mb stuff, but it sounds like you got one of the few tech's that knows what he is doing. A lot of times the response will be, oh ya pings around 200 are fine. If he is sending it to the NOC, you may actually get some resolution soon. Definately one of the best conversations with online support I've read about.
--
You want the truth? You can't handle the truth!

reply to VacantLot
Same problem here in Schaumburg. I spoke with a tech who said they are aware of the problem but don't know when it will get fixed...god I hate ComCrap

Here are my results from 8/6--->

C:\Documents and Settings\Richard>tracert www.yahoo.com

Tracing route to www.yahoo.akadns.net [66.218.71.94]
over a maximum of 30 hops:

1 14 ms 15 ms 15 ms 12-248-52-1.client.attbi.com [12.248.52.1]
2 16 ms 12 ms 10 ms 12.244.104.97
3 254 ms 159 ms 156 ms 12.244.74.226
4 562 ms 157 ms 151 ms gbr1-p50.cgcil.ip.att.net [12.123.5.74]
5 367 ms 161 ms 155 ms tbr1-p013502.cgcil.ip.att.net [12.122.11.33]
6 152 ms 155 ms 153 ms ggr2-p300.cgcil.ip.att.net [12.123.6.33]
7 145 ms 146 ms 148 ms so-1-1-0.edge1.Chicago1.Level3.net [209.0.227.77
]
8 145 ms 144 ms 147 ms so-2-1-0.bbr1.Chicago1.level3.net [209.244.8.9]

9 196 ms 196 ms 200 ms so-1-0-0.mp1.SanJose1.level3.net [209.247.9.118]

10 198 ms 200 ms 203 ms gige9-1.ipcolo3.SanJose1.Level3.net [64.159.2.73
]
11 198 ms 198 ms 200 ms unknown.Level3.net [64.152.69.30]
12 243 ms 212 ms 204 ms w15.www.scd.yahoo.com [66.218.71.94]

Trace complete.

C:\Documents and Settings\Richard>ping www.yahoo.com

Pinging www.yahoo.akadns.net [66.218.71.87] with 32 bytes of data:

Reply from 66.218.71.87: bytes=32 time=288ms TTL=53
Reply from 66.218.71.87: bytes=32 time=211ms TTL=53
Reply from 66.218.71.87: bytes=32 time=195ms TTL=53
Reply from 66.218.71.87: bytes=32 time=209ms TTL=53

Ping statistics for 66.218.71.87:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 195ms, Maximum = 288ms, Average = 225ms

reply to VacantLot
Its been a while since I've seen a tech that is that helpful. They should hire more like that!

reply to VacantLot
I noticed and started a thread also
»Drop in Quality of Connection
It seems a little better now but there are still periods of badness.

Tracing route to www.broadbandreports.com [209.123.109.175]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 10 ms 10 ms 22 ms 10.164.52.1
3 9 ms 9 ms 9 ms 12.244.105.129
4 11 ms 9 ms 9 ms 12.244.68.17
5 10 ms 9 ms 9 ms 12.244.68.13
6 10 ms 10 ms 15 ms 12.244.68.9
7 13 ms 11 ms 11 ms 12.244.72.238
8 13 ms 11 ms 12 ms 12.123.6.2
9 12 ms 12 ms 18 ms 12.122.11.41
10 31 ms 49 ms 31 ms 12.122.10.57
11 32 ms 31 ms 33 ms 12.123.214.181
12 32 ms 32 ms 31 ms 12.119.140.30
13 32 ms 31 ms 31 ms 209.123.11.78
14 36 ms 32 ms 32 ms 209.123.11.233
15 34 ms 33 ms 34 ms 64.21.102.2
16 34 ms 33 ms 33 ms 209.123.109.175

Trace complete.

reply to VacantLot
For what it's worth, we were having similar issues here in dekalb last sunday.

First 3 hops great, then 4+ were 300ms + range.

Problem got cleared up by monday morning.

However, a friend in morton grove still has the same issue daily from about 7/8pm through midnight.

At midnight it is as though a switch is flipped and things return to normal.

He says thats been the case for last several months actually.

As was discussed in other posts, unless you really know what you're looking for, 90% of the HSD users (probably more), don't perceive a problem, and why should comcast spend resources to fix an issue that very few are complaining about.

So if you're reading this thread, and have some time to spare, give comcast a call and register a complaint. THe more get they, the more they may be inclined to perform the necessary repairs.

Been having it in Crest Hill for a few weeks or so as well. Called Comcast on Wednesday night as it went into the 300 range. And as it goes up for only about 2 min by the time I got a tech on the line they could not see a problem. There was no know issue or so I was told, though a ticket was opened at the time.

On Saturday we had them in the 2k range for about 2 min. It seems they go up for a short time then things go back to normal.

Unfortunately all traces are on the home PC expect this one I had posted in a different forum.

Target Name: www.attbi.com
IP: 63.240.76.8
Date/Time: 7/18/2003 10:59:49 PM

1 40 ms 10 ms 9 ms [10.163.216.1]
2 15 ms 9 ms 9 ms [12.244.106.129]
3 14 ms 10 ms 9 ms [12.244.68.26]
4 10 ms 10 ms 12 ms [12.244.68.30]
5 487 ms 493 ms 494 ms [12.244.72.242]
6 487 ms 493 ms 496 ms gbr2-p100.cgcil.ip.att.net [12.123.5.78]
7 487 ms 495 ms 496 ms tbr2-p013602.cgcil.ip.att.net [12.122.11.53]
8 494 ms 501 ms 505 ms tbr2-p012501.sl9mo.ip.att.net [12.122.10.10]
9 493 ms 501 ms 503 ms tbr1-p012401.sl9mo.ip.att.net [12.122.9.141]
10 512 ms 515 ms 519 ms tbr1-cl4.wswdc.ip.att.net [12.122.10.29]
11 512 ms 515 ms 519 ms tbr2-p013601.wswdc.ip.att.net [12.122.9.150]
12 517 ms 523 ms 523 ms tbr1-p012201.n54ny.ip.att.net [12.122.10.17]
13 516 ms 522 ms 522 ms gbr2-p20.n54ny.ip.att.net [12.122.11.22]
14 518 ms 520 ms 521 ms gar1-p370.n54ny.ip.att.net [12.123.1.133]
15 551 ms 520 ms 522 ms mdf1-gsr12-2-pos-7-0.nyc3.attens.net [12.122.255.162]
16 527 ms 521 ms 518 ms [63.240.64.102]
17 519 ms 519 ms 522 ms [192.168.201.6]
18 517 ms 521 ms 525 ms www.attbi.com [63.240.76.8]

reply to VacantLot
Update, never got the email promised from Eric the comcast tech so I don't have a trouble ticket number and still have the problem. I'll keep you posted.

rshands

reply to VacantLot
please do rshands, I will continue to work them as well as this is not a new thing - but it is deeply troublesome for many applications, gaming aside. After all, who wants to pay $42.95/mo to wait 5 seconds for a web page to load. And that's not even throwing in Packet Loss.

Jsolo1: Your description about "a switch being flipped" is right on the $$$ for me, I encounter the same thing many nights.

Keep the posts coming Chicago!!!

C:\>tracert www.comcast.net

Tracing route to www.comcast.net [63.240.76.72]
over a maximum of 30 hops:

1 13 ms 14 ms 18 ms 12-211-128-1.client.attbi.com [12.211.128.1]
2 21 ms 19 ms 15 ms 12.244.108.81
3 15 ms 13 ms 16 ms 12.244.68.30
4 39 ms 41 ms 40 ms 12.244.72.246
5 36 ms 35 ms 35 ms gbr5-p90.cgcil.ip.att.net [12.123.6.2]
6 44 ms 42 ms 42 ms tbr1-p013501.cgcil.ip.att.net [12.122.11.41]
7 57 ms 57 ms 58 ms tbr1-p012301.n54ny.ip.att.net [12.122.10.1]
8 65 ms 62 ms 62 ms gbr1-p10.n54ny.ip.att.net [12.122.11.2]
9 64 ms 62 ms 65 ms gar1-p360.n54ny.ip.att.net [12.123.1.129]
10 67 ms 69 ms 70 ms mdf1-gsr12-2-pos-7-0.nyc3.attens.net [12.122.255
.162]
11 68 ms 61 ms 61 ms mdf2-bi8k-2-ve-25.nyc3.attens.net [63.240.64.98]

12 56 ms 54 ms 53 ms 192.168.201.12
13 64 ms 58 ms 61 ms www.comcast.net [63.240.76.72]

Trace complete.

C:\>

looks like its fixed. gaming is back to normal.

rshands

reply to VacantLot
Don't be so sure...is that trace from the evening (after 9pm)?

Here's a tracert at 10 pm here in buffalo grove:

1 8 ms 8 ms 10 ms xxxxxxx
2 7 ms 10 ms 38 ms 12.244.106.65
3 8 ms 12 ms 7 ms 12.244.68.57
4 158 ms 136 ms 120 ms 12.244.72.226
5 128 ms 121 ms 121 ms gbr1-p50.cgcil.ip.att.net [12.123.5.74]
6 118 ms 121 ms 184 ms tbr1-p013502.cgcil.ip.att.net [12.122.11.33]
7 156 ms 144 ms 152 ms tbr1-p013601.n54ny.ip.att.net [12.122.10.57]
8 152 ms 155 ms 161 ms tbr1-cl8.phlpa.ip.att.net [12.122.2.18]
9 156 ms 156 ms 192 ms gbr2-p10.phlpa.ip.att.net [12.122.12.102]
10 208 ms 138 ms 143 ms gar1-p370.phlpa.ip.att.net [12.123.137.25]
11 158 ms 156 ms 165 ms 12.118.191.18
12 * * * Request timed out.
13 145 ms 146 ms 144 ms www7.tomshardware.com [209.68.60.7]

Tracing route to pingplotter.com [216.92.151.75]
over a maximum of 30 hops:

1 21 ms 47 ms 7 ms xxxxxxxx
2 9 ms 8 ms 37 ms 12.244.106.65
3 9 ms 14 ms 39 ms 12.244.68.57
4 125 ms 119 ms 126 ms 12.244.72.226
5 122 ms 130 ms 130 ms gbr2-p100.cgcil.ip.att.net [12.123.5.78]
6 126 ms 122 ms 136 ms tbr1-p013602.cgcil.ip.att.net [12.122.11.37]
7 144 ms 196 ms 185 ms tbr1-p012301.n54ny.ip.att.net [12.122.10.1]
8 162 ms 138 ms 160 ms tbr1-cl8.phlpa.ip.att.net [12.122.2.18]
9 135 ms 156 ms 147 ms gbr1-p10.phlpa.ip.att.net [12.122.12.98]
10 138 ms 139 ms 141 ms gar1-p360.phlpa.ip.att.net [12.123.137.21]
11 164 ms 141 ms 138 ms 12.118.191.18
12 * * * Request timed out.
13 178 ms 158 ms 191 ms pingplotter.com [216.92.151.75]

Trace complete.

C:\Documents and Settings\MC^2>tracert google.com

Tracing route to google.com [216.239.51.100]
over a maximum of 30 hops:

1 26 ms 10 ms 11 ms xxxxxxxx
2 15 ms 7 ms 24 ms 12.244.106.65
3 8 ms 10 ms 8 ms 12.244.68.57
4 148 ms 145 ms 155 ms 12.244.72.230
5 156 ms 195 ms 153 ms gbr6-p90.cgcil.ip.att.net [12.123.6.6]
6 165 ms 180 ms 146 ms tbr1-p013601.cgcil.ip.att.net [12.122.11.45]
7 132 ms 196 ms 137 ms ggr2-p300.cgcil.ip.att.net [12.123.6.33]
8 131 ms 191 ms 140 ms att-gw.sf.prserv.net [192.205.32.194]
9 160 ms 155 ms 147 ms p16-1-0-0.r01.chcgil06.us.bb.verio.net [129.250.
5.77]
10 139 ms 166 ms 165 ms p16-7-0-0.r01.chcgil01.us.bb.verio.net [129.250.
5.71]
11 181 ms 174 ms 174 ms p16-1-0-1.r20.asbnva01.us.bb.verio.net [129.250.
5.103]
12 206 ms 161 ms 173 ms p16-7-0-0.r02.asbnva01.us.bb.verio.net [129.250.
2.83]
13 165 ms 197 ms 174 ms ge-1-1.a00.asbnva01.us.ra.verio.net [129.250.26.
97]
14 184 ms 202 ms 177 ms ge-3-2.a00.asbnva01.us.ce.verio.net [168.143.105
.58]
15 175 ms 178 ms 177 ms 216.239.47.102
16 205 ms 187 ms 192 ms www.google.com [216.239.51.100]

reply to VacantLot
I have been having the same problems here in the Northern Suburbs (Winnetka); however, it is not always limited to the nighttime hours. It seems to happen intermittently throughout the day. However, at night I average about 186ms, and it is at its worst! Speed tests have also show that my connection is only at 50/35 at its "peak" hours.

Hope this is resolved soon!

wow back worse then before now

Tracing route to www.comcast.net [63.240.76.72]
over a maximum of 30 hops:

1 31 ms 16 ms 16 ms 12-208-64-1.client.attbi.com [12.208.64.1]
2 * * 813 ms 12-208-64-1.client.attbi.com [12.208.64.1]
3 781 ms 16 ms 16 ms 12.244.72.226
4 656 ms 16 ms 16 ms gbr2-p100.cgcil.ip.att.net [12.123.5.78]
5 672 ms 31 ms 16 ms tbr1-p013602.cgcil.ip.att.net [12.122.11.37]
6 * * * Request timed out.
7 * * 1016 ms gbr1-p10.n54ny.ip.att.net [12.122.11.2]
8 * * * Request timed out.
9 922 ms 32 ms 46 ms mdf1-gsr12-2-pos-7-0.nyc3.attens.net [12.122.255
.162]
10 891 ms 47 ms 31 ms sccsbix11-1-6.attbi.com [63.240.64.38]
11 859 ms 47 ms 32 ms 192.168.201.12
12 * * 829 ms www.comcast.net [63.240.76.72]

Trace complete.