Comcast user connection issues

[Chapel]

I tried calling and requested tier 2 help, the fella didn't transfer me but continued to try and "fix" the issue. Comcast is so helpful!
So to make a long story short....

As far as I'm concerned the dude at Comcast can eat a fat wang (or other creative explicatives you can think of).

I called em up to report the issues, he tried some stuff, and then he rebooted my cable modem remotely which disconnected our call. He calls back, tries a few more things and then when he couldn't determine the problem....

"Sir? Are you there sir? Awww man....did you put me on hold?"
I responded no, that I was still there and can hear him.
"Can you hear me sir? You didn't put me on hold did you?"
I responded no, I can hear him, and that he's not on hold.
"Due to unresponsiveness I must terminate this call, if you continue to have issues, call 1-800-Comcast"

I was a raging, pissed off, mushroom cloud laying (more explicatives here that I won't mention) at this point and decided I'd better do something else to avoid saying something to Comcast that i'd regret. I can't believe he pretended I put him on hold to avoid the issue. He had my number, and he'd called back once already, he totally could have called again.

I plan to contact them today and explain my issue and circumstance.

[fudgums]

<--- sent an e-mail to Obama this morning suggesting the creation of a Cabinet Level post: Internet Czar,

Skuzzy I hope you don't mind me mentioning your name 

  now Skuzzy will be on Obamas top 5. If you know what I mean

[oceans11]

Ok first let me explain what is happening to me

I am running comcast

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/20/2008 4:44:12 PM to 12/20/2008 4:45:42 PM

 1   *       *       *       *       *       *       *       [-]
 2   10 ms    9 ms    9 ms   10 ms    8 ms   10 ms   13 ms  [68.87.214.117]
 3    9 ms   11 ms   10 ms    9 ms   12 ms   14 ms   13 ms  po-20-ar01.eatontown.nj.panjde.comcast.net [68.86.210.82]
 4   13 ms   28 ms   14 ms   13 ms   12 ms   12 ms   17 ms  po-90-ar01.verona.nj.panjde.comcast.net [68.86.208.9]
 5   12 ms   15 ms   12 ms   14 ms   16 ms   14 ms   13 ms  pos-0-11-0-0.ar01.plainfield.nj.panjde.comcast.net [68.86.153.98]
 6   24 ms   24 ms   14 ms   14 ms   14 ms   18 ms   23 ms  pos-0-5-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.90.29]
 7   14 ms   15 ms   22 ms   14 ms   26 ms   14 ms   20 ms  xe-10-3-0.edge1.NewYork2.Level3.net [4.71.184.1]
 8   16 ms   13 ms   13 ms   15 ms   16 ms   14 ms   23 ms  ae-13-69.car3.NewYork1.Level3.net [4.68.16.5]
 9   22 ms   14 ms   15 ms  100 ms   21 ms   18 ms   48 ms  att-level3-oc192.NewYork1.Level3.net [4.68.127.150]
10   89 ms   90 ms   90 ms   89 ms  104 ms   89 ms   92 ms  tbr2.n54ny.ip.att.net [12.123.3.110]
11   89 ms   91 ms   91 ms   90 ms  179 ms   90 ms  100 ms  cr2.n54ny.ip.att.net [12.122.16.149]
12   95 ms   90 ms   89 ms   89 ms   *       97 ms   93 ms  cr2.wswdc.ip.att.net [12.122.3.38]
13   89 ms   89 ms   88 ms   88 ms   *      103 ms   93 ms  cr1.attga.ip.att.net [12.122.1.173]
14   99 ms   88 ms   90 ms   91 ms   89 ms   93 ms   89 ms  cr2.dlstx.ip.att.net [12.122.28.174]
15   89 ms   89 ms   89 ms   90 ms   88 ms   91 ms   92 ms  gar5.dlstx.ip.att.net [12.122.138.5]
16   89 ms   89 ms   90 ms   90 ms   96 ms   90 ms   92 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
17   90 ms   *       *       *       *       *       *      mdf1-bi8k-1-eth-1-4.dal1.attens.net [63.241.192.42]
18   90 ms   91 ms   90 ms   91 ms   90 ms   91 ms   90 ms  [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 7, Received = 7, Lost = 0 (0.0%)
Round Trip Times: Minimum = 90ms, Maximum = 91ms, Average = 90ms





When I log into the game the ping ratio shows - next to orange arena I only see pings next to blue or purple arena

When i do Log into the game I fly then screen starts to hiccup
I am getting about 59 -62 frame rate memory is not being hogged then video  freezes up but I hear the sound still.

I called comcast and The person I spoke to was real helpfull He explained to me it is actually a ATT issue since they use ATT as the backbone.

Does this sound like the same symptons everybody else is having or am I experiencing something different ?



Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/20/2008 5:00:27 PM to 12/20/2008 5:02:42 PM

 1   *       *       *       *       *       *       *       *       *       *       [-]
 2   15 ms    8 ms    9 ms   10 ms   10 ms   10 ms   10 ms   19 ms   26 ms   19 ms  [68.87.214.117]
 3    9 ms    9 ms   10 ms   21 ms   10 ms   11 ms   10 ms    9 ms    9 ms    9 ms  po-20-ar01.eatontown.nj.panjde.comcast.net [68.86.210.82]
 4   13 ms   13 ms   17 ms   12 ms   13 ms   12 ms   12 ms   14 ms   11 ms   13 ms  po-90-ar01.verona.nj.panjde.comcast.net [68.86.208.9]
 5   24 ms   14 ms   13 ms   13 ms   13 ms   13 ms   13 ms   13 ms   12 ms   14 ms  pos-0-11-0-0.ar01.plainfield.nj.panjde.comcast.net [68.86.153.98]
 6   14 ms   14 ms   15 ms   15 ms   23 ms   15 ms   20 ms   16 ms   14 ms   26 ms  pos-0-5-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.90.29]
 7   16 ms   16 ms   17 ms   14 ms   13 ms   23 ms   14 ms   15 ms   15 ms   14 ms  xe-10-3-0.edge1.NewYork2.Level3.net [4.71.184.1]
 8   16 ms   16 ms   14 ms   15 ms  133 ms   14 ms   24 ms   50 ms   14 ms   14 ms  ae-13-69.car3.NewYork1.Level3.net [4.68.16.5]
 9   14 ms   *       16 ms   16 ms   16 ms   17 ms   *       *       15 ms   15 ms  att-level3-oc192.NewYork1.Level3.net [4.68.127.150]
10   89 ms   90 ms   90 ms   99 ms   97 ms   89 ms   89 ms   89 ms   91 ms   89 ms  tbr2.n54ny.ip.att.net [12.123.3.110]
11   89 ms   91 ms   91 ms   90 ms   90 ms  119 ms   92 ms   90 ms   91 ms   90 ms  cr2.n54ny.ip.att.net [12.122.16.149]
12   91 ms   98 ms   91 ms   91 ms   92 ms  101 ms   91 ms   90 ms   99 ms   90 ms  cr2.wswdc.ip.att.net [12.122.3.38]
13   90 ms   90 ms   90 ms   89 ms   89 ms   88 ms   90 ms   89 ms   90 ms  110 ms  cr1.attga.ip.att.net [12.122.1.173]
14   91 ms   97 ms   90 ms   97 ms   94 ms   92 ms   90 ms   90 ms   90 ms   89 ms  cr2.dlstx.ip.att.net [12.122.28.174]
15   88 ms   89 ms   90 ms   99 ms   88 ms   90 ms   *      111 ms   89 ms   87 ms  gar5.dlstx.ip.att.net [12.122.138.5]
16   90 ms  100 ms   89 ms   89 ms   90 ms   90 ms   89 ms   91 ms   89 ms   92 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
17   *       *       *       *       *       *       *       *       *       *      mdf1-bi8k-1-eth-1-4.dal1.attens.net [63.241.192.42]
18   90 ms   90 ms   92 ms   89 ms   92 ms   90 ms  103 ms   91 ms   90 ms   92 ms  [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 89ms, Maximum = 103ms, Average = 91ms

[Sincraft]

I tried calling and requested tier 2 help, the fella didn't transfer me but continued to try and "fix" the issue. Comcast is so helpful!
So to make a long story short....

As far as I'm concerned the dude at Comcast can eat a fat wang (or other creative explicatives you can think of).

I called em up to report the issues, he tried some stuff, and then he rebooted my cable modem remotely which disconnected our call. He calls back, tries a few more things and then when he couldn't determine the problem....

"Sir? Are you there sir? Awww man....did you put me on hold?"
I responded no, that I was still there and can hear him.
"Can you hear me sir? You didn't put me on hold did you?"
I responded no, I can hear him, and that he's not on hold.
"Due to unresponsiveness I must terminate this call, if you continue to have issues, call 1-800-Comcast"

I was a raging, pissed off, mushroom cloud laying (more explicatives here that I won't mention) at this point and decided I'd better do something else to avoid saying something to Comcast that i'd regret. I can't believe he pretended I put him on hold to avoid the issue. He had my number, and he'd called back once already, he totally could have called again.

I plan to contact them today and explain my issue and circumstance.

The only thing that guy you spoke to knows about network is how to spell it.  If you want to listen to lip service and ineptitude, call comcast. 

[ink]

well I am also having issues, every time I log in it lets me play maybe 5 min, then it reboots my computer, I just went in to offline and played rangers winter breakout mission, no problems!!

I still cant think of why it being online would reboot my system?

gonna go try again.

[OOZ662]

Still haven't discoed, but I think someone at AT&T hates me. This one actually looks much nicer than the one I ran before. Skipped the first three hops as they're in-house.

Target Name: HTC Main Arena
         IP: 206.16.60.39
  Date/Time: 12/20/2008 9:09:31 PM to 12/20/2008 9:24:30 PM

Hop Sent Err  PL% Min  Max Avg  Host Name / [IP]
 4   900   9  1.0   7   87  10  te-5-1-ur01.ferndale.wa.seattle.comcast.net [68.86.96.113]
 5   900   3  0.3   7   31  10  te-5-3-ur02.ferndale.wa.seattle.comcast.net [68.86.96.110]
 6   900   1  0.1  11   34  13  te-7-1-ar02.seattle.wa.seattle.comcast.net [68.86.96.105]
 7   900   0  0.0  11   36  13  te-0-4-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.90.209]
 8   900  21  2.3  11  376  28  te-3-3.car1.Seattle1.Level3.net [4.79.104.109]
 9   900  15  1.7  11   96  14  ge-2-0-0-52.gar1.Seattle1.Level3.net [4.68.105.41]
10   459  21  4.6  30  143  34  [192.205.33.145]
11   900  23  2.6  74  138  77  tbr1.st6wa.ip.att.net [12.127.6.169]
12   900  77  8.6  74  108  77  cr1.st6wa.ip.att.net [12.122.23.153]
13   900  74  8.2  74   94  77  cr2.sffca.ip.att.net [12.122.31.194]
14   900  50  5.6  74  104  77  cr2.la2ca.ip.att.net [12.122.31.133]
15   900  52  5.8  74  111  77  cr2.dlstx.ip.att.net [12.122.28.177]
16   900  99 11.0  74  194  78  gar5.dlstx.ip.att.net [12.122.138.5]
17   900  79  8.8  75   94  77  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
18   900  99 11.0  75 2745  98  mdf1-bi8k-2-eth-2-1.dal1.attens.net [63.241.192.198]
19   900   0  0.0  74   97  77  [206.16.60.39]

[drdeathx]

I tried calling and requested tier 2 help, the fella didn't transfer me but continued to try and "fix" the issue. Comcast is so helpful!
So to make a long story short....

As far as I'm concerned the dude at Comcast can eat a fat wang (or other creative explicatives you can think of).

I called em up to report the issues, he tried some stuff, and then he rebooted my cable modem remotely which disconnected our call. He calls back, tries a few more things and then when he couldn't determine the problem....

"Sir? Are you there sir? Awww man....did you put me on hold?"
I responded no, that I was still there and can hear him.
"Can you hear me sir? You didn't put me on hold did you?"
I responded no, I can hear him, and that he's not on hold.
"Due to unresponsiveness I must terminate this call, if you continue to have issues, call 1-800-Comcast"

I was a raging, pissed off, mushroom cloud laying (more explicatives here that I won't mention) at this point and decided I'd better do something else to avoid saying something to Comcast that i'd regret. I can't believe he pretended I put him on hold to avoid the issue. He had my number, and he'd called back once already, he totally could have called again.

I plan to contact them today and explain my issue and circumstance.

Comcast customer service is awesome. Never have a long wait for a CSR. My bandwith is superior close to T3(3 meg d/l, 1.5 meg upload). Try another service, you will probably be back to Comcast quickly.

[Delirium]

Skuzzy, do you want pingplots on everyone with Comcast or just those with problems?

[Skuzzy]

The Ping Plots were for the benefit of Comcast and AT&T so they could get a sense of how wide spread the problem was.

Again, the problems between Comcast and Level3 are not going to be fixed.  They are there by design.  Well, lack of design.  The only thing that is going to help that situation is less network traffic.

[Hawk78th]

 From Burlington VT...

 I get hiccups... then then random lock up.. Not consistant though.

Looks like the ATT side of things for me... yes...?


 and this is Sunday Mornin'n Ping

 Target Name:KBTV--HTC
         IP: 206.16.60.38
  Date/Time: 12/21/2008 10:59:27 AM

 1    6 ms    8 ms    8 ms    7 ms  c-75-69-32-1.hsd1.vt.comcast.net [75.69.32.1]
 2    7 ms    8 ms    7 ms    6 ms  ge-2-3-ur01.williston.vt.boston.comcast.net [68.86.236.25]
 3    8 ms    8 ms    8 ms    9 ms  te-9-1-ur01.rutland.vt.boston.comcast.net [68.87.146.234]
 4    8 ms    9 ms   10 ms    9 ms  te-8-1-ur01.bennington.vt.boston.comcast.net [68.87.146.238]
 5   11 ms   13 ms   14 ms   11 ms  te-8-4-ar01.springfield.ma.boston.comcast.net [68.87.147.18]
 6   14 ms   13 ms   13 ms   12 ms  po-11-ar01.chartford.ct.hartford.comcast.net [68.87.146.26]
 7   17 ms   15 ms   16 ms   16 ms  te-0-4-0-1-cr01.newyork.ny.ibone.comcast.net [68.86.90.61]
 8   72 ms   44 ms   13 ms   15 ms  xe-10-1-0.edge1.NewYork2.Level3.net [4.78.169.45]
 9   15 ms   18 ms   16 ms  N/A     ae-23-79.car3.NewYork1.Level3.net [4.68.16.69]
10   53 ms   15 ms   16 ms   15 ms  [192.205.33.93]
11  339 ms  337 ms  335 ms  N/A     tbr2.n54ny.ip.att.net [12.123.0.94]
12  338 ms  337 ms  337 ms  N/A     cr2.n54ny.ip.att.net [12.122.16.213]
13  339 ms   *      336 ms  N/A     cr2.wswdc.ip.att.net [12.122.3.38]
14  N/A     337 ms  336 ms  N/A     cr1.attga.ip.att.net [12.122.1.173]
15  339 ms  337 ms  337 ms  N/A     cr2.dlstx.ip.att.net [12.122.28.174]
16  338 ms  336 ms  334 ms  N/A     gar5.dlstx.ip.att.net [12.122.138.5]
17  338 ms  373 ms  348 ms  N/A     mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
18  N/A     337 ms  337 ms  N/A     mdf1-bi8k-1-eth-1-3.dal1.attens.net [63.241.192.206]
19  337 ms   *      337 ms  N/A     [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 3, Received = 2, Lost = 1 (33.3%)
Round Trip Times: Minimum = 337ms, Maximum = 337ms, Average = 337ms

[BaldEagl]

Everything was working good last night.

Thanks Skuzzy.  You might want to take the MOTD down.

[dentin]

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/21/2008 10:37:41 AM to 12/21/2008 10:39:56 AM

 1    8 ms    7 ms   11 ms    7 ms    8 ms    9 ms    9 ms    9 ms    8 ms    8 ms  c-3-0-ubr05.westfield.ma.boston.comcast.net [73.160.232.1]
 2    8 ms    9 ms    9 ms   11 ms    9 ms    7 ms    9 ms    8 ms   19 ms    9 ms  [68.85.186.17]
 3   13 ms   14 ms   11 ms   11 ms   14 ms   12 ms   13 ms   11 ms   12 ms   17 ms  te-8-2-ar01.needham.ma.boston.comcast.net [68.87.146.198]
 4   16 ms   16 ms   16 ms   16 ms   15 ms   15 ms   15 ms   16 ms   16 ms   15 ms  [68.85.162.70]
 5   19 ms   19 ms   19 ms   18 ms   19 ms   18 ms   20 ms   17 ms   18 ms   17 ms  te-0-4-0-1-cr01.newyork.ny.ibone.comcast.net [68.86.90.61]
 6   26 ms   19 ms   18 ms   18 ms   17 ms   18 ms   18 ms   18 ms   18 ms   18 ms  xe-11-3-0.edge1.NewYork2.Level3.net [4.71.186.5]
 7   20 ms   19 ms   19 ms   18 ms   19 ms   18 ms  199 ms   17 ms   17 ms   19 ms  ae-23-79.car3.NewYork1.Level3.net [4.68.16.69]
 8   19 ms   18 ms   18 ms   19 ms   91 ms   19 ms   19 ms   20 ms   18 ms   19 ms  att-level3-oc192.NewYork1.Level3.net [4.68.127.150]
 9  341 ms  341 ms  341 ms  341 ms  342 ms  339 ms  341 ms  341 ms  340 ms  344 ms  tbr2.n54ny.ip.att.net [12.123.3.61]
10  339 ms  340 ms  346 ms   *      340 ms  342 ms  340 ms  340 ms  339 ms  N/A     cr2.n54ny.ip.att.net [12.122.16.141]
11  339 ms  338 ms  339 ms  338 ms  345 ms  342 ms  340 ms  340 ms  340 ms  N/A     cr2.wswdc.ip.att.net [12.122.3.38]
12  340 ms   *      339 ms  339 ms  339 ms  342 ms  338 ms  341 ms  340 ms  N/A     cr1.attga.ip.att.net [12.122.1.173]
13  340 ms  343 ms  343 ms  340 ms  341 ms  340 ms  341 ms  341 ms  342 ms  N/A     cr2.dlstx.ip.att.net [12.122.28.174]
14  340 ms  343 ms  338 ms  338 ms  338 ms   *      341 ms  342 ms  340 ms  N/A     gar5.dlstx.ip.att.net [12.122.138.5]
15  341 ms  341 ms  341 ms  341 ms  345 ms   *      341 ms  339 ms   *      N/A     mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
16  340 ms  345 ms  341 ms  343 ms  341 ms  343 ms  341 ms  341 ms  340 ms  N/A     mdf1-bi8k-2-eth-2-1.dal1.attens.net [63.241.192.198]
17   *      339 ms  338 ms  338 ms   *      340 ms  340 ms  341 ms   *      N/A     [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 10, Received = 7, Lost = 3 (30.0%)
Round Trip Times: Minimum = 338ms, Maximum = 342ms, Average = 339ms

[Skuzzy]

No Hawk, your problems are in the Level3, as are yours dentin.

[HighGTrn]

Well, everything was going fine for a while until this morning.  Got on early (6 AM) EST and things were good.  By 0900, latency was so bad, I was avg 330 mps.  Its like that now at 1130. 

[oceans11]

Same thing here

Seems we must be in the same area
Thi sis getting pathetic

As soon as FIOS is available I am switching

Had it in my other town

Makes cable look like a welfare case