Aces High Bulletin Board

Help and Support Forums => Technical Support => Topic started by: BaldEagl on December 19, 2008, 01:26:31 PM

Title: Comcast user connection issues
Post by: BaldEagl on December 19, 2008, 01:26:31 PM
I installed the ie 7 patch today.  Now I get lost UDP every 15 minutes or so.  After I do I have to re-boot to get back into the game or even to get to this web-site.

Any ideas?

OK... now I didn't have to re-boot this time.  I typed the above from my laptop and without re-booting I can gt here and to the game when I came back and tried again.

Do you guys just not want people playing today?
Title: Connection Issues Last Five Days
Post by: Paladin3 on December 19, 2008, 02:02:56 PM
Well, for the first time ever I have had a few stutters, nothing serious, but it is to me sense I have never had such a problem. This game is always smooth as silk. Now, sense the At&T work was done... Well today I can't fly. I get on, I get switched to UDP and then I disco, and can't get back in for awhile. Anyone else having this? I talked to a few folks in the MA and they said they were and that it was new... Any help would be appriciated.
Title: Re: Connection Issues Last Five Days
Post by: Skuzzy on December 19, 2008, 02:11:37 PM
Actually, the work done ended up being in a different part of the colo facility and had no effect on us.

That said, it does not surprise you are having problems.  Try running a Ping Plot to 206.16.60.38.  My guess is you will see an amount of packet loss at the gateway between Comcast and Level3.

It is the holidays, and Internet traffic is spiking all over the U.S.  Comcast/RR/(you cable company) had already gone with an ISP who has an oversold network, so it is going to get worse during these times of the year.

But, I am speculating.  Try running the Ping Plot for a few minutes and see what is happening.
Title: Re: Connection Issues Last Five Days
Post by: Paladin3 on December 19, 2008, 02:27:30 PM
Thanks for the quick look Skuzzy. First off, I looked at the net in game and never saw a problem... I downloaded and ran ping plot... So far nothing stands out. Bear in mind I'm not sure what I am looking for but everything is in the green while I am sitting here  :lol I attempted the reboot and all the other things one normally tries (even tried kicking it once) and got a nice kill and discoed. Anyone have anything specific I should look for on ping plot? Or is there another issue I should look at in addition to this one?
Title: Re: Connection Issues Last Five Days
Post by: Paladin3 on December 19, 2008, 02:29:59 PM
Just saw how I can save it, so I'll try to do that as well. What length of time is preferred for diagnosis?
Title: Re: Connection Issues Last Five Days
Post by: Skuzzy on December 19, 2008, 02:36:23 PM
Between 3 and 5 minutes should be sufficient.  It should be done immediately after a disco from the arena.
Title: Re: Connection Issues Last Five Days
Post by: Paladin3 on December 19, 2008, 02:36:52 PM
Roger that sir. Much appriciated, and I have to say, great response time.  :rock
Title: Re: Connection Issues Last Five Days
Post by: Paladin3 on December 19, 2008, 02:46:10 PM
Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/19/2008 3:42:31 PM to 12/19/2008 3:44:46 PM

 1    7 ms    5 ms    7 ms    5 ms    6 ms    7 ms    5 ms    7 ms    5 ms    5 ms  c-76-26-64-1.hsd1.wv.comcast.net [76.26.64.1]
 2    6 ms    4 ms    6 ms    7 ms    5 ms    6 ms    4 ms    6 ms    4 ms    4 ms  ge-3-1-ur01.huntington.wv.hntngton.comcast.net [68.85.214.133]
 3    6 ms    6 ms    7 ms    4 ms    5 ms    6 ms    6 ms    4 ms    5 ms    5 ms  te-3-3-ar01.huntington.wv.hntngton.comcast.net [68.85.214.9]
 4   14 ms   13 ms   13 ms   13 ms   14 ms   14 ms   12 ms   12 ms   13 ms   13 ms  pos-4-1-ar01.pittsburgh.pa.pitt.comcast.net [68.86.100.105]
 5   14 ms   37 ms   13 ms   14 ms   13 ms   15 ms   12 ms   14 ms   13 ms   12 ms  te-3-4-ar01.pittsburgh.pa.pitt.comcast.net [68.86.100.85]
 6   18 ms   16 ms   17 ms   17 ms   18 ms   18 ms   16 ms   18 ms   17 ms   16 ms  te-0-4-0-4-cr01.cleveland.oh.ibone.comcast.net [68.86.90.97]
 7   24 ms   22 ms   23 ms   29 ms   23 ms   24 ms   22 ms   24 ms   23 ms   23 ms  pos-0-6-0-0-cr01.mclean.va.ibone.comcast.net [68.86.85.41]
 8   23 ms   22 ms   24 ms   22 ms   23 ms   23 ms   21 ms   22 ms   69 ms   24 ms  ge-5-1-125.ipcolo1.Washington1.Level3.net [63.210.62.157]
 9   27 ms   26 ms   26 ms   26 ms   26 ms   26 ms   25 ms   27 ms   28 ms   25 ms  ae-4-99.edge1.Washington3.Level3.net [4.68.17.203]
10  N/A      25 ms  N/A      24 ms  N/A      25 ms  N/A      27 ms  N/A      25 ms  att-level3-oc192.Washington1.Level3.net [4.68.127.154]
11  N/A     N/A      95 ms   96 ms  321 ms   95 ms   96 ms   95 ms   95 ms   94 ms  tbr2.wswdc.ip.att.net [12.123.8.118]
12  N/A     N/A      95 ms   93 ms   96 ms   95 ms   95 ms   97 ms   96 ms   95 ms  cr2.wswdc.ip.att.net [12.122.16.109]
13  N/A     N/A      97 ms   96 ms   97 ms   97 ms   98 ms   97 ms   97 ms   98 ms  cr1.attga.ip.att.net [12.122.1.173]
14  N/A     N/A      94 ms   94 ms   95 ms   95 ms   95 ms   94 ms   94 ms   96 ms  cr2.dlstx.ip.att.net [12.122.28.174]
15  N/A     N/A     148 ms   96 ms   97 ms   98 ms   98 ms   96 ms   97 ms   98 ms  gar5.dlstx.ip.att.net [12.122.138.5]
16  N/A     N/A      99 ms   96 ms   97 ms   97 ms   98 ms   98 ms   97 ms   98 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
17  N/A     N/A     188 ms  113 ms  311 ms   98 ms  227 ms  107 ms   98 ms   98 ms  mdf1-bi8k-2-eth-2-1.dal1.attens.net [63.241.192.198]
18   97 ms   96 ms   95 ms   96 ms   95 ms   97 ms   95 ms   95 ms   95 ms   96 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 = 95ms, Maximum = 97ms, Average = 95ms

There you are sir. Big red spike at the beginning. Not sure what it means, so I'll take your word for it as far as interpretation. All I know is that I have never had a hiccup and now its driving me nuts as I can't complete a sortie. (Well one where I accidentally took off with 25% fuel, did a 180 at the end of the runway and landed  :lol
Title: Re: Connection Issues Last Five Days
Post by: Skuzzy on December 19, 2008, 02:54:41 PM
Yep, see those "N/A" in the Level3 network (hop #10)?  Consider that packet loss.  Only it is at the AT&T gateway from Level3.  I was close.

All bets are off after that.  I'll file a trouble ticket, but with Level3 it is not something they will get fixed.  You wil lneed to file a complaint with Comcast as well.  It wil not do any good, but at least it will get on record.

After the holidays, everything will return back to normal again.  I know that is little consolation, but this is what the cable company ISP's have all done to themselves.  All of them have, or are in process of, switching to Level3 for thier backbone.  Level3 did not have the capacity to carry one of the cable ISP's much less all of them.
Title: Re: Connection Issues Last Five Days
Post by: Skuzzy on December 19, 2008, 03:09:48 PM
Apparently, many Comcast users are having the same problem.  Seems to be network wide, effecting all Comcast users.

Might even be weather related, but I am guessing there.  And, of course, Comcast first tier support is saying they have no issues whatsoever.
Title: Re: Comast user connection issues
Post by: Paladin3 on December 19, 2008, 03:15:34 PM
Well Skuzzy, I appriciate your help sir. As well as the quick response. I just hope that it isn't like this all month. That would leave me without my addiction the whole time. I'll ream comcast here shortly.
Title: Re: Comast user connection issues
Post by: Skuzzy on December 19, 2008, 03:20:00 PM
Ok, Comcast has some issues going on.  Here is a trace back to you Paladin.  I have annotated the geographic area your data packets are traveling through.

traceroute 76.26.64.1
traceroute to 76.26.64.1 (76.26.64.1), 30 hops max, 40 byte packets
 dallas 1  206.16.60.33 (206.16.60.33)  0.657 ms  0.529 ms  0.491 ms
 dallas 2  mdf1-gsr12-1-gig-2-0.dal1.attens.net (63.241.192.205)  0.260 ms  0.193 ms  0.170 ms
 dallas 3  gar5.dlstx.ip.att.net (12.122.255.81)  1.214 ms  0.956 ms  0.924 ms
 dallas 4  cr2.dlstx.ip.att.net (12.122.138.6)  2.210 ms  1.774 ms  1.494 ms
 dallas 5  tbr2.dlstx.ip.att.net (12.122.18.198)  1.975 ms  1.690 ms  2.013 ms
 dallas 6  ggr3.dlstx.ip.att.net (12.123.16.205)  1.212 ms  1.232 ms  1.163 ms
 unknown 7  192.205.33.134 (192.205.33.134)  1.456 ms  1.412 ms  1.276 ms
 los angeles 8  cr1-pos-0-3-3-0.losangeles.savvis.net (204.70.194.53)  33.526 ms  33.761 ms  33.582 ms
 los angeles 9  er2-tengig-2-1.lay.savvis.net (204.70.198.6)  33.636 ms  33.675 ms  33.688 ms
unknown 10  208.172.41.162 (208.172.41.162)  34.692 ms  34.820 ms  34.918 ms
atlanta 11  pos-0-9-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.142)  36.710 ms  35.803 ms  36.051 ms
atlanta 12  pos-0-13-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.85.254)  55.581 ms  56.026 ms  55.470 ms
unknown 13  68.86.85.242 (68.86.85.242)  72.860 ms  72.837 ms  73.125 ms
pittsburgh 14  te-9-4-ar01.mckeesport.pa.pitt.comcast.net (68.86.91.130)  78.696 ms  78.895 ms  78.950 ms
pittsburgh 15  te-8-1-ar01.pittsburgh.pa.pitt.comcast.net (68.86.100.5)  84.531 ms  84.526 ms  84.392 ms
unknown 16  68.86.100.62 (68.86.100.62)  84.382 ms  84.397 ms  84.456 ms
west virginia 17  pos-4-1-ar01.huntington.wv.hntngton.comcast.net (68.86.100.106)  92.411 ms  92.680 ms  93.427 ms
west virginia 18  te-4-3-ur01.huntington.wv.hntngton.comcast.net (68.85.214.10)  92.692 ms  92.755 ms  94.665 ms
west virginia 19  c-76-26-64-1.hsd1.wv.comcast.net (76.26.64.1)  93.555 ms  93.220 ms  93.781 ms


That is just some bizarre routing going on right there.
Title: Re: Comast user connection issues
Post by: BaldEagl on December 19, 2008, 03:38:54 PM
Here's ping plots to both servers. I ran a third try to the Orange arena server and got destination address not reachable.  Everything else on the Internet is working just fine:

Target Name: N/A
         IP: 206.16.60.41
  Date/Time: 12/19/2008 3:27:42 PM to 12/19/2008 3:30:19 PM

 1    1 ms    0 ms    0 ms    0 ms    0 ms  N/A       0 ms    0 ms    0 ms    0 ms  [ME]
 2    7 ms    5 ms    5 ms    7 ms    7 ms  N/A       7 ms    7 ms    5 ms    5 ms  [--.---.---.-]
 3    6 ms    6 ms    6 ms    6 ms    6 ms  N/A       6 ms    6 ms    6 ms    7 ms  ge-9-2-ur02.minnetonka.mn.minn.comcast.net [68.85.164.125]
 4    6 ms    7 ms    7 ms    7 ms    7 ms  N/A       6 ms    7 ms    7 ms    5 ms  te-2-3-ur01.minnetonka.mn.minn.comcast.net [68.86.232.141]
 5    7 ms    5 ms    6 ms    6 ms    6 ms  N/A       6 ms    6 ms   18 ms    6 ms  te-8-1-ur01.martin.mn.minn.comcast.net [68.86.232.37]
 6    7 ms    7 ms    6 ms    7 ms    7 ms  N/A       6 ms    6 ms    6 ms    7 ms  te-2-3-ur01.martin.mn.minn.comcast.net [68.86.232.161]
 7    7 ms    6 ms    8 ms    8 ms    7 ms  N/A       7 ms    7 ms    8 ms    6 ms  te-8-1-ur02.crosstown.mn.minn.comcast.net [68.86.232.33]
 8    6 ms    6 ms    6 ms    6 ms    6 ms  N/A       6 ms    6 ms    6 ms    6 ms  te-2-1-ur01.crosstown.mn.minn.comcast.net [68.86.232.5]
 9    7 ms    9 ms    8 ms    8 ms    8 ms  N/A       7 ms    7 ms    8 ms    8 ms  te-0-1-0-5-ar02.crosstown.mn.minn.comcast.net [68.86.232.1]
10   11 ms    7 ms    7 ms    7 ms    8 ms  N/A       9 ms    9 ms    7 ms    7 ms  te-0-2-0-0-ar03.roseville.mn.minn.comcast.net [68.87.174.209]
11   18 ms   20 ms   17 ms   17 ms   17 ms  N/A      16 ms   17 ms   17 ms   17 ms  te-0-2-0-5-cr01.chicago.il.ibone.comcast.net [68.86.91.141]
12   19 ms   18 ms   18 ms   17 ms   17 ms  N/A      17 ms   17 ms   17 ms   18 ms  xe-10-0-0.edge1.Chicago2.Level3.net [4.71.248.29]
13   16 ms   16 ms   16 ms   18 ms   18 ms  N/A      16 ms   20 ms   16 ms   17 ms  vlan51.ebr1.Chicago2.Level3.n et [4.69.138.158]
14   20 ms   29 ms   23 ms   29 ms   17 ms  N/A      20 ms   26 ms   18 ms   26 ms  ae-6.ebr1.Chicago1.Level3.net [4.69.140.189]
15   20 ms   16 ms   18 ms   19 ms   18 ms  N/A      18 ms   18 ms   18 ms   17 ms  ae-14-51.car4.Chicago1.Level3.net [4.68.101.8]
16   17 ms   17 ms   17 ms   17 ms   18 ms  N/A      17 ms   17 ms   17 ms   17 ms  [192.205.33.209]
17   76 ms   78 ms   78 ms   77 ms   79 ms  N/A      77 ms   79 ms   77 ms   77 ms  tbr2.cgcil.ip.att.net [12.123.6.70]
18   82 ms   76 ms   76 ms   75 ms   78 ms  N/A      78 ms   78 ms   75 ms   76 ms  cr2.cgcil.ip.att.net [12.122.17.197]
19   76 ms   76 ms   76 ms   76 ms   77 ms  N/A      75 ms   76 ms   76 ms   76 ms  cr2.sl9mo.ip.att.net [12.122.2.22]
20   77 ms   77 ms   77 ms   77 ms   78 ms  N/A      78 ms   77 ms   77 ms   76 ms  cr1.sl9mo.ip.att.net [12.122.2.217]
21  106 ms   76 ms   76 ms   76 ms   75 ms  N/A      75 ms   75 ms   76 ms   76 ms  cr2.dlstx.ip.att.net [12.122.3.221]
22   79 ms   76 ms  118 ms   76 ms   76 ms  N/A      76 ms   76 ms   76 ms   95 ms  gar5.dlstx.ip.att.net [12.122.138.5]
23   77 ms   75 ms   78 ms   77 ms   77 ms  N/A      78 ms   77 ms   75 ms   76 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
24  559 ms   77 ms   78 ms  145 ms   77 ms  N/A      76 ms  538 ms   81 ms   77 ms  mdf1-bi8k-2-eth-2-2.dal1.attens.net [63.241.192.218]
25   78 ms   77 ms   80 ms   77 ms   77 ms  N/A      77 ms   77 ms   77 ms   78 ms  [206.16.60.41]

Ping statistics for 206.16.60.41
Packets: Sent = 9, Received = 9, Lost = 0 (0.0%)
Round Trip Times: Minimum = 77ms, Maximum = 80ms, Average = 77ms

Target Name: N/A
         IP: 206.16.60.39
  Date/Time: 12/19/2008 3:31:07 PM to 12/19/2008 3:33:22 PM

 1    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms  [ME]
 2    9 ms    6 ms    6 ms    7 ms    6 ms    6 ms    6 ms    6 ms    6 ms    6 ms  [--.---.---.-]
 3    8 ms    8 ms    7 ms    5 ms    6 ms    7 ms    5 ms    7 ms    7 ms    7 ms  ge-9-1-ur02.minnetonka.mn.minn.comcast.net [68.85.164.117]
 4    7 ms    6 ms    6 ms    7 ms    6 ms    6 ms    6 ms    6 ms    6 ms    6 ms  te-2-3-ur01.minnetonka.mn.minn.comcast.net [68.86.232.141]
 5    8 ms    7 ms    7 ms    7 ms    7 ms    7 ms    7 ms    7 ms    7 ms    7 ms  te-8-1-ur01.martin.mn.minn.comcast.net [68.86.232.37]
 6    7 ms   10 ms   10 ms    6 ms    6 ms    6 ms    6 ms    8 ms    7 ms    5 ms  te-2-3-ur01.martin.mn.minn.comcast.net [68.86.232.161]
 7    7 ms    6 ms    7 ms    7 ms    6 ms    6 ms    6 ms    6 ms    6 ms    6 ms  te-8-1-ur02.crosstown.mn.minn.comcast.net [68.86.232.33]
 8    7 ms    7 ms    7 ms    7 ms    7 ms    7 ms    7 ms    7 ms    7 ms    7 ms  te-2-1-ur01.crosstown.mn.minn.comcast.net [68.86.232.5]
 9   24 ms    6 ms    6 ms    7 ms    6 ms    7 ms    6 ms    7 ms   16 ms    6 ms  te-0-1-0-5-ar02.crosstown.mn.minn.comcast.net [68.86.232.1]
10    8 ms    8 ms    8 ms    8 ms    8 ms    8 ms    8 ms    8 ms    8 ms    8 ms  te-0-2-0-0-ar03.roseville.mn.minn.comcast.net [68.87.174.209]
11   21 ms   18 ms   18 ms   17 ms   16 ms   16 ms   17 ms   18 ms   19 ms   18 ms  te-0-2-0-4-cr01.chicago.il.ibone.comcast.net [68.86.91.137]
12   19 ms   16 ms   16 ms   75 ms   17 ms   16 ms   17 ms   16 ms   29 ms   17 ms  xe-9-2-0.edge1.Chicago2.Level3.net [4.71.248.25]
13   17 ms   18 ms   17 ms   17 ms   18 ms   18 ms   17 ms   17 ms   17 ms   17 ms  vlan51.ebr1.Chicago2.Level3.n et [4.69.138.158]
14   29 ms   26 ms   17 ms   22 ms   28 ms   18 ms   26 ms   17 ms   22 ms   16 ms  ae-6.ebr1.Chicago1.Level3.net [4.69.140.189]
15   18 ms   17 ms   17 ms   18 ms   18 ms   18 ms   18 ms  139 ms   17 ms   18 ms  ae-14-53.car4.Chicago1.Level3.net [4.68.101.72]
16   18 ms   18 ms   18 ms   19 ms   18 ms   23 ms   75 ms   18 ms   18 ms   18 ms  [192.205.33.209]
17   78 ms   76 ms   76 ms   80 ms   76 ms   77 ms   77 ms   77 ms   77 ms   77 ms  tbr2.cgcil.ip.att.net [12.123.6.70]
18   76 ms   77 ms   77 ms   77 ms   77 ms   78 ms   77 ms   81 ms   81 ms   79 ms  cr2.cgcil.ip.att.net [12.122.17.197]
19   77 ms   75 ms   78 ms   76 ms   78 ms   75 ms   76 ms   75 ms   77 ms   77 ms  cr2.sl9mo.ip.att.net [12.122.2.22]
20   75 ms   76 ms   76 ms   79 ms   76 ms   76 ms   77 ms   76 ms   76 ms   76 ms  cr2.kc9mo.ip.att.net [12.122.28.89]
21   78 ms   77 ms   77 ms   77 ms   77 ms   77 ms   77 ms   77 ms   85 ms   77 ms  cr1.dlstx.ip.att.net [12.122.28.85]
22   75 ms  153 ms   75 ms   75 ms   75 ms   75 ms   75 ms   75 ms   85 ms   77 ms  gar5.dlstx.ip.att.net [12.122.139.5]
23   76 ms   77 ms   77 ms   77 ms   77 ms   77 ms   76 ms   77 ms   77 ms   77 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
24   77 ms  559 ms   77 ms   76 ms   76 ms   78 ms   78 ms   77 ms   77 ms   77 ms  mdf1-bi8k-2-eth-2-1.dal1.attens.net [63.241.192.198]
25   80 ms   76 ms   76 ms   76 ms   76 ms   76 ms   76 ms   76 ms   76 ms   76 ms  [206.16.60.39]

Ping statistics for 206.16.60.39
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 76ms, Maximum = 80ms, Average = 76ms
Title: Re: Comast user connection issues
Post by: BaldEagl on December 19, 2008, 03:52:22 PM
Well this doesn't look good:

Target Name: N/A
         IP: 206.16.60.41
  Date/Time: 12/19/2008 3:49:52 PM to 12/19/2008 3:52:07 PM

 2    6 ms    6 ms    7 ms    6 ms    6 ms    6 ms    6 ms    6 ms    6 ms    6 ms  [73.112.244.1]
 3    6 ms    6 ms    7 ms    7 ms    8 ms    8 ms    7 ms    7 ms    7 ms    7 ms  ge-9-2-ur02.minnetonka.mn.minn.comcast.net [68.85.164.125]
 4    5 ms    6 ms    6 ms    6 ms    6 ms    6 ms    6 ms    6 ms    5 ms    6 ms  te-2-3-ur01.minnetonka.mn.minn.comcast.net [68.86.232.141]
 5    5 ms    7 ms    7 ms    7 ms    7 ms    7 ms    6 ms    7 ms    7 ms    7 ms  te-8-1-ur01.martin.mn.minn.comcast.net [68.86.232.37]
 6    5 ms    6 ms    6 ms    6 ms    6 ms    5 ms    6 ms    5 ms    5 ms    7 ms  te-2-3-ur01.martin.mn.minn.comcast.net [68.86.232.161]
 7    5 ms    7 ms    7 ms    7 ms    7 ms    7 ms    7 ms    6 ms    6 ms    7 ms  te-8-1-ur02.crosstown.mn.minn.comcast.net [68.86.232.33]
 8    7 ms    6 ms    6 ms    6 ms    5 ms    8 ms    7 ms    7 ms    7 ms    7 ms  te-2-1-ur01.crosstown.mn.minn.comcast.net [68.86.232.5]
 9    8 ms    8 ms    7 ms    7 ms    6 ms    6 ms    6 ms    7 ms    6 ms    7 ms  te-0-1-0-5-ar02.crosstown.mn.minn.comcast.net [68.86.232.1]
10    8 ms    8 ms    9 ms    8 ms    8 ms    9 ms    8 ms    8 ms    8 ms    8 ms  te-0-2-0-0-ar03.roseville.mn.minn.comcast.net [68.87.174.209]
11   18 ms   16 ms   16 ms   16 ms   16 ms   16 ms   18 ms   18 ms   18 ms   18 ms  te-0-2-0-5-cr01.chicago.il.ibone.comcast.net [68.86.91.141]
12   17 ms   17 ms   17 ms   18 ms   17 ms   17 ms   17 ms   16 ms   16 ms   16 ms  xe-10-0-0.edge1.Chicago2.Level3.net [4.71.248.29]
13   17 ms   18 ms   17 ms   17 ms   17 ms   18 ms   17 ms   17 ms   17 ms   17 ms  vlan51.ebr1.Chicago2.Level3.n et [4.69.138.158]
14   25 ms   17 ms   20 ms   27 ms   16 ms   21 ms   27 ms   16 ms   22 ms   27 ms  ae-6.ebr1.Chicago1.Level3.net [4.69.140.189]
15   18 ms   18 ms   18 ms   18 ms   18 ms   18 ms   17 ms   18 ms   17 ms   22 ms  ae-14-51.car4.Chicago1.Level3.net [4.68.101.8]
16   37 ms   33 ms   16 ms   17 ms   19 ms   18 ms   19 ms   18 ms   18 ms   18 ms  [192.205.33.209]
17   76 ms   76 ms   *       *       *       *       *       *       *       *      tbr2.cgcil.ip.att.net [12.123.6.70]
18   78 ms   78 ms   *       *       *       *       *       *       *       *      cr2.cgcil.ip.att.net [12.122.17.197]
19   76 ms   77 ms   *       *       *       *       *       *       *       *      cr2.sl9mo.ip.att.net [12.122.2.22]
20   76 ms   77 ms  132 ms  298 ms  289 ms  228 ms  112 ms   76 ms   76 ms   76 ms  cr1.sl9mo.ip.att.net [12.122.2.217]
21   76 ms   76 ms  135 ms  298 ms  289 ms  228 ms  112 ms   77 ms   77 ms   76 ms  cr2.dlstx.ip.att.net [12.122.3.221]
22   79 ms   76 ms  184 ms  297 ms  287 ms  423 ms  110 ms   75 ms   75 ms   77 ms  gar5.dlstx.ip.att.net [12.122.138.5]
23   76 ms   77 ms   *       *       *       *       *       *       *       *      mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
24   77 ms   76 ms  131 ms  297 ms  288 ms  212 ms   92 ms   78 ms  195 ms   79 ms  mdf1-bi8k-2-eth-2-2.dal1.attens.net [63.241.192.218]
25   76 ms   77 ms   *       *       *       *       *       *       *       *      [206.16.60.41]

Ping statistics for 206.16.60.41
Packets: Sent = 10, Received = 2, Lost = 8 (80.0%)
Round Trip Times: Minimum = 76ms, Maximum = 77ms, Average = 76ms

Another thing.  I can easily get to the AH website but sometimes can't access the forums.
Title: Re: Comast user connection issues
Post by: Skuzzy on December 19, 2008, 03:55:05 PM
25 hops from Minnesota?  That's insane.

The trace back to you does not look good either.

traceroute 68.85.164.125
traceroute to 68.85.164.125 (68.85.164.125), 30 hops max, 40 byte packets
 1  206.16.60.33 (206.16.60.33)  0.678 ms  0.541 ms  0.482 ms
 2  mdf1-gsr12-1-gig-2-0.dal1.attens.net (63.241.192.205)  0.237 ms  0.173 ms  0.145 ms
 3  gar5.dlstx.ip.att.net (12.122.255.77)  0.984 ms  0.931 ms  0.906 ms
 4  cr1.dlstx.ip.att.net (12.122.139.6)  2.591 ms  1.637 ms  1.316 ms
 5  tbr1.dlstx.ip.att.net (12.122.18.154)  1.904 ms  1.864 ms  1.994 ms
 6  ggr3.dlstx.ip.att.net (12.123.16.193)  1.195 ms  1.188 ms  1.152 ms
 7  bcr2-so-6-0-0.Dallas.savvis.net (208.172.139.225)  1.310 ms  1.355 ms  1.285 ms
 8  * cr1-pos-0-3-3-1.losangeles.savvis.net (204.70.192.245)  33.739 ms  33.700 ms
 9  er2-tengig-2-1.lay.savvis.net (204.70.198.6)  33.665 ms  33.646 ms  33.682 ms
10  208.173.55.218 (208.173.55.218)  34.341 ms  40.606 ms  35.157 ms
11  pos-0-8-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.138)  35.595 ms  35.902 ms  35.878 ms
12  pos-0-7-0-0-cr01.denver.co.ibone.comcast.net (68.86.85.173)  50.624 ms  51.493 ms  51.034 ms
13  te-9-4-ar02.roseville.mn.minn.comcast.net (68.86.91.154)  69.379 ms  68.861 ms  68.613 ms
14  te-2-3-ar01.roseville.mn.minn.comcast.net (68.87.174.1)  71.757 ms  71.923 ms  71.223 ms
15  te-8-1-ur01.crosstown.mn.minn.comcast.net (68.86.232.2)  71.190 ms  70.674 ms  70.767 ms
16  te-2-1-ur02.crosstown.mn.minn.comcast.net (68.86.232.6)  69.431 ms  69.342 ms  69.404 ms
17  te-2-1-ur01.martin.mn.minn.comcast.net (68.86.232.34)  69.802 ms  69.465 ms  69.400 ms
18  te-2-3-ur02.martin.mn.minn.comcast.net (68.86.232.162)  69.785 ms  69.958 ms  69.779 ms
19  te-2-1-ur01.minnetonka.mn.minn.comcast.net (68.86.232.38)  70.306 ms  69.859 ms  69.946 ms
20  68.85.164.122 (68.85.164.122)  69.624 ms  69.666 ms  69.695 ms
21  ge-9-2-ur02.minnetonka.mn.minn.comcast.net (68.85.164.125)  70.251 ms *  70.204 ms
Title: Re: Comast user connection issues
Post by: Skuzzy on December 19, 2008, 03:58:21 PM
It looks like every single packet destined for a Comcast user is being routed through one router in Los Angeles.

This wreaks of a routing issue, but I do not know who is screwing up at the moment.
Title: Re: Comast user connection issues
Post by: BaldEagl on December 19, 2008, 03:59:14 PM
So what can I do about it?
Title: Re: Comast user connection issues
Post by: Skuzzy on December 19, 2008, 04:01:00 PM
Contact Comcast and tell them you need the problem escalated to tier two, or higher.  First tier support only knows how to trouble shoot your local connection only.
Title: Re: Comcast user connection issues
Post by: kvuo75 on December 19, 2008, 04:26:39 PM
2 discos in 17 mins  :cry

Target Name: N/A
         IP: 206.16.60.41
  Date/Time: 12/19/2008 2:24:41 PM to 12/19/2008 2:25:26 PM

 1    2 ms    2 ms    2 ms    2 ms    2 ms    2 ms    6 ms    2 ms    2 ms    1 ms  [192.168.1.1]
 2    7 ms    7 ms   10 ms    7 ms    8 ms    9 ms   10 ms    8 ms    7 ms   10 ms  [73.93.112.1]
 3    8 ms    7 ms    8 ms    8 ms    8 ms    8 ms    8 ms    8 ms    8 ms   10 ms  [68.85.150.49]
 4    8 ms    8 ms    9 ms   16 ms    9 ms    9 ms    9 ms    9 ms    8 ms   14 ms  te-8-3-ar01.beaverton.or.bverton.comcast.net [68.87.216.21]
 5   11 ms   11 ms   12 ms   11 ms   16 ms   12 ms   12 ms   13 ms   13 ms   15 ms  [68.86.90.229]
 6   14 ms   14 ms   15 ms   13 ms   23 ms   14 ms   18 ms   14 ms   14 ms   14 ms  pos-0-0-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.85.205]
 7   13 ms  245 ms   14 ms   13 ms   13 ms   14 ms   14 ms   15 ms   14 ms   14 ms  te-3-3.car1.Seattle1.Level3.net [4.79.104.109]
 8   13 ms   13 ms   14 ms   13 ms   13 ms   14 ms   15 ms   14 ms   15 ms   14 ms  ge-1-0-0-51.gar1.Seattle1.Level3.net [4.68.105.9]
 9   32 ms  N/A      30 ms  N/A     N/A      31 ms  N/A      30 ms  N/A      32 ms  att-level3-oc48.seattle1.level3.net [4.68.127.110]
10   75 ms   76 ms   74 ms   75 ms   77 ms   74 ms   74 ms   76 ms   74 ms   76 ms  tbr1.st6wa.ip.att.net [12.127.6.58]
11   *       *       *       *       *       *       *       *       *       *       [-]
12   *       *       *       *       *       *       *       *       *       *       [-]
13   *       *       *       *       *       *       *       *       *       *       [-]
14   73 ms   77 ms   75 ms   76 ms   75 ms   75 ms   77 ms   75 ms   77 ms   74 ms  cr2.dlstx.ip.att.net [12.122.28.177]
15   75 ms   90 ms   *       73 ms   75 ms   74 ms   76 ms   *       75 ms   74 ms  gar5.dlstx.ip.att.net [12.122.138.5]
16   *       *       *       *       *       *       *       *       *       *       [-]
17   76 ms   80 ms   76 ms   75 ms   76 ms  517 ms   76 ms   76 ms   75 ms   75 ms  mdf1-bi8k-1-eth-1-2.dal1.attens.net [63.241.192.202]
18   75 ms   83 ms   75 ms   75 ms   76 ms   74 ms   75 ms   76 ms   75 ms   74 ms  [206.16.60.41]

Ping statistics for 206.16.60.41
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 74ms, Maximum = 83ms, Average = 75ms
Title: Re: Comcast user connection issues
Post by: Skuzzy on December 19, 2008, 04:27:06 PM
I need as many Comcast users as I can get to post in this thread with trace routes to 206.16.60.38.
Title: Re: Comcast user connection issues
Post by: BaldEagl on December 19, 2008, 04:27:52 PM
Called Comcast.  Gave them all the addresses with problems.  They said a specialist was going to research it and get back to me within 24 hours.  I'll hold my breath.
Title: Re: Comcast user connection issues
Post by: Skuzzy on December 19, 2008, 04:29:01 PM
kvou, here is what I get when I try to trace back to your second hop.

traceroute 73.93.112.1
traceroute to 73.93.112.1 (73.93.112.1), 30 hops max, 40 byte packets
 1  206.16.60.33 (206.16.60.33)  0.618 ms  0.513 ms  0.441 ms
 2  mdf1-gsr12-1-gig-2-0.dal1.attens.net (63.241.192.205)  0.361 ms  0.175 ms  0.146 ms
 3  gar5.dlstx.ip.att.net (12.122.255.81)  1.056 ms  0.940 ms  0.919 ms
 4  cr1.dlstx.ip.att.net (12.122.139.6)  2.116 ms  1.447 ms  1.291 ms
 5  tbr1.dlstx.ip.att.net (12.122.18.146)  1.627 ms  2.017 ms  1.975 ms
 6  ggr3.dlstx.ip.att.net (12.123.16.193)  1.341 ms  1.226 ms  1.173 ms
 7  192.205.33.134 (192.205.33.134)  1.631 ms  1.608 ms  1.370 ms
 8  cr1-pos-0-3-3-0.losangeles.savvis.net (204.70.194.53)  34.067 ms  33.773 ms  33.617 ms
 9  er2-tengig-2-1.lay.savvis.net (204.70.198.6)  33.644 ms  33.640 ms  33.755 ms
10  * * *
11  * * *

Not good.
Title: Re: Comcast user connection issues
Post by: kvuo75 on December 19, 2008, 04:43:51 PM
heres to teh other server


Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/19/2008 2:36:34 PM to 12/19/2008 2:41:29 PM

Hop Sent Err  PL% Min Max Avg  Host Name / [IP]
 1    60   0  0.0   1   7   2  [192.168.1.1]
 2    60   0  0.0   6  16   8  [73.93.112.1]
 3    60   1  1.7   7  17   9  [68.85.150.57]
 4    60   1  1.7   8  15   9  te-8-2-ar01.troutdale.or.bverton.comcast.net [68.87.216.81]
 5    60   0  0.0  12  19  13  te-0-4-0-5-cr01.seattle.wa.ibone.comcast.net [68.86.90.237]
 6    60   1  1.7  12 208  29  te-3-3.car1.Seattle1.Level3.net [4.79.104.109]
 7    60   1  1.7  12  24  13  ge-2-0-0-54.gar1.Seattle1.Level3.net [4.68.105.105]
 8    29   1  3.4  28  75  32  [192.205.33.145]
 9    60  28 46.7  73  78  74  tbr1.st6wa.ip.att.net [12.127.6.169]
10    60   1  1.7  72 297 114  cr1.st6wa.ip.att.net [12.122.23.145]
11    60  26 43.3  73  81  74  cr2.sffca.ip.att.net [12.122.31.194]
12    60  26 43.3  73  99  76  cr2.la2ca.ip.att.net [12.122.31.133]
13    60  10 16.7  72 275  91  cr2.dlstx.ip.att.net [12.122.28.177]
14    60  12 20.0  72 301  87  gar5.dlstx.ip.att.net [12.122.138.5]
15    60  29 48.3  73  87  74  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
16    60  26 43.3  73 519  91  mdf1-bi8k-2-eth-2-1.dal1.attens.net [63.241.192.198]
17    60   1  1.7  73 453 121  [206.16.60.38]


Title: Re: Comcast user connection issues
Post by: BaldEagl on December 19, 2008, 04:44:06 PM
Here's a 206.16.60.38 for you.  It took me five minutes to get to the forums (multiple page not available screens).  Everything else on the Internet is working fine for me.

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/19/2008 4:38:42 PM to 12/19/2008 4:40:57 PM

 2    8 ms    5 ms    8 ms    5 ms    7 ms    7 ms    7 ms    8 ms    6 ms    7 ms  [73.112.244.1]
 3    6 ms    8 ms    6 ms    6 ms    6 ms    9 ms    6 ms    7 ms    6 ms    6 ms  ge-9-1-ur02.minnetonka.mn.minn.comcast.net [68.85.164.117]
 4    7 ms    7 ms    7 ms    7 ms    7 ms    7 ms    7 ms    8 ms    7 ms    7 ms  te-2-3-ur01.minnetonka.mn.minn.comcast.net [68.86.232.141]
 5    6 ms    6 ms    7 ms    6 ms    6 ms    5 ms    6 ms    7 ms    5 ms    7 ms  te-8-1-ur01.martin.mn.minn.comcast.net [68.86.232.37]
 6    8 ms    7 ms    7 ms    8 ms    6 ms    7 ms    6 ms    8 ms    6 ms    6 ms  te-2-3-ur01.martin.mn.minn.comcast.net [68.86.232.161]
 7    7 ms    5 ms    6 ms    8 ms    7 ms    8 ms    7 ms    7 ms    8 ms    7 ms  te-8-1-ur02.crosstown.mn.minn.comcast.net [68.86.232.33]
 8    7 ms    6 ms    6 ms    6 ms    6 ms    6 ms    6 ms    6 ms    6 ms    6 ms  te-2-1-ur01.crosstown.mn.minn.comcast.net [68.86.232.5]
 9    8 ms    8 ms    7 ms    7 ms    7 ms    7 ms    7 ms    8 ms    8 ms    8 ms  te-0-1-0-5-ar02.crosstown.mn.minn.comcast.net [68.86.232.1]
10    7 ms    7 ms    7 ms    6 ms    7 ms    7 ms    9 ms    8 ms    8 ms    8 ms  te-8-3-ar02.roseville.mn.minn.comcast.net [68.87.174.6]
11   25 ms   26 ms   25 ms   25 ms   25 ms   25 ms   25 ms   26 ms   25 ms   26 ms  [68.86.91.181]
12  109 ms   26 ms   26 ms   27 ms   26 ms   26 ms   26 ms   26 ms   26 ms   25 ms  te-4-4.car2.Denver1.Level3.net [4.79.82.57]
13   28 ms   30 ms   36 ms   25 ms   32 ms   25 ms   29 ms   37 ms   26 ms   34 ms  ae-31-55.ebr1.Denver1.Level3.net [4.68.107.158]
14   42 ms   41 ms   42 ms   49 ms   51 ms   53 ms   40 ms   41 ms   43 ms   45 ms  ae-2.ebr2.Dallas1.Level3.net [4.69.132.106]
15   43 ms   41 ms   44 ms   46 ms   48 ms   51 ms   54 ms   41 ms   41 ms   43 ms  ae-82-82.csw3.Dallas1.Level3.net [4.69.136.146]
16   43 ms   41 ms   41 ms   41 ms   41 ms   40 ms   41 ms   41 ms   41 ms   40 ms  ae-3-89.edge2.Dallas3.Level3.net [4.68.19.140]
17   76 ms   75 ms   75 ms   75 ms   75 ms  113 ms   75 ms   75 ms   75 ms   75 ms  [192.205.35.141]
18   78 ms   75 ms   75 ms   74 ms   75 ms   74 ms   76 ms   76 ms   76 ms   77 ms  tbr2.dlstx.ip.att.net [12.122.86.210]
19   76 ms   75 ms   76 ms   75 ms   75 ms   75 ms   75 ms   75 ms   75 ms   75 ms  cr2.dlstx.ip.att.net [12.122.18.229]
20   76 ms   76 ms   77 ms   75 ms   76 ms   75 ms   81 ms  168 ms   75 ms   75 ms  gar5.dlstx.ip.att.net [12.122.138.5]
21   79 ms   75 ms   76 ms   75 ms   75 ms   74 ms   74 ms   75 ms   77 ms   77 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
22   75 ms   76 ms   78 ms   76 ms   76 ms   75 ms   76 ms  322 ms   79 ms   76 ms  mdf1-bi8k-2-eth-2-1.dal1.attens.net [63.241.192.198]
23   79 ms   75 ms   77 ms   76 ms   76 ms   77 ms   76 ms   76 ms   76 ms   76 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 = 75ms, Maximum = 79ms, Average = 76ms
Title: Re: Comcast user connection issues
Post by: kvuo75 on December 19, 2008, 04:45:53 PM
yea bald. the last few mins, lost website also.. same time as you..


Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/19/2008 2:45:11 PM to 12/19/2008 2:45:56 PM

 1    1 ms    2 ms    2 ms    2 ms    2 ms    2 ms    2 ms    2 ms    2 ms    2 ms  [192.168.1.1]
 2    8 ms    7 ms   14 ms    6 ms    7 ms    8 ms   15 ms    8 ms    9 ms    7 ms  [73.93.112.1]
 3    9 ms    7 ms    6 ms   12 ms    7 ms    9 ms    8 ms    7 ms    7 ms    8 ms  [68.85.150.57]
 4    9 ms    9 ms    9 ms    8 ms   14 ms    9 ms    9 ms   10 ms   16 ms    8 ms  te-8-2-ar01.troutdale.or.bverton.comcast.net [68.87.216.81]
 5   13 ms   14 ms   13 ms   13 ms   14 ms   13 ms   13 ms   22 ms   14 ms   13 ms  te-0-4-0-5-cr01.seattle.wa.ibone.comcast.net [68.86.90.237]
 6   14 ms   12 ms   13 ms   12 ms   14 ms   94 ms   *       12 ms   14 ms   14 ms  te-3-3.car1.Seattle1.Level3.net [4.79.104.109]
 7   13 ms   13 ms   76 ms   40 ms   14 ms   13 ms   13 ms   14 ms   13 ms   12 ms  ge-2-0-0-54.gar1.Seattle1.Level3.net [4.68.105.105]
 8   30 ms   30 ms   *      N/A      30 ms   *       29 ms  N/A     N/A      28 ms  [192.205.33.145]
 9   75 ms   74 ms   82 ms   80 ms   78 ms   74 ms   75 ms   73 ms   74 ms   74 ms  tbr1.st6wa.ip.att.net [12.127.6.169]
10   74 ms   73 ms   76 ms   73 ms   74 ms   73 ms   74 ms   73 ms   74 ms  N/A     cr1.st6wa.ip.att.net [12.122.23.145]
11   82 ms   74 ms   75 ms   73 ms   73 ms   78 ms   74 ms   73 ms   74 ms  N/A     cr2.sffca.ip.att.net [12.122.31.194]
12   *       73 ms   74 ms   73 ms   74 ms   73 ms   78 ms   74 ms   74 ms  N/A     cr2.la2ca.ip.att.net [12.122.31.133]
13   76 ms   74 ms   74 ms   74 ms   83 ms   88 ms   72 ms   73 ms   73 ms  N/A     cr2.dlstx.ip.att.net [12.122.28.177]
14   74 ms   73 ms   73 ms   73 ms   *       *       74 ms   74 ms   74 ms  N/A     gar5.dlstx.ip.att.net [12.122.138.5]
15   73 ms   75 ms   74 ms   74 ms   74 ms   74 ms   74 ms   74 ms   75 ms  N/A     mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
16   75 ms   73 ms   73 ms   74 ms   75 ms   75 ms   75 ms   75 ms   75 ms  N/A     mdf1-bi8k-2-eth-2-1.dal1.attens.net [63.241.192.198]
17   73 ms   74 ms   74 ms   74 ms   73 ms   75 ms   73 ms   73 ms   73 ms  N/A     [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 9, Received = 9, Lost = 0 (0.0%)
Round Trip Times: Minimum = 73ms, Maximum = 75ms, Average = 73ms
Title: Re: Comcast user connection issues
Post by: Skuzzy on December 19, 2008, 04:46:12 PM
The number of hops changed.  Not a good sign at all.  And I still cannot get back to your connection.
Title: Re: Comcast user connection issues
Post by: Skuzzy on December 19, 2008, 04:49:47 PM
Here's a 206.16.60.38 for you.  It took me five minutes to get to the forums (multiple page not available screens).  Everything else on the Internet is working fine for me.

No, everything else is not working fine.  Our WEB page is at another ISP (ThePlanet).  Our forums is on another connection in AT&T network.  Our server are at another location.  From what you just said, you are having issues with all three locations.

I just went in a did a poll of Comcast userss in the arena.  It seems only the people in the NW part of the U.S, maybe some surrounding areas, are being affected.
Title: Re: Comcast user connection issues
Post by: Paladin3 on December 19, 2008, 04:51:26 PM
Yeah for me, AH is the only thing I am having problems with. America's Army, web surfing, chat all work just fine. Guess none of them have that much drag on the pipeline...
Title: Re: Comcast user connection issues
Post by: kvuo75 on December 19, 2008, 04:54:36 PM
stupid intertubes being all messed up.....  :frown:


i wish I had run pingplotter before to various places under good circumstances so I could compare... I have no idea how to interpret it now, except seeing packet losses at almost every hop CANT be good :)


which btw, is it normal to see route changes almost every 5-10 seconds?



Title: Re: Comcast user connection issues
Post by: BaldEagl on December 19, 2008, 04:55:49 PM
When I was getting disco'd I went and watched a 90+ minute streamed movie at Netflix without issue.  Not sure where they are located though.  No problems with NFL, Nascar, Microsoft or other web-sites.
Title: Re: Comcast user connection issues
Post by: Skuzzy on December 19, 2008, 05:03:46 PM
stupid intertubes being all messed up.....  :frown:


i wish I had run pingplotter before to various places under good circumstances so I could compare... I have no idea how to interpret it now, except seeing packet losses at almost every hop CANT be good :)


which btw, is it normal to see route changes almost every 5-10 seconds?

No it is not normal  In the networking business, that is known as a router flap.  Not a good thing at all.
Title: Re: Comcast user connection issues
Post by: angels10 on December 19, 2008, 05:15:12 PM
Northern IN comcast hostage here same disco and log in probs .  Don't  know how to ping wish i could help though.  I guess i am in the offline practice arena. ill keep checking in tho good luck :cry :salute
Title: Re: Comcast user connection issues
Post by: BaldEagl on December 19, 2008, 05:20:46 PM
Skuzzy... don't think you're getting out of there until you've fixed the Internet.    ;)
Title: Re: Comcast user connection issues
Post by: Hawk55 on December 19, 2008, 05:45:35 PM
Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/19/2008 6:43:13 PM to 12/19/2008 6:43:58 PM

 1    7 ms   11 ms    6 ms    5 ms    6 ms    6 ms   17 ms    8 ms    8 ms    6 ms  [73.156.172.1]
 2    7 ms    7 ms    6 ms   10 ms    8 ms   12 ms    6 ms    5 ms    7 ms    5 ms  ge-3-40-ur01.danbury.ct.hartford.comcast.net [68.86.231.66]
 3    7 ms    6 ms    6 ms    9 ms    6 ms    6 ms    8 ms    6 ms    6 ms    6 ms  te-8-3-ur02.danbury.ct.hartford.comcast.net [68.86.231.226]
 4    7 ms   10 ms    8 ms    9 ms    7 ms   10 ms    8 ms    9 ms   11 ms    8 ms  te-9-1-ur01.westhaven.ct.hartford.comcast.net [68.87.182.62]
 5   22 ms   20 ms   16 ms   16 ms   20 ms   26 ms   23 ms   14 ms   12 ms   13 ms  te-9-1-ur01.newhaven.ct.hartford.comcast.net [68.87.182.58]
 6    8 ms   10 ms    8 ms    9 ms   10 ms   16 ms    7 ms    8 ms   10 ms  N/A     te-4-1-rr01.branford.ct.hartford.comcast.net [68.87.182.54]
 7   10 ms   10 ms   10 ms    8 ms   13 ms   17 ms    9 ms    9 ms   10 ms  N/A     po-21-rr01.bolton.ct.hartford.comcast.net [68.87.182.210]
 8   11 ms   12 ms   10 ms   11 ms   11 ms   12 ms    9 ms    9 ms   13 ms  N/A     po-23-rr01.ehartford.ct.hartford.comcast.net [68.87.182.229]
 9   12 ms   13 ms   12 ms   11 ms   10 ms   10 ms   11 ms    9 ms    9 ms  N/A     po-22-rr01.chartford.ct.hartford.comcast.net [68.87.182.233]
10   10 ms    9 ms    9 ms   13 ms    9 ms   10 ms   12 ms   10 ms   10 ms  N/A     te-8-1-ar01.chartford.ct.hartford.comcast.net [68.87.182.86]
11   14 ms   14 ms   13 ms   16 ms   14 ms   12 ms   13 ms   12 ms   13 ms  N/A     te-0-4-0-1-cr01.newyork.ny.ibone.comcast.net [68.86.90.61]
12   15 ms   15 ms   34 ms   15 ms   16 ms   16 ms   15 ms   14 ms   14 ms  N/A     xe-11-0-0.edge1.NewYork2.Level3.net [4.71.186.1]
13   12 ms   14 ms   13 ms   14 ms   16 ms   13 ms   14 ms   52 ms   13 ms  N/A     ae-43-99.car3.NewYork1.Level3.net [4.68.16.197]
14   37 ms   13 ms   27 ms   16 ms   16 ms   26 ms   15 ms   15 ms   15 ms  N/A     [192.205.33.93]
15   91 ms   90 ms   90 ms   91 ms   92 ms   89 ms   91 ms   91 ms   91 ms  N/A     tbr2.n54ny.ip.att.net [12.123.3.110]
16   89 ms   91 ms   89 ms   92 ms  105 ms   92 ms   90 ms   88 ms   91 ms  N/A     cr2.n54ny.ip.att.net [12.122.16.197]
17   89 ms   88 ms   89 ms   88 ms  112 ms   89 ms   90 ms   90 ms   92 ms  N/A     cr2.wswdc.ip.att.net [12.122.3.38]
18   89 ms   90 ms   90 ms   89 ms   94 ms   89 ms   90 ms   89 ms   90 ms  N/A     cr1.attga.ip.att.net [12.122.1.173]
19   91 ms   89 ms   89 ms   89 ms   96 ms   90 ms   90 ms   91 ms   90 ms  N/A     cr2.dlstx.ip.att.net [12.122.28.174]
20   89 ms   88 ms   89 ms   90 ms   98 ms   89 ms  277 ms   88 ms   89 ms  N/A     gar5.dlstx.ip.att.net [12.122.138.5]
21   92 ms   88 ms   90 ms   93 ms   91 ms   91 ms   91 ms   91 ms   90 ms  N/A     mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
22   90 ms   88 ms   90 ms   91 ms   89 ms   90 ms   90 ms   91 ms   92 ms  N/A     mdf1-bi8k-1-eth-1-1.dal1.attens.net [63.241.192.250]
23   91 ms   90 ms   90 ms   90 ms   90 ms   90 ms   91 ms   92 ms   89 ms  N/A     [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 = 92ms, Average = 90ms

Here you go Skuzz...*@#* Comcast
Title: Re: Comcast user connection issues
Post by: VonMessa on December 19, 2008, 05:47:59 PM
I live in Lansdale, PA  about 10-15 miles from Philadelphia proper.

The following is a 5 minute plot using pingplotter(free) immediately after I discoed.

Host Information
1,,-
2, -------------- ,68.87.215.233
3,po-90-ur01.pottstown.pa.panjde.comcast.net,68.86.209.157
4,po-90-ur01.phoenixville.pa.panjde.comcast.net,68.86.209.153
5,po-21-ur01.coatesville.pa.panjde.comcast.net,68.86.209.149
6,po-10-ar01.newcastle.de.panjde.comcast.net,68.86.211.193
7,po-90-ur01.medford.nj.panjde.comcast.net,68.86.210.209
8,pos-0-5-0-0-cr01.philadelphia.pa.ibone.comcast.net,68.86.90.13
9,xe-11-0-0.edge1.Washington1.Level3.net,4.79.231.1
10,ae-3-89.edge1.Washington3.Level3.net,4.68.17.139
11,att-level3-oc192.Washington1.Level3.net,209.244.219.142
12,tbr2.wswdc.ip.att.net,12.123.8.110
13,cr2.wswdc.ip.att.net,12.122.16.125
14,cr1.attga.ip.att.net,12.122.1.173
15,cr2.dlstx.ip.att.net,12.122.28.174
16,gar5.dlstx.ip.att.net,12.122.138.5
17,mdf1-gsr12-1-pos-6-0.dal1.attens.net,12.122.255.78
18,mdf1-bi8k-1-eth-1-1.dal1.attens.net,63.241.192.250
19, -------------- ,206.16.60.38

Sample Information
"12/19/2008 6:40:55 PM",*,11,11,22,12,16,14,21,20,18,N/A,91,92,90,91,91,91,91,91
"12/19/2008 6:41:10 PM",*,12,12,13,14,14,16,20,74,20,20,92,90,91,92,130,91,92,90
"12/19/2008 6:41:25 PM",*,19,16,13,14,24,14,26,79,20,20,92,114,90,101,90,90,98,91
"12/19/2008 6:41:40 PM",*,14,13,13,16,18,18,20,38,21,N/A,93,91,94,95,90,106,96,91
"12/19/2008 6:41:55 PM",*,11,12,12,15,14,15,21,36,21,N/A,92,95,90,91,89,100,92,90
"12/19/2008 6:42:10 PM",*,24,13,13,14,16,16,19,71,22,21,91,92,94,91,91,90,91,91
"12/19/2008 6:42:25 PM",*,10,15,15,24,28,24,20,19,21,22,93,124,95,92,102,92,92,92
"12/19/2008 6:42:40 PM",*,11,11,12,16,14,15,20,39,22,N/A,91,94,92,91,158,92,93,93
"12/19/2008 6:42:55 PM",*,12,21,14,15,15,17,44,20,26,N/A,92,93,92,98,93,91,92,111


(http://i239.photobucket.com/albums/ff107/tymekeepyr/206166038.png)
Title: Re: Comcast user connection issues
Post by: Hawk55 on December 19, 2008, 05:52:33 PM
Here's the next one Skuzzy...Unbelievable!  We are in the middle of a snowstorm if that has anything to do with it.

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/19/2008 6:50:43 PM to 12/19/2008 6:51:28 PM

 1    5 ms    7 ms    5 ms    6 ms    5 ms    7 ms    6 ms    6 ms    6 ms    6 ms  [73.156.172.1]
 2    5 ms    6 ms    7 ms    7 ms    6 ms    7 ms    6 ms    6 ms    7 ms    6 ms  ge-3-40-ur01.danbury.ct.hartford.comcast.net [68.86.231.66]
 3    7 ms    6 ms    7 ms    5 ms    5 ms    6 ms    7 ms    6 ms    6 ms    5 ms  te-8-3-ur02.danbury.ct.hartford.comcast.net [68.86.231.226]
 4    7 ms   10 ms    7 ms    7 ms    7 ms    6 ms    7 ms    8 ms    8 ms    9 ms  te-9-1-ur01.westhaven.ct.hartford.comcast.net [68.87.182.62]
 5    7 ms    6 ms    6 ms   10 ms    7 ms    8 ms    8 ms    7 ms    7 ms    9 ms  te-9-1-ur01.newhaven.ct.hartford.comcast.net [68.87.182.58]
 6    8 ms    8 ms    9 ms   11 ms    8 ms    7 ms    8 ms   10 ms   70 ms    8 ms  te-4-1-rr01.branford.ct.hartford.comcast.net [68.87.182.54]
 7    8 ms   10 ms   19 ms    9 ms    9 ms    9 ms    8 ms    8 ms    8 ms   10 ms  po-21-rr01.bolton.ct.hartford.comcast.net [68.87.182.210]
 8   13 ms    9 ms   14 ms   11 ms   10 ms    8 ms    9 ms   12 ms   10 ms   10 ms  po-23-rr01.ehartford.ct.hartford.comcast.net [68.87.182.229]
 9   11 ms   11 ms    8 ms    9 ms    9 ms    9 ms   10 ms    9 ms    8 ms   20 ms  po-22-rr01.chartford.ct.hartford.comcast.net [68.87.182.233]
10    9 ms   10 ms   12 ms   11 ms   10 ms    9 ms    9 ms    9 ms    9 ms   12 ms  te-8-1-ar01.chartford.ct.hartford.comcast.net [68.87.182.86]
11   16 ms   14 ms   11 ms   13 ms   14 ms   13 ms   14 ms   11 ms   11 ms   14 ms  te-0-4-0-1-cr01.newyork.ny.ibone.comcast.net [68.86.90.61]
12   12 ms   14 ms   53 ms   12 ms   13 ms   13 ms   12 ms   13 ms   12 ms   12 ms  xe-11-0-0.edge1.NewYork2.Level3.net [4.71.186.1]
13   13 ms   14 ms   17 ms   12 ms   14 ms   12 ms   13 ms   13 ms   14 ms   32 ms  ae-43-99.car3.NewYork1.Level3.net [4.68.16.197]
14   14 ms   13 ms   14 ms   13 ms   14 ms   14 ms   13 ms   13 ms   22 ms   13 ms  [192.205.33.93]
15   *       *       *       *       *       *       *       *       *      N/A     tbr2.n54ny.ip.att.net [12.123.3.110]
16   89 ms   89 ms  100 ms   90 ms   89 ms   89 ms   90 ms   90 ms   89 ms   90 ms  cr2.n54ny.ip.att.net [12.122.16.197]
17   89 ms   90 ms   89 ms   88 ms   89 ms   89 ms   89 ms   98 ms  104 ms   89 ms  cr2.wswdc.ip.att.net [12.122.3.38]
18   *       *       *       *       *       *       *       *       *      N/A     cr1.attga.ip.att.net [12.122.1.173]
19   *       *       *       *       *       *       *       *       *      N/A     cr2.dlstx.ip.att.net [12.122.28.174]
20   *       *       *       *       *       *       *       *       *      N/A     gar5.dlstx.ip.att.net [12.122.138.5]
21   *       *       *       *       *       *       *       *       *      N/A     mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
22   92 ms   90 ms   91 ms   89 ms   90 ms   89 ms   90 ms   89 ms   88 ms   90 ms  mdf1-bi8k-1-eth-1-1.dal1.attens.net [63.241.192.250]
23   *       *       *       *       *       *       *       *       *      N/A     [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 10, Received = 0, Lost = 10 (100.0%)
Round Trip Times: Minimum = 0ms, Maximum = 0ms, Average = 0ms
Title: Re: Comcast user connection issues
Post by: kvuo75 on December 19, 2008, 05:56:13 PM
alright been runnin pingplot almost hour, i see it all goes really wack every like 15-20 mins.. fwiw..

skuzzy would that suggest somethin like a failed piece of equipment resetting or something? there has been a hell of a snowstorm up here in the seattle/portland area..


(http://img380.imageshack.us/img380/8078/weirdtj3.jpg) (http://imageshack.us)
(http://img380.imageshack.us/img380/weirdtj3.jpg/1/w799.png) (http://g.imageshack.us/img380/weirdtj3.jpg/1/)
Title: Re: Comcast user connection issues
Post by: merc17` on December 19, 2008, 06:03:46 PM
Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/19/2008 4:00:54 PM

 1    7 ms  c-24-7-136-1.hsd1.ca.comcast.net [24.7.136.1]
 2   10 ms  ge-2-3-sr01.placerville.ca.sacra.comcast.net [68.87.213.201]
 3    8 ms  te-8-1-ar02.sacramento.ca.sacra.comcast.net [68.87.212.33]
 4    8 ms  te-9-3-ar01.sacramento.ca.sacra.comcast.net [68.87.212.5]
 5    9 ms  te-0-6-0-0-ar01.oakland.ca.sfba.comcast.net [68.86.143.25]
 6   12 ms  pos-0-2-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.90.141]
 7   15 ms  pos-0-14-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.85.181]
 8   15 ms  xe-11-0-0.edge1.SanJose1.Level3.net [4.79.43.137]
 9   15 ms  ae-33-89.car3.SanJose1.Level3.net [4.68.18.133]
10   17 ms  level3-gw.sffca.ip.att.net [192.205.33.81]
11   58 ms  tbr2.sffca.ip.att.net [12.122.86.38]
12   59 ms  cr2.sffca.ip.att.net [12.122.19.109]
13   56 ms  cr2.la2ca.ip.att.net [12.122.31.133]
14   57 ms  cr2.dlstx.ip.att.net [12.122.28.177]
15   58 ms  gar5.dlstx.ip.att.net [12.122.138.5]
16   59 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
17   57 ms  mdf1-bi8k-2-eth-2-6.dal1.attens.net [63.241.192.46]
18   58 ms  [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 58ms, Maximum = 58ms, Average = 58ms
Title: Re: Comcast user connection issues
Post by: Hungry on December 19, 2008, 06:09:06 PM
Just West of Chicago

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/19/2008 06:08:27 PM

 1   *       *       *       *       *       *       *       [-]
 2   13 ms   12 ms   12 ms   12 ms   12 ms   12 ms   13 ms  [68.85.131.33]
 3   12 ms   11 ms   14 ms   13 ms   12 ms   13 ms   16 ms  te-9-3-ar01.elmhurst.il.chicago.comcast.net [68.87.230.81]
 4   19 ms   14 ms   16 ms   16 ms   16 ms   16 ms   30 ms  ge-1-2-ar03.area4.il.chicago.comcast.net [68.87.230.237]
 5   38 ms   41 ms   46 ms   67 ms   37 ms   38 ms   41 ms  [68.86.90.49]
 6   39 ms   36 ms   37 ms   38 ms   36 ms   40 ms   50 ms  xe-9-3-0.edge1.Chicago2.Level3.net [4.71.248.21]
 7   37 ms   39 ms   37 ms   41 ms   41 ms   55 ms   38 ms  vlan51.ebr1.Chicago2.Level3.n et [4.69.138.158]
 8   47 ms   48 ms   47 ms   49 ms   42 ms   48 ms   45 ms  ae-6.ebr1.Chicago1.Level3.net [4.69.140.189]
 9   38 ms   37 ms   38 ms   38 ms   38 ms   37 ms   43 ms  ae-14-55.car4.Chicago1.Level3.net [4.68.101.136]
10   38 ms   39 ms   41 ms   42 ms   52 ms   40 ms   39 ms  [192.205.33.209]
11   *       *       *       *       *       *       *       [-]
12   *       *       *       *       *       *       *       [-]
13   *       *       *       *       *       *       *       [-]
14   *       *       *       *       *       *       *       [-]
15  309 ms  289 ms  282 ms  281 ms  262 ms  247 ms  228 ms  cr2.dlstx.ip.att.net [12.122.3.221]
16   *       *       *       *       *       *       *       [-]
17   *       *       *       *       *       *       *       [-]
18  304 ms  300 ms  290 ms  290 ms   *      269 ms  262 ms  mdf1-bi8k-2-eth-2-6.dal1.attens.net [63.241.192.46]
Title: Re: Comcast user connection issues
Post by: jamusta on December 19, 2008, 06:12:07 PM
ATL GA Here..

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\jam>tracert 206.16.60.38

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1    <1 ms     5 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3    11 ms    18 ms    11 ms  ge-1-5-ur02.c2jonesboro.ga.atlanta.comcast.net [
68.86.110.121]
  4    24 ms    13 ms     8 ms  te-9-4-ur01.c3riverdale.ga.atlanta.comcast.net [
68.86.106.89]
  5    11 ms     9 ms    13 ms  te-9-2-ur01.e1eastpoint.ga.atlanta.comcast.net [
68.86.106.85]
  6    11 ms     9 ms    13 ms  te-9-2-ur01.a5atlanta.ga.atlanta.comcast.net [68
.86.106.57]
  7    12 ms     9 ms     8 ms  te-9-4-ur01.a6atlanta.ga.atlanta.comcast.net [68
.86.106.21]
  8    13 ms     9 ms    13 ms  te-9-4-ar01.b0atlanta.ga.atlanta.comcast.net [68
.86.106.17]
  9    13 ms    10 ms    15 ms  te-0-1-0-4-cr01.atlanta.ga.ibone.comcast.net [68
.86.90.121]
 10    14 ms     9 ms    13 ms  te-4-3.car1.Atlanta2.Level3.net [4.71.252.25]
 11    14 ms    10 ms    13 ms  ae-18-51.car2.Atlanta4.Level3.net [4.68.103.13]

 12    31 ms    30 ms    31 ms  192.205.35.213
 13   131 ms   135 ms   127 ms  cr1.attga.ip.att.net [12.122.82.98]
 14   119 ms   117 ms   115 ms  cr2.dlstx.ip.att.net [12.122.28.174]
 15   109 ms   106 ms   107 ms  gar5.dlstx.ip.att.net [12.122.138.5]
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *       70 ms  206.16.60.38

Trace complete.

Title: Re: Comcast user connection issues
Post by: Yeager on December 19, 2008, 06:13:38 PM
Had a great connect last few days.  Today it is crap.  Oh well.....hope it does not last long.
Title: Re: Comcast user connection issues
Post by: HighGTrn on December 19, 2008, 06:41:45 PM
Sorry for the spam.  First one was a fat finger on IP.  Here's the correct report. 

Tracing route to 206.16.60.38 over a maximum of 30 hops



  1    <1 ms    <1 ms    <1 ms  192.168.1.1

  2     *        *        *     Request timed out.

  3     8 ms     7 ms     6 ms  68.85.147.1

  4     8 ms     7 ms     6 ms  te-8-4-ur02.manassascc.va.bad.comcast.net [68.87.128.190]

  5     8 ms     6 ms     7 ms  te-8-4-ur01.manassascc.va.bad.comcast.net [68.87.129.101]

  6     7 ms     9 ms     9 ms  te-1-4-ar01.manassascc.va.bad.comcast.net [68.87.129.89]

  7     9 ms     9 ms     9 ms  po-90-ar01.capitolhghts.md.bad.comcast.net [68.87.129.82]

  8    12 ms    11 ms    11 ms  68.85.130.122

  9    11 ms    11 ms    11 ms  te-3-3-ar01.plainfield.nj.panjde.comcast.net [68.86.90.34]

 10    12 ms    11 ms    11 ms  68.86.90.33

 11    13 ms    11 ms    11 ms  xe-9-0-0.edge1.Washington1.Level3.net [63.210.62.57]

 12    11 ms    11 ms    11 ms  ae-3-89.edge1.Washington3.Level3.net [4.68.17.139]

 13    12 ms    12 ms    14 ms  att-level3-oc192.Washington1.Level3.net [209.244.219.142]

 14    83 ms    84 ms    83 ms  tbr2.wswdc.ip.att.net [12.123.8.102]

 15    82 ms    83 ms    84 ms  cr2.wswdc.ip.att.net [12.122.16.117]

 16    84 ms    84 ms    83 ms  cr1.attga.ip.att.net [12.122.1.173]

 17    83 ms    83 ms    84 ms  cr2.dlstx.ip.att.net [12.122.28.174]

 18    82 ms    81 ms    81 ms  gar5.dlstx.ip.att.net [12.122.138.5]

 19    83 ms    83 ms    84 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]

 20    83 ms    83 ms    84 ms  mdf1-bi8k-1-eth-1-1.dal1.attens.net [63.241.192.250]

 21    85 ms    84 ms    84 ms  206.16.60.38



Trace complete.



Title: Re: Comcast user connection issues
Post by: drdeathx on December 19, 2008, 06:51:36 PM
(http://i435.photobucket.com/albums/qq77/AAdeath/333.jpg)
Title: Re: Comcast user connection issues
Post by: Nightmare on December 19, 2008, 06:53:12 PM
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\ACES>ping 206.16.60.38

Pinging 206.16.60.38 with 32 bytes of data:

Reply from 206.16.60.38: bytes=32 time=74ms TTL=237
Reply from 206.16.60.38: bytes=32 time=71ms TTL=237
Reply from 206.16.60.38: bytes=32 time=72ms TTL=237
Reply from 206.16.60.38: bytes=32 time=73ms TTL=237

Ping statistics for 206.16.60.38:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 71ms, Maximum = 74ms, Average = 72ms

C:\Documents and Settings\ACES>
Title: Re: Comcast user connection issues
Post by: Iucky on December 19, 2008, 06:54:12 PM
First couldnt logg on to game then , got in game for 15 min then lost connect, couldnt log on to htc web site for few min...
Target Name: 206.16.60.38.
         IP: 206.16.60.38
  Date/Time: 12/19/2008 4:36:12 PM to 12/19/2008 4:53:25 PM

Hop Sent Err  PL% Min Max Avg  Host Name / [IP]
 1   155   0  0.0   0   0   0  [192.168.0.1]
 2   155   0  0.0   5  72   9  [73.73.196.1]
 3   155   0  0.0   6  86   9  ge-2-25-ur01.sanmateo.ca.sfba.comcast.net [68.85.217.229]
 4   155   0  0.0   6  70   9  te-9-1-ur02.sanmateo.ca.sfba.comcast.net [68.87.192.18]
 5   155   0  0.0   8  80  12  te-0-3-0-5-ar01.oakland.ca.sfba.comcast.net [68.87.192.34]
 6   155   0  0.0  10  76  13  pos-0-4-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.90.137]
 7   155   0  0.0  13  83  16  pos-0-14-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.85.181]
 8   155   0  0.0  12 205  21  xe-10-3-0.edge1.SanJose1.Level3.net [4.71.118.5]
 9   155   0  0.0  14 228  33  ae-13-69.car3.SanJose1.Level3.net [4.68.18.5]
10   155   1  0.6  15 212  27  level3-gw.sffca.ip.att.net [192.205.33.81]
11   155  37 23.9  57 122  60  tbr2.sffca.ip.att.net [12.122.86.38]
12   155   0  0.0  57 281  73  cr2.sffca.ip.att.net [12.122.19.93]
13   155  37 23.9  57 127  60  cr2.la2ca.ip.att.net [12.122.31.133]
14   155  37 23.9  57 126  60  cr2.dlstx.ip.att.net [12.122.28.177]
15   155  43 27.7  56 178  65  gar5.dlstx.ip.att.net [12.122.138.5]
16   155  37 23.9  57 127  60  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
17   155  17 11.0  57 639  83  mdf1-bi8k-2-eth-2-1.dal1.attens.net [63.241.192.198]
18   155  37 23.9  57 122  60  [206.16.60.38]
Title: Re: Comcast user connection issues
Post by: shegotya on December 19, 2008, 06:54:50 PM
If I did this correctly here is mine ...

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.


C:\Documents and Settings\Aces High>ping 206.16.60.38

Pinging 206.16.60.38 with 32 bytes of data:

Reply from 206.16.60.38: bytes=32 time=73ms TTL=237
Reply from 206.16.60.38: bytes=32 time=73ms TTL=237
Reply from 206.16.60.38: bytes=32 time=71ms TTL=237
Reply from 206.16.60.38: bytes=32 time=74ms TTL=237

Ping statistics for 206.16.60.38:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 71ms, Maximum = 74ms, Average = 72ms

C:\Documents and Settings\Aces High>
Title: Re: Comcast user connection issues
Post by: Iucky on December 19, 2008, 06:55:44 PM
how can I post the image part of ping plotter?
Title: Re: Comcast user connection issues
Post by: 3lips on December 19, 2008, 06:58:19 PM
  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3    11 ms     9 ms    10 ms  ge-2-1-ur01.bayville.nj.panjde.comcast.net [68.8
6.221.25]
  4    12 ms    10 ms    12 ms  te-9-1-ur02.manahawkin.nj.panjde.comcast.net [68
.86.210.53]
  5    16 ms    11 ms     9 ms  te-9-1-ur01.manahawkin.nj.panjde.comcast.net [68
.86.158.169]
  6    18 ms    15 ms    12 ms  te-8-1-ar01.absecon.nj.panjde.comcast.net [68.86
.210.49]
  7    13 ms    15 ms    17 ms  be-30-crs01.audubon.nj.panjde.comcast.net [68.86
.208.22]
  8    18 ms    18 ms    16 ms  be-60-crs01.plainfield.nj.panjde.comcast.net [68
.86.208.1]
  9    20 ms    24 ms    26 ms  pos-0-3-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.90.25]
 10    16 ms    29 ms    16 ms  xe-11-3-0.edge1.NewYork2.Level3.net [4.71.186.5]

 11    16 ms    17 ms    16 ms  ae-23-79.car3.NewYork1.Level3.net [4.68.16.69]
 12    20 ms    31 ms    18 ms  att-level3-oc192.NewYork1.Level3.net [4.68.127.1
50]
 13    90 ms    92 ms    90 ms  tbr2.n54ny.ip.att.net [12.123.3.61]
 14    96 ms    93 ms    95 ms  cr2.n54ny.ip.att.net [12.122.16.205]
 15    96 ms    98 ms    95 ms  cr2.wswdc.ip.att.net [12.122.3.38]
 16    92 ms    89 ms    91 ms  cr1.attga.ip.att.net [12.122.1.173]
 17    91 ms    90 ms    91 ms  cr2.dlstx.ip.att.net [12.122.28.174]
 18    89 ms    88 ms    91 ms  gar5.dlstx.ip.att.net [12.122.138.5]
 19    90 ms    90 ms    98 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255
.82]
 20    92 ms    96 ms   104 ms  mdf1-bi8k-1-eth-1-3.dal1.attens.net [63.241.192.
206]
 21    93 ms    99 ms    94 ms  206.16.60.38

Trace complete.
Title: Re: Comcast user connection issues
Post by: Iucky on December 19, 2008, 07:00:04 PM
here is allitle more, I'm comcast west coast San fran bay area


Target Name: 206.16.60.38.
         IP: 206.16.60.38
  Date/Time: 12/19/2008 4:36:12 PM to 12/19/2008 4:53:25 PM

Hop Sent Err  PL% Min Max Avg  Host Name / [IP]
 1   155   0  0.0   0   0   0  [192.168.0.1]
 2   155   0  0.0   5  72   9  [73.73.196.1]
 3   155   0  0.0   6  86   9  ge-2-25-ur01.sanmateo.ca.sfba.comcast.net [68.85.217.229]
 4   155   0  0.0   6  70   9  te-9-1-ur02.sanmateo.ca.sfba.comcast.net [68.87.192.18]
 5   155   0  0.0   8  80  12  te-0-3-0-5-ar01.oakland.ca.sfba.comcast.net [68.87.192.34]
 6   155   0  0.0  10  76  13  pos-0-4-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.90.137]
 7   155   0  0.0  13  83  16  pos-0-14-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.85.181]
 8   155   0  0.0  12 205  21  xe-10-3-0.edge1.SanJose1.Level3.net [4.71.118.5]
 9   155   0  0.0  14 228  33  ae-13-69.car3.SanJose1.Level3.net [4.68.18.5]
10   155   1  0.6  15 212  27  level3-gw.sffca.ip.att.net [192.205.33.81]
11   155  37 23.9  57 122  60  tbr2.sffca.ip.att.net [12.122.86.38]
12   155   0  0.0  57 281  73  cr2.sffca.ip.att.net [12.122.19.93]
13   155  37 23.9  57 127  60  cr2.la2ca.ip.att.net [12.122.31.133]
14   155  37 23.9  57 126  60  cr2.dlstx.ip.att.net [12.122.28.177]
15   155  43 27.7  56 178  65  gar5.dlstx.ip.att.net [12.122.138.5]
16   155  37 23.9  57 127  60  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
17   155  17 11.0  57 639  83  mdf1-bi8k-2-eth-2-1.dal1.attens.net [63.241.192.198]
18   155  37 23.9  57 122  60  [206.16.60.38]
Host Information
1, -------------- ,192.168.0.1
2, -------------- ,73.73.196.1
3,ge-2-25-ur01.sanmateo.ca.sfba.comcast.net,68.85.217.229
4,te-9-1-ur02.sanmateo.ca.sfba.comcast.net,68.87.192.18
5,te-0-3-0-5-ar01.oakland.ca.sfba.comcast.net,68.87.192.34
6,pos-0-4-0-0-cr01.sacramento.ca.ibone.comcast.net,68.86.90.137
7,pos-0-14-0-0-cr01.sacramento.ca.ibone.comcast.net,68.86.85.181
8,xe-10-3-0.edge1.SanJose1.Level3.net,4.71.118.5
9,ae-13-69.car3.SanJose1.Level3.net,4.68.18.5
10,level3-gw.sffca.ip.att.net,192.205.33.81
11,tbr2.sffca.ip.att.net,12.122.86.38
12,cr2.sffca.ip.att.net,12.122.19.93
13,cr2.la2ca.ip.att.net,12.122.31.133
14,cr2.dlstx.ip.att.net,12.122.28.177
15,gar5.dlstx.ip.att.net,12.122.138.5
16,mdf1-gsr12-1-pos-7-0.dal1.attens.net,12.122.255.82
17,mdf1-bi8k-2-eth-2-1.dal1.attens.net,63.241.192.198
18, -------------- ,206.16.60.38

Sample Information
"12/19/2008 4:36:12 PM",0,15,9,12,17,13,22,19,21,18,62,64,60,63,147,62,60,70
"12/19/2008 4:36:27 PM",0,8,8,8,10,15,20,15,17,17,73,61,59,58,59,59,58,59
"12/19/2008 4:36:42 PM",0,7,8,9,17,16,17,17,17,17,58,58,58,59,57,66,68,60
"12/19/2008 4:36:57 PM",0,8,10,7,13,14,17,15,17,16,61,66,58,58,60,57,58,59
"12/19/2008 4:37:15 PM",N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A
"12/19/2008 4:37:15 PM",N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A
"12/19/2008 4:37:25 PM",0,10,17,8,10,11,19,35,17,17,63,64,62,60,57,60,58,60
"12/19/2008 4:40:55 PM",N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A
"12/19/2008 4:40:56 PM",N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A
"12/19/2008 4:41:00 PM",0,6,6,7,9,11,16,12,202,15,58,58,57,59,56,58,65,80
"12/19/2008 4:41:05 PM",0,6,8,10,9,12,16,18,51,18,57,59,58,67,57,59,58,64
"12/19/2008 4:41:10 PM",0,7,6,7,10,15,14,36,15,17,58,61,60,62,65,60,59,61
"12/19/2008 4:41:15 PM",0,7,8,7,10,12,27,15,16,17,57,59,58,59,57,61,*,58
"12/19/2008 4:41:20 PM",0,8,7,8,10,10,17,16,17,19,59,58,57,60,57,61,59,58
"12/19/2008 4:41:25 PM",0,14,12,7,9,12,16,14,16,17,58,57,59,60,62,59,58,69
"12/19/2008 4:41:30 PM",0,11,10,8,12,14,16,14,16,15,62,61,57,58,61,58,57,61
"12/19/2008 4:41:35 PM",0,9,7,6,11,11,17,20,17,16,59,60,57,60,59,60,58,60
"12/19/2008 4:41:40 PM",0,9,7,7,13,14,14,14,14,151,62,60,57,62,*,68,58,61
"12/19/2008 4:41:45 PM",0,10,8,7,9,24,16,16,18,16,58,62,59,58,63,61,59,61
"12/19/2008 4:41:50 PM",0,8,10,7,11,12,14,13,19,16,60,58,63,59,59,60,*,60
"12/19/2008 4:41:55 PM",0,8,6,6,10,14,14,15,19,16,57,60,58,59,57,57,57,60
"12/19/2008 4:42:00 PM",0,12,8,6,10,12,14,15,15,15,59,60,58,61,59,59,59,59
"12/19/2008 4:42:05 PM",0,16,8,10,11,14,15,13,17,18,65,63,57,69,59,64,59,60
"12/19/2008 4:42:10 PM",0,9,6,8,10,12,24,13,136,16,58,57,59,61,57,58,57,57
"12/19/2008 4:42:15 PM",0,8,7,7,11,11,15,15,15,21,59,58,62,59,56,61,57,58
"12/19/2008 4:42:20 PM",0,7,6,6,9,13,14,14,16,20,57,59,59,57,61,59,59,57
"12/19/2008 4:42:25 PM",0,8,8,17,13,17,16,28,15,17,60,57,63,57,68,58,60,58
"12/19/2008 4:42:30 PM",0,7,8,10,13,12,17,62,19,15,60,58,62,60,65,59,59,61
"12/19/2008 4:42:35 PM",0,11,11,11,9,16,14,15,15,18,59,58,58,60,57,58,*,57
"12/19/2008 4:42:40 PM",0,8,22,8,14,11,16,87,16,19,58,58,58,70,60,62,58,62
"12/19/2008 4:42:45 PM",0,8,6,8,11,12,14,18,16,161,61,61,69,58,66,78,60,70
"12/19/2008 4:42:50 PM",0,9,6,6,14,13,16,15,15,18,59,58,62,57,59,58,57,59
"12/19/2008 4:42:55 PM",0,8,8,8,28,14,14,13,17,17,60,58,57,58,59,59,58,70
"12/19/2008 4:43:00 PM",0,6,12,7,17,13,17,14,193,84,61,59,57,59,56,58,59,58
"12/19/2008 4:43:05 PM",0,7,6,6,9,11,16,16,15,17,58,71,58,68,57,58,*,58
"12/19/2008 4:43:10 PM",0,7,6,9,9,12,16,15,15,16,58,58,60,58,58,58,59,61
"12/19/2008 4:43:15 PM",0,7,7,6,9,12,16,14,116,17,58,60,59,58,59,59,58,57
"12/19/2008 4:43:20 PM",0,9,20,11,27,13,14,15,15,16,*,175,*,*,*,*,212,*
"12/19/2008 4:43:25 PM",0,7,7,9,10,13,17,14,15,16,*,274,*,*,*,*,246,*
"12/19/2008 4:43:30 PM",0,24,86,52,75,76,83,84,74,35,*,278,*,*,*,*,279,*
"12/19/2008 4:43:35 PM",0,9,6,6,9,13,14,15,15,17,*,279,*,*,*,*,280,*
"12/19/2008 4:43:40 PM",0,8,7,8,9,13,15,15,16,17,*,281,*,*,*,*,639,*
"12/19/2008 4:43:45 PM",0,6,8,8,16,13,17,13,16,17,*,274,*,*,*,*,277,*
"12/19/2008 4:43:50 PM",0,6,9,6,10,11,17,14,19,173,*,262,*,*,*,*,254,*
"12/19/2008 4:43:55 PM",0,7,7,7,9,19,14,15,15,25,*,242,*,*,*,*,230,*
"12/19/2008 4:44:00 PM",0,6,11,19,12,11,16,15,16,15,*,217,*,*,*,*,198,*
"12/19/2008 4:44:05 PM",0,11,8,8,12,13,25,15,34,20,*,189,*,*,*,*,164,*
"12/19/2008 4:44:10 PM",0,8,9,6,12,11,16,17,19,17,*,157,*,*,*,*,122,*
"12/19/2008 4:44:15 PM",0,6,8,7,12,11,15,17,19,17,*,113,*,*,*,*,75,*
"12/19/2008 4:44:20 PM",0,7,6,8,10,12,15,19,29,17,*,69,*,*,*,*,58,*
"12/19/2008 4:44:25 PM",0,7,7,8,9,22,14,14,15,17,*,58,*,*,*,*,60,*
"12/19/2008 4:44:30 PM",0,5,7,8,10,13,14,16,15,27,*,58,*,*,*,*,59,*
"12/19/2008 4:44:35 PM",0,7,7,8,9,12,15,15,20,17,*,58,*,*,*,*,58,*
"12/19/2008 4:44:40 PM",0,7,9,7,10,13,15,15,70,20,*,58,*,*,*,*,59,*
"12/19/2008 4:44:45 PM",0,5,7,6,12,13,17,16,19,45,*,59,*,*,*,*,59,*
"12/19/2008 4:44:50 PM",0,6,6,7,14,11,16,62,15,23,*,58,*,*,*,*,123,*
"12/19/2008 4:44:55 PM",0,6,8,8,10,15,15,13,16,180,*,58,*,*,*,*,58,*
"12/19/2008 4:45:00 PM",0,5,7,6,10,13,15,15,21,17,*,58,*,*,*,*,61,*
"12/19/2008 4:45:05 PM",0,7,10,6,9,11,15,16,16,19,*,59,*,*,*,*,507,*
"12/19/2008 4:45:10 PM",0,5,7,8,11,12,17,16,15,17,*,58,*,*,*,*,312,*
"12/19/2008 4:45:15 PM",0,6,8,11,9,13,15,14,26,16,*,59,*,*,*,*,60,*
"12/19/2008 4:45:20 PM",0,13,8,9,10,11,17,13,15,16,*,59,*,*,*,*,61,*
"12/19/2008 4:45:25 PM",0,6,9,7,9,11,13,15,182,18,*,58,*,*,*,*,58,*
"12/19/2008 4:45:30 PM",0,8,7,6,10,10,15,20,160,16,*,60,*,*,*,*,311,*
"12/19/2008 4:45:35 PM",0,7,9,6,8,10,15,15,15,17,*,60,*,*,*,*,59,*
"12/19/2008 4:45:40 PM",0,18,11,7,11,14,15,41,16,16,*,59,*,*,*,*,59,*
"12/19/2008 4:45:45 PM",0,8,7,6,10,12,14,14,18,18,*,62,*,*,*,*,58,*
"12/19/2008 4:45:50 PM",0,24,13,6,11,11,14,13,35,15,*,62,*,*,*,*,68,*
"12/19/2008 4:45:55 PM",0,6,6,7,10,12,13,14,14,16,*,59,*,*,*,*,72,*
"12/19/2008 4:46:00 PM",0,8,6,7,9,12,14,14,14,196,*,59,*,*,*,*,58,*
"12/19/2008 4:46:05 PM",0,9,6,7,9,13,15,20,15,18,*,59,*,*,*,*,58,*
"12/19/2008 4:46:10 PM",0,7,6,7,9,12,14,13,17,18,*,58,*,*,*,*,58,*
"12/19/2008 4:46:15 PM",0,7,7,7,20,11,15,15,113,*,*,59,*,*,*,*,60,*
"12/19/2008 4:46:20 PM",0,7,8,6,9,11,14,13,15,15,*,59,*,*,*,*,59,*
"12/19/2008 4:46:25 PM",0,6,6,7,9,12,13,16,17,17,59,63,58,58,107,57,61,59
"12/19/2008 4:46:30 PM",0,7,8,6,8,13,15,15,16,16,59,58,59,57,58,57,58,59
Title: Re: Comcast user connection issues
Post by: CRYPTIC on December 19, 2008, 07:02:28 PM

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     9 ms     9 ms     9 ms  ge-2-1-ur01.bayville.nj.panjde.comcast.net [68.8
6.221.25]
  4    13 ms     9 ms    11 ms  te-9-1-ur02.manahawkin.nj.panjde.comcast.net [68
.86.210.53]
  5    13 ms     9 ms    10 ms  te-9-1-ur01.manahawkin.nj.panjde.comcast.net [68
.86.158.169]
  6    12 ms    11 ms    11 ms  te-8-1-ar01.absecon.nj.panjde.comcast.net [68.86
.210.49]
  7    43 ms    14 ms    14 ms  be-30-crs01.audubon.nj.panjde.comcast.net [68.86
.208.22]
  8    18 ms    17 ms    32 ms  be-60-crs01.plainfield.nj.panjde.comcast.net [68
.86.208.1]
  9    16 ms    18 ms    20 ms  pos-0-5-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.90.29]
 10    17 ms    20 ms    19 ms  xe-11-0-0.edge1.NewYork2.Level3.net [4.71.186.1]

 11    16 ms    18 ms    17 ms  ae-13-69.car3.NewYork1.Level3.net [4.68.16.5]
 12    24 ms    23 ms    20 ms  192.205.33.93
 13    97 ms    99 ms    93 ms  tbr2.n54ny.ip.att.net [12.123.3.110]
 14    91 ms    94 ms    90 ms  cr2.n54ny.ip.att.net [12.122.16.141]
 15    91 ms    91 ms    91 ms  cr2.wswdc.ip.att.net [12.122.3.38]
 16    92 ms    91 ms    96 ms  cr1.attga.ip.att.net [12.122.1.173]
 17    99 ms    96 ms    93 ms  cr2.dlstx.ip.att.net [12.122.28.174]
 18    90 ms    90 ms    93 ms  gar5.dlstx.ip.att.net [12.122.138.5]
 19    92 ms    90 ms    91 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255
.82]
 20    94 ms    92 ms    91 ms  mdf1-bi8k-1-eth-1-1.dal1.attens.net [63.241.192.
250]
 21    91 ms    91 ms    95 ms  206.16.60.38

Trace complete
Title: Re: Comcast user connection issues
Post by: gameofd1 on December 19, 2008, 07:25:13 PM
i don't know how to do the ping but i got disco'd over 20 times today in the NW
Title: Re: Comcast user connection issues
Post by: ten367th on December 19, 2008, 07:36:54 PM
just don't understand if comcast problem why every thing else on the net works just find. I'm not a computer person so not able to do much but log on. looks like no flying for a while.
Title: Re: Comcast user connection issues
Post by: carhint on December 19, 2008, 07:37:35 PM
I'm having issues as well. Called Comcast and was told that since World of War Craft was reporting problems that if I opened a ticket on the HTC problem that I would get charged a fee!!!! :furious :furious :furious

I guess they think that all game sites are the same.

Neat way to keep their stats on customer problems down though.
Title: Re: Comcast user connection issues
Post by: ImADot on December 19, 2008, 07:37:55 PM
Up until yesterday, I've had no issues.  Today, disco'd after 2 minutes and had heck of a time with the BBS.

PingPlot shows problem with ATT section:

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/19/2008 7:34:06 PM to 12/19/2008 7:36:22 PM

 1    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms  [192.168.1.1]
 2    5 ms    7 ms    8 ms    6 ms   15 ms    9 ms    6 ms    6 ms   10 ms    5 ms  [73.205.44.1]
 3    7 ms    7 ms    8 ms    7 ms    9 ms    8 ms   23 ms    6 ms   12 ms    7 ms  ge-4-1-ur01.crosstown.mn.minn.comcast.net [68.85.164.1]
 4    8 ms    8 ms    7 ms    8 ms   10 ms    9 ms    6 ms    8 ms   11 ms    6 ms  te-0-1-0-5-ar02.crosstown.mn.minn.comcast.net [68.86.232.1]
 5   10 ms    9 ms   11 ms    7 ms   10 ms   10 ms    9 ms   13 ms   10 ms    8 ms  [68.87.174.217]
 6   18 ms   16 ms   17 ms   18 ms   21 ms   19 ms   19 ms   16 ms   20 ms   17 ms  te-0-2-0-5-cr01.chicago.il.ibone.comcast.net [68.86.91.141]
 7   37 ms   17 ms   17 ms   16 ms   21 ms   50 ms   18 ms   17 ms   18 ms   16 ms  xe-9-2-0.edge1.Chicago2.Level3.net [4.71.248.25]
 8   18 ms   18 ms   21 ms   21 ms   20 ms   19 ms   23 ms   17 ms   16 ms   21 ms  vlan51.ebr1.Chicago2.Level3.n et [4.69.138.158]
 9   27 ms   27 ms   26 ms   25 ms   26 ms   25 ms   22 ms   20 ms   19 ms   21 ms  ae-6.ebr1.Chicago1.Level3.net [4.69.140.189]
10   20 ms   19 ms   17 ms   24 ms   26 ms  166 ms   22 ms   22 ms   24 ms   20 ms  ae-14-55.car4.Chicago1.Level3.net [4.68.101.136]
11   21 ms   21 ms   18 ms   19 ms   19 ms   21 ms   20 ms  126 ms   18 ms   18 ms  [192.205.33.209]
12   79 ms   77 ms   79 ms   76 ms   77 ms   79 ms   80 ms   77 ms   78 ms   81 ms  tbr2.cgcil.ip.att.net [12.123.6.70]
13   *       *       77 ms   77 ms   78 ms   79 ms   77 ms   77 ms   76 ms   80 ms  cr2.cgcil.ip.att.net [12.122.17.229]
14   78 ms   78 ms   82 ms   78 ms   77 ms   79 ms   76 ms   77 ms   78 ms   81 ms  cr2.sl9mo.ip.att.net [12.122.2.22]
15   *       *       82 ms   76 ms   78 ms   77 ms   76 ms   77 ms   75 ms   79 ms  cr2.kc9mo.ip.att.net [12.122.28.89]
16   *       *       78 ms   77 ms   76 ms   78 ms   81 ms   76 ms   76 ms   77 ms  cr1.dlstx.ip.att.net [12.122.28.85]
17   76 ms   77 ms   77 ms   76 ms   77 ms   77 ms   75 ms   76 ms   76 ms   78 ms  gar5.dlstx.ip.att.net [12.122.139.5]
18   *       *       78 ms   79 ms   79 ms   79 ms   78 ms   78 ms   76 ms   87 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
19   *       *       77 ms   79 ms   77 ms  435 ms   78 ms   77 ms   79 ms   90 ms  mdf1-bi8k-1-eth-1-2.dal1.attens.net [63.241.192.202]
20   *       *       76 ms   76 ms   85 ms   78 ms   77 ms   78 ms   77 ms   78 ms  [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 10, Received = 8, Lost = 2 (20.0%)
Round Trip Times: Minimum = 76ms, Maximum = 85ms, Average = 78ms

Title: Re: Comcast user connection issues
Post by: woolyb on December 19, 2008, 07:39:25 PM
I am also a comcast user from PA. I have been having problems all day. Lost TCP switching to UDP and then disco. Then I can't even access the AH website. It's gotten worse as the day has progressed. Here are my trace route results:

Host Information
1, -------------- ,192.168.1.1
2, -------------- ,73.155.227.1
3,ge-6-3-ur01.pottsville.pa.panjde.comcast.net,68.86.154.205
4,ge-9-24-ur01.pinegrove.pa.panjde.comcast.net,68.86.208.241
5,ge-2-24-ur01.lebanon.pa.panjde.comcast.net,68.86.208.237
6,te-9-1-ur01.hershey.pa.panjde.comcast.net,68.86.208.205
7, -------------- ,68.85.158.21
8, -------------- ,68.85.158.17
9,te-8-1-ar01.lowerpaxton.pa.panjde.comcast.net,68.86.208.193
10,be-60-crs01.ivyland.pa.panjde.comcast.net,68.86.208.46
11,be-40-crs01.401nbroadst.pa.panjde.comcast.net,68.86.208.33
12,pos-0-5-0-0-cr01.philadelphia.pa.ibone.comcast.net,68.86.90.13
13,ge-4-0-142.ipcolo2.Washington1.Level3.net,63.210.62.33
14,ae-1-69.edge1.Washington3.Level3.net,4.68.17.11
15,att-level3-oc192.Washington1.Level3.net,209.244.219.142
16,tbr2.wswdc.ip.att.net,12.123.8.102
17,cr2.wswdc.ip.att.net,12.122.16.69
18,cr1.attga.ip.att.net,12.122.1.173
19,cr2.dlstx.ip.att.net,12.122.28.174
20,gar5.dlstx.ip.att.net,12.122.138.5
21,mdf1-gsr12-1-pos-6-0.dal1.attens.net,12.122.255.78
22,mdf1-bi8k-2-eth-2-2.dal1.attens.net,63.241.192.218
23, -------------- ,206.16.60.38

Sample Information
"12/19/2008 8:17:08 PM",1,12,8,20,13,9,10,20,10,12,14,28,22,28,N/A,92,90,91,95,90,92,91,92
"12/19/2008 8:19:08 PM",1,8,9,9,9,10,10,9,10,17,15,20,18,28,N/A,92,92,98,91,90,89,246,92
"12/19/2008 8:21:08 PM",1,8,8,10,10,9,11,10,12,13,16,20,19,23,32,94,91,91,91,91,92,99,93
"12/19/2008 8:23:08 PM",1,6,9,9,9,9,9,8,13,13,17,17,21,20,21,91,88,92,90,90,99,100,92
"12/19/2008 8:25:08 PM",1,7,11,8,9,8,10,12,10,16,19,26,18,20,22,93,89,92,91,88,89,92,91
"12/19/2008 8:27:08 PM",5,9,10,10,10,10,9,10,12,15,15,35,24,21,22,101,91,91,92,89,92,92,92
Title: Re: Comcast user connection issues
Post by: Bino on December 19, 2008, 07:41:04 PM
Skuzzy, just FYI...

I connect via an Optimum Online cable modem from Granite Springs, New York.  I'm about 50 miles north of NYC.

Here is a link to a PingPlotter screen capture (http://tinyurl.com/4ggp7r)

Level3 is the badguy here, too.  :mad:

Title: Re: Comcast user connection issues
Post by: drdeathx on December 19, 2008, 07:48:56 PM
Info for Skuzzy,

Hops 10 and above are fluctuating. Stable except every 10 min or so jumps to about 300-400 briefly. Comcast tech said world of war was having same problem and he said verizon too.That info may or may not be accurate seeing he works for comcast. My level 3 is same as my last week post and has not changed. Actually all IP addys are the same. I am wondering if hop 14 may be the culprit.

Did yall call comcast to complain???? I did and insist they report it. My tech was under the assumption they knew.


Last week:
(http://i435.photobucket.com/albums/qq77/AAdeath/untitled.jpg)

today:
(http://i435.photobucket.com/albums/qq77/AAdeath/4444.jpg)
Title: Re: Comcast user connection issues
Post by: shegotya on December 19, 2008, 07:50:24 PM
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Aces High>tracert 206.16.60.38

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1     3 ms     1 ms    <1 ms  wr850g.hsd1.in.comcast.net [192.168.10.1]
  2     *        *        *     Request timed out.
  3     9 ms     7 ms     9 ms  68.85.131.73
  4     7 ms     7 ms     9 ms  te-8-3-ur02.hammond.in.chicago.comcast.net [68.8
7.230.150]
  5     9 ms     9 ms     9 ms  te-9-1-ar01.area4.il.chicago.comcast.net [68.87.
230.153]
  6    32 ms    30 ms    31 ms  68.86.90.49
  7    30 ms    30 ms    31 ms  xe-10-3-0.edge1.Chicago2.Level3.net [4.71.248.9]

  8    33 ms    32 ms    31 ms  vlan52.ebr2.Chicago2.Level3.n et [4.69.138.190]
  9    39 ms    36 ms    36 ms  ae-5.ebr2.Chicago1.Level3.net [4.69.140.193]
 10    32 ms    30 ms    31 ms  ae-24-52.car4.Chicago1.Level3.net [4.68.101.40]

 11    32 ms    31 ms    30 ms  192.205.33.185
 12   160 ms   159 ms   158 ms  tbr2.cgcil.ip.att.net [12.123.6.26]
 13   145 ms   142 ms   143 ms  cr2.cgcil.ip.att.net [12.122.17.221]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *       75 ms    72 ms  206.16.60.38

Trace complete.

C:\Documents and Settings\Aces High>
Title: Re: Comcast user connection issues
Post by: StokesAk on December 19, 2008, 07:52:58 PM
So how long do you think until this problem can be solved,is comcast doing anything to help?   :mad:  :mad:  :mad:  :mad:
Title: Re: Comcast user connection issues
Post by: gameofd1 on December 19, 2008, 08:04:45 PM
Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/19/2008 9:01:12 PM to 12/19/2008 9:03:56 PM

Hop Sent Err   PL% Min Max Avg  Host Name / [IP]
 1    12  12 100.0   0   0   0   [-]
 2    12   0   0.0   6  32  10  ge-2-19-ur01.punxy.pa.pitt.comcast.net [68.86.146.193]
 3    12   0   0.0   8  23  13  te-9-1-ur01.ruralvalley.pa.pitt.comcast.net [68.86.100.122]
 4    12   0   0.0  11  20  13  te-6-4-ar01.pittsburgh.pa.pitt.comcast.net [68.86.100.182]
 5    12   0   0.0  13  19  16  te-0-4-0-4-cr01.cleveland.oh.ibone.comcast.net [68.86.90.97]
 6    12   0   0.0  20  31  23  pos-0-6-0-0-cr01.mclean.va.ibone.comcast.net [68.86.85.41]
 7    12   0   0.0  23  56  27  xe-8-3-0.edge1.Washington1.Level3.net [63.210.62.49]
 8    12   0   0.0  20  39  24  ae-2-79.edge1.Washington3.Level3.net [4.68.17.75]
 9     7   0   0.0  24  38  30  att-level3-oc192.Washington1.Level3.net [209.244.219.142]
10     1   0   0.0  92  92  92  tbr2.wswdc.ip.att.net [12.123.8.118]
11     1   0   0.0 104 104 104  cr2.wswdc.ip.att.net [12.122.16.69]
12     1   0   0.0  94  94  94  cr1.attga.ip.att.net [12.122.1.173]
13     1   0   0.0 112 112 112  cr2.dlstx.ip.att.net [12.122.28.174]
14    12   0   0.0  95 226 111  gar5.dlstx.ip.att.net [12.122.138.5]
15     1   0   0.0  94  94  94  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
16     1   0   0.0  94  94  94  mdf1-bi8k-2-eth-2-2.dal1.attens.net [63.241.192.218]
17    12  11  91.7  95  95  95  [206.16.60.38]
Title: Re: Comcast user connection issues
Post by: WxMan on December 19, 2008, 08:07:00 PM
Logged in the game with just enough time to read the MOD then disconnected.


C:\Documents and Settings\Dan>tracert 206.16.60.38

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3    10 ms     9 ms     9 ms  ge-2-1-ur01.canonsburg.pa.pitt.comcast.net [68.8
6.147.93]
  4    11 ms    15 ms    14 ms  te-8-1-ur01.wheeling.wv.pitt.comcast.net [68.86.
100.29]
  5    12 ms    12 ms    11 ms  te-8-1-ur01.stclairsvill.oh.pitt.comcast.net [68
.86.100.25]
  6    14 ms    14 ms    14 ms  te-8-1-ur01.steubenville.oh.pitt.comcast.net [68
.86.100.21]
  7    17 ms    14 ms    14 ms  te-8-1-ur01.eliverpool.oh.pitt.comcast.net [68.8
6.100.17]
  8    16 ms    15 ms    14 ms  te-8-1-ur01.beaverfalls.pa.pitt.comcast.net [68.
86.100.13]
  9    16 ms    16 ms    16 ms  68.87.173.13
 10    20 ms    26 ms    22 ms  te-0-4-0-4-cr01.cleveland.oh.ibone.comcast.net [
68.86.90.97]
 11    26 ms    26 ms    28 ms  pos-0-7-0-0-cr01.mclean.va.ibone.comcast.net [68
.86.85.45]
 12    29 ms    80 ms    29 ms  ge-5-1-125.ipcolo1.Washington1.Level3.net [63.21
0.62.157]
 13    29 ms    28 ms    26 ms  ae-1-69.edge1.Washington3.Level3.net [4.68.17.11
]
 14    28 ms    31 ms    29 ms  att-level3-oc192.Washington1.Level3.net [209.244
.219.142]
 15   100 ms   101 ms   100 ms  tbr2.wswdc.ip.att.net [12.123.8.118]
 16   102 ms    99 ms   103 ms  cr2.wswdc.ip.att.net [12.122.16.85]
 17   106 ms    98 ms    98 ms  cr1.attga.ip.att.net [12.122.1.173]
 18   109 ms   101 ms   101 ms  cr2.dlstx.ip.att.net [12.122.28.174]
 19    98 ms    96 ms   115 ms  gar5.dlstx.ip.att.net [12.122.138.5]
 20   107 ms   100 ms   100 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255
.82]
 21   101 ms   101 ms    98 ms  mdf1-bi8k-1-eth-1-4.dal1.attens.net [63.241.192.
42]
 22   106 ms   102 ms   103 ms  206.16.60.38

Trace complete.

C:\Documents and Settings\Dan>
Title: Re: Comcast user connection issues
Post by: Shuffler on December 19, 2008, 08:12:00 PM
Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/19/2008 8:09:30 PM to 12/19/2008 8:11:45 PM

 1   24 ms   18 ms   14 ms    9 ms   16 ms    2 ms   16 ms    8 ms    4 ms    2 ms  [192.168.1.1]
 2    9 ms    7 ms    7 ms   10 ms    8 ms    8 ms    8 ms    8 ms   11 ms    8 ms  [192.168.1.1]
 3    9 ms    9 ms    9 ms    9 ms    9 ms    8 ms    9 ms    9 ms    9 ms   11 ms  ge-2-26-ur01.northshore.tx.houston.comcast.net [68.85.248.237]
 4    9 ms   10 ms    9 ms    7 ms   10 ms   10 ms    9 ms   18 ms    9 ms    8 ms  te-8-1-ur02.northshore.tx.houston.comcast.net [68.85.244.186]
 5    9 ms   11 ms    9 ms    9 ms   19 ms   11 ms    9 ms   11 ms    9 ms   13 ms  te-8-1-ur01.wallisville.tx.houston.comcast.net [68.85.244.181]
 6   10 ms   10 ms   12 ms   12 ms   11 ms   11 ms   11 ms   *       11 ms   11 ms  te-9-3-ar02.royalton.tx.houston.comcast.net [68.85.244.137]
 7   12 ms   11 ms   12 ms   11 ms   13 ms   11 ms   11 ms   11 ms   12 ms   13 ms  po-17-ar02.greenspoint.tx.houston.comcast.net [68.85.244.130]
 8   19 ms   16 ms   16 ms   16 ms   17 ms   17 ms   17 ms   16 ms   19 ms   17 ms  te-0-4-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.91.49]
 9   17 ms   17 ms   17 ms   17 ms   19 ms   17 ms   18 ms   17 ms   16 ms   15 ms  xe-11-3-0.edge3.Dallas1.Level3.net [4.71.198.9]
10   18 ms   18 ms   18 ms   16 ms   17 ms   24 ms   17 ms   16 ms   17 ms   16 ms  ae-3-89.edge2.Dallas3.Level3.net [4.68.19.140]
11   56 ms   *       61 ms   50 ms   52 ms   61 ms   56 ms   54 ms   51 ms   51 ms  [192.205.35.141]
12   52 ms   52 ms   54 ms   60 ms   61 ms   *       *       51 ms   52 ms   52 ms  tbr1.dlstx.ip.att.net [12.123.16.202]
13   51 ms   52 ms   52 ms   *       *       52 ms   52 ms   51 ms   52 ms   54 ms  cr1.dlstx.ip.att.net [12.122.18.137]
14   51 ms   52 ms   51 ms   53 ms   51 ms   52 ms   52 ms   61 ms   52 ms  N/A     gar5.dlstx.ip.att.net [12.122.139.5]
15   53 ms   *       53 ms   53 ms   51 ms   53 ms   61 ms   *       51 ms   51 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
16   52 ms   52 ms   52 ms   52 ms   52 ms   52 ms   *       52 ms   54 ms   50 ms  mdf1-bi8k-1-eth-1-2.dal1.attens.net [63.241.192.202]
17   52 ms   52 ms   52 ms   51 ms   51 ms   53 ms   55 ms   53 ms   51 ms   51 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 = 51ms, Maximum = 55ms, Average = 52ms

AT&T phone service has never been any good in the Houston area. I do not know about their cable.
Comcast took over from Roadrunner and when they started making changes everything slowed down. Roadrunner was so much better.
Title: Re: Comcast user connection issues
Post by: 4XTCH on December 19, 2008, 08:19:12 PM
Well, As A CM and I'm Hosting FSO for tonight ..... SKUZZY HELP!!!!!

4XTCH


Target Name: 206.16.60.38.
         IP: 206.16.60.38
  Date/Time: 12/19/2008 8:15:51 PM

 1    1 ms    1 ms    1 ms  c-69-246-223-158.hsd1.il.comcast.net [69.246.223.158]
 2   *       *       *       [-]
 3    9 ms    8 ms    8 ms  [68.87.208.105]
 4   10 ms    8 ms    8 ms  te-8-4-ur01.mtprospect.il.chicago.comcast.net [68.87.231.73]
 5   10 ms    8 ms   10 ms  te-8-2-ur01.algonquin.il.chicago.comcast.net [68.87.230.21]
 6   11 ms    9 ms    9 ms  te-2-1-ar02.elmhurst.il.chicago.comcast.net [68.87.230.17]
 7   14 ms   14 ms   13 ms  [68.87.229.109]
 8   16 ms   15 ms   15 ms  [68.86.90.49]
 9   14 ms   99 ms   15 ms  xe-9-2-0.edge1.Chicago2.Level3.net [4.71.248.25]
10   16 ms   13 ms   13 ms  vlan52.ebr2.Chicago2.Level3.n et [4.69.138.190]
11   20 ms   13 ms   17 ms  ae-5.ebr2.Chicago1.Level3.net [4.69.140.193]
12   17 ms   14 ms   15 ms  ae-24-56.car4.Chicago1.Level3.net [4.68.101.168]
13   16 ms   14 ms   15 ms  [192.205.33.185]
14   *       *       *       [-]
15   *       *       *       [-]
16   *       *       *       [-]
17  162 ms   85 ms   77 ms  cr2.kc9mo.ip.att.net [12.122.28.89]
18   77 ms   78 ms   79 ms  cr1.dlstx.ip.att.net [12.122.28.85]
19  160 ms   77 ms   78 ms  gar5.dlstx.ip.att.net [12.122.139.5]
20   *       *       *       [-]
21   *       *       *       [-]
22   82 ms   84 ms   79 ms  [206.16.60.38]

Ping statistics for 206.16.60.38.
Packets: Sent = 3, Received = 3, Lost = 0 (0.0%)
Round Trip Times: Minimum = 79ms, Maximum = 84ms, Average = 81ms
Title: Re: Comcast user connection issues
Post by: gameofd1 on December 19, 2008, 08:19:23 PM
Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/19/2008 9:11:11 PM to 12/19/2008 9:17:41 PM

Hop Sent Err   PL% Min Max Avg  Host Name / [IP]
 1    27  27 100.0   0   0   0   [-]
 2    27   0   0.0   6 781  38  ge-2-19-ur01.punxy.pa.pitt.comcast.net [68.86.146.193]
 3    27   0   0.0   8 752  38  te-9-1-ur01.ruralvalley.pa.pitt.comcast.net [68.86.100.122]
 4    27   0   0.0  10 880  45  te-6-4-ar01.pittsburgh.pa.pitt.comcast.net [68.86.100.182]
 5    27   0   0.0  14 851  48  te-0-4-0-4-cr01.cleveland.oh.ibone.comcast.net [68.86.90.97]
 6    27   0   0.0  21 820  54  pos-0-6-0-0-cr01.mclean.va.ibone.comcast.net [68.86.85.41]
 7    27   0   0.0  22 792  58  xe-8-3-0.edge1.Washington1.Level3.net [63.210.62.49]
 8    27   0   0.0  21 755  51  ae-2-79.edge1.Washington3.Level3.net [4.68.17.75]
 9    18   0   0.0  22 724  65  att-level3-oc192.Washington1.Level3.net [4.68.127.154]
10    27  10  37.0  93 111  95  tbr2.wswdc.ip.att.net [12.123.8.118]
11    27  10  37.0  94 101  96  cr2.wswdc.ip.att.net [12.122.16.69]
12    27  10  37.0  94 110  97  cr1.attga.ip.att.net [12.122.1.173]
13    27  10  37.0  92 114  95  cr2.dlstx.ip.att.net [12.122.28.174]
14    27   0   0.0  93 626 136  gar5.dlstx.ip.att.net [12.122.138.5]
15    27  10  37.0  92  96  93  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
16    27  10  37.0  92 526 154  mdf1-bi8k-2-eth-2-2.dal1.attens.net [63.241.192.218]
17    27  10  37.0  92 102  95  [206.16.60.38]
Title: Re: Comcast user connection issues
Post by: Hamltnblue on December 19, 2008, 08:23:20 PM
I'm a comcast sub outside of philly and getting the same thing.  It looks like numbers are good until it hits ATT.Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Jim>tracert 206.16.60.38

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     8 ms     9 ms    10 ms  ge-2-4-ur01.wallingford.pa.panjde.comcast.net [6
8.86.218.189]
  4     9 ms     9 ms     8 ms  po-10-ur02.wallingford.pa.panjde.comcast.net [68
.86.208.186]
  5     8 ms    10 ms    11 ms  po-70-ar01.wallingford.pa.panjde.comcast.net [68
.86.208.190]
  6     9 ms    11 ms     9 ms  be-60-crs01.401nbroadst.pa.panjde.comcast.net [6
8.86.208.29]
  7    13 ms    13 ms    15 ms  pos-0-5-0-0-cr01.philadelphia.pa.ibone.comcast.n
et [68.86.90.13]
  8    15 ms    14 ms    13 ms  xe-11-1-0.edge1.Washington1.Level3.net [4.79.231
.9]
  9    13 ms    14 ms    14 ms  ae-2-79.edge1.Washington3.Level3.net [4.68.17.75
]
 10    14 ms    16 ms    14 ms  att-level3-oc192.Washington1.Level3.net [4.68.12
7.154]
 11     *        *       86 ms  tbr2.wswdc.ip.att.net [12.123.8.102]
 12    89 ms    91 ms    95 ms  cr2.wswdc.ip.att.net [12.122.16.85]
 13    90 ms    86 ms    84 ms  cr1.attga.ip.att.net [12.122.1.173]
 14    85 ms    85 ms    86 ms  cr2.dlstx.ip.att.net [12.122.28.174]
 15    85 ms    83 ms    84 ms  gar5.dlstx.ip.att.net [12.122.138.5]
 16    84 ms    85 ms    86 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255
.78]
 17    85 ms    86 ms    85 ms  mdf1-bi8k-1-eth-1-4.dal1.attens.net [63.241.192.
42]
 18    87 ms    86 ms    85 ms  206.16.60.38

Trace complete.

C:\Users\Jim>
Title: Re: Comcast user connection issues
Post by: gameofd1 on December 19, 2008, 08:24:01 PM
2 times within 5 min........DANG!!! SOMEONE DO SOEMTHING :cry





Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/19/2008 9:19:11 PM to 12/19/2008 9:22:41 PM

Hop Sent Err   PL% Min Max Avg  Host Name / [IP]
 1    15  15 100.0   0   0   0   [-]
 2    15   0   0.0   6  16   9  ge-2-19-ur01.punxy.pa.pitt.comcast.net [68.86.146.193]
 3    15   0   0.0   8  21  10  te-9-1-ur01.ruralvalley.pa.pitt.comcast.net [68.86.100.122]
 4    15   0   0.0  10  23  13  te-6-4-ar01.pittsburgh.pa.pitt.comcast.net [68.86.100.182]
 5    15   0   0.0  14  22  16  te-0-4-0-4-cr01.cleveland.oh.ibone.comcast.net [68.86.90.97]
 6    15   0   0.0  20  30  22  pos-0-6-0-0-cr01.mclean.va.ibone.comcast.net [68.86.85.41]
 7    15   0   0.0  22  33  23  xe-8-3-0.edge1.Washington1.Level3.net [63.210.62.49]
 8    15   0   0.0  21  26  22  ae-2-79.edge1.Washington3.Level3.net [4.68.17.75]
 9     6   0   0.0  23  26  23  att-level3-oc192.Washington1.Level3.net [4.68.127.154]
10    15  13  86.7  94  95  94  tbr2.wswdc.ip.att.net [12.123.8.118]
11    15  13  86.7  95  96  95  cr2.wswdc.ip.att.net [12.122.16.69]
12    15  13  86.7  93  96  94  cr1.attga.ip.att.net [12.122.1.173]
13    15  13  86.7  93  95  94  cr2.dlstx.ip.att.net [12.122.28.174]
14    15   1   6.7  94 184 113  gar5.dlstx.ip.att.net [12.122.138.5]
15    15  13  86.7  93  94  93  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
16    15  12  80.0  93  94  93  mdf1-bi8k-2-eth-2-2.dal1.attens.net [63.241.192.218]
17    15  15 100.0   0   0   0   [-]
18    15  15 100.0   0   0   0   [-]
19    15  15 100.0   0   0   0   [-]
20    15  15 100.0   0   0   0   [-]
21    15  15 100.0   0   0   0   [-]
22    15  13  86.7  93  96  94  [206.16.60.38]
Title: Re: Comcast user connection issues
Post by: Krusty on December 19, 2008, 08:31:05 PM
I was able to fly a bit late last night, but the forums have been having fits all day long.

(http://www.nakatomitower.com/htc-pingtrace1.jpg)
Title: Re: Comcast user connection issues
Post by: 4XTCH on December 19, 2008, 08:38:49 PM
My last big Disco


Target Name: 206.16.60.38.
         IP: 206.16.60.38
  Date/Time: 12/19/2008 8:38:03 PM

 1    1 ms  c-69-246-223-158.hsd1.il.comcast.net [69.246.223.158]
 2   *       [-]
 3    7 ms  [68.87.208.105]
 4   10 ms  te-8-4-ur01.mtprospect.il.chicago.comcast.net [68.87.231.73]
 5    9 ms  te-8-2-ur01.algonquin.il.chicago.comcast.net [68.87.230.21]
 6   11 ms  te-2-1-ar02.elmhurst.il.chicago.comcast.net [68.87.230.17]
 7   14 ms  [68.87.229.109]
 8   17 ms  [68.86.90.49]
 9   17 ms  xe-9-2-0.edge1.Chicago2.Level3.net [4.71.248.25]
10   14 ms  vlan52.ebr2.Chicago2.Level3.n et [4.69.138.190]
11   17 ms  ae-5.ebr2.Chicago1.Level3.net [4.69.140.193]
12   21 ms  ae-24-56.car4.Chicago1.Level3.net [4.68.101.168]
13   26 ms  [192.205.33.185]
14   79 ms  tbr2.cgcil.ip.att.net [12.123.6.70]
15   80 ms  cr2.cgcil.ip.att.net [12.122.17.221]
16   79 ms  cr2.sl9mo.ip.att.net [12.122.2.22]
17   78 ms  cr2.kc9mo.ip.att.net [12.122.28.89]
18   77 ms  cr1.dlstx.ip.att.net [12.122.28.85]
19   79 ms  gar5.dlstx.ip.att.net [12.122.139.5]
20   88 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
21   88 ms  mdf1-bi8k-1-eth-1-2.dal1.attens.net [63.241.192.202]
22   79 ms  [206.16.60.38]

Ping statistics for 206.16.60.38.
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 79ms, Maximum = 79ms, Average = 79ms
Title: Re: Comcast user connection issues
Post by: gameofd1 on December 19, 2008, 08:39:36 PM
         IP: 206.16.60.38
  Date/Time: 12/19/2008 9:34:26 PM to 12/19/2008 9:37:56 PM

Hop Sent Err   PL% Min Max Avg  Host Name / [IP]
 1    15  15 100.0   0   0   0   [-]
 2    15   0   0.0   6  20   8  ge-2-19-ur01.punxy.pa.pitt.comcast.net [68.86.146.193]
 3    15   0   0.0   8  16  10  te-9-1-ur01.ruralvalley.pa.pitt.comcast.net [68.86.100.122]
 4    15   0   0.0  11  16  13  te-6-4-ar01.pittsburgh.pa.pitt.comcast.net [68.86.100.182]
 5    15   0   0.0  15  26  16  te-0-4-0-4-cr01.cleveland.oh.ibone.comcast.net [68.86.90.97]
 6    15   0   0.0  20  35  23  pos-0-6-0-0-cr01.mclean.va.ibone.comcast.net [68.86.85.41]
 7    15   0   0.0  22  81  29  xe-8-3-0.edge1.Washington1.Level3.net [63.210.62.49]
 8    15   0   0.0  21  41  25  ae-2-79.edge1.Washington3.Level3.net [4.68.17.75]
 9     7   1  14.3  23  30  24  att-level3-oc192.Washington1.Level3.net [4.68.127.154]
10    15  13  86.7  94  94  94  tbr2.wswdc.ip.att.net [12.123.8.118]
11    15  13  86.7  95  98  96  cr2.wswdc.ip.att.net [12.122.16.69]
12    15  13  86.7  95  97  96  cr1.attga.ip.att.net [12.122.1.173]
13    15  13  86.7  94  95  94  cr2.dlstx.ip.att.net [12.122.28.174]
14    15   1   6.7  94 314 142  gar5.dlstx.ip.att.net [12.122.138.5]
15    15  13  86.7  93  95  94  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
16    15  12  80.0  93 492 291  mdf1-bi8k-2-eth-2-2.dal1.attens.net [63.241.192.218]
17    15  13  86.7  93 115 104  [206.16.60.38]

Title: Re: Comcast user connection issues
Post by: Hamltnblue on December 19, 2008, 08:52:27 PM
I seem to be having more problems with the TA and disco's.
so far in early war no probs yet TA I disco in 5 mins.
Of course that could change I'm sure
Title: Re: Comcast user connection issues
Post by: gameofd1 on December 19, 2008, 08:59:11 PM
blue arena has a better connect to orange for me atleast and i have comcast
Title: Re: Comcast user connection issues
Post by: kvuo75 on December 19, 2008, 09:00:09 PM
just got off phone with comcast, couldn't make it above call center boy's supervisor, who assured me "they're working on it"


they did at least have aces high 2 listed as 2000-6000 users affected :)



Title: Re: Comcast user connection issues
Post by: 4440 on December 19, 2008, 09:04:05 PM
My turn   NW WA state

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/19/08 7:02:30 PM

 1   *       *       *       [-]
 2   10 ms    6 ms    9 ms  [68.87.207.129]
 3    7 ms    6 ms   12 ms  te-5-3-ur02.ferndale.wa.seattle.comcast.net [68.86.96.110]
 4   13 ms   10 ms   13 ms  te-7-1-ar02.seattle.wa.seattle.comcast.net [68.86.96.105]
 5   11 ms   11 ms   11 ms  te-0-4-0-1-cr01.seattle.wa.ibone.comcast.net [68.86.90.213]
 6   16 ms  142 ms   11 ms  te-3-3.car1.Seattle1.Level3.net [4.79.104.109]
 7   13 ms   11 ms   11 ms  ge-2-0-0-52.gar1.Seattle1.Level3.net [4.68.105.41]
 8   31 ms   30 ms   30 ms  [192.205.33.145]
 9   80 ms   76 ms   77 ms  tbr1.st6wa.ip.att.net [12.127.6.169]
10   80 ms   77 ms   75 ms  cr1.st6wa.ip.att.net [12.122.23.129]
11   74 ms   76 ms   76 ms  cr2.sffca.ip.att.net [12.122.31.194]
12   75 ms   77 ms   75 ms  cr2.la2ca.ip.att.net [12.122.31.133]
13   73 ms   77 ms   74 ms  cr2.dlstx.ip.att.net [12.122.28.177]
14   74 ms   75 ms   77 ms  gar5.dlstx.ip.att.net [12.122.138.5]
15   76 ms   76 ms   77 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
16   76 ms   77 ms   74 ms  mdf1-bi8k-2-eth-2-2.dal1.attens.net [63.241.192.218]
17   77 ms   77 ms   75 ms  [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 3, Received = 3, Lost = 0 (0.0%)
Round Trip Times: Minimum = 75ms, Maximum = 77ms, Average = 76ms
Title: Re: Comcast user connection issues
Post by: BaldEagl on December 19, 2008, 09:04:36 PM
just got off phone with comcast, couldn't make it above call center boy's supervisor, who assured me "they're working on it"


they did at least have aces high 2 listed as 2000-6000 users affected :)





I'm guessing they won't be calling me back within 24 hours then.   :rofl
Title: Re: Comcast user connection issues
Post by: captain1ma on December 19, 2008, 09:08:06 PM
12/19/08
10:09pm EST

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1   <10 ms   <10 ms   <10 ms  192.168.0.1
  2     7 ms     7 ms     7 ms  73.219.88.1
  3     7 ms     7 ms     7 ms  ge-1-43-ur01.lowell.ma.boston.comcast.net [68.87
.155.177]
  4    13 ms     9 ms     7 ms  po-22-ar02.needham.ma.boston.comcast.net [68.87.
144.29]
  5    12 ms    11 ms    12 ms  68.85.162.70
  6    15 ms    15 ms    15 ms  pos-0-3-0-0-cr01.chicago.il.ibone.comcast.net [6
8.86.90.57]
  7    15 ms    15 ms    16 ms  xe-10-3-0.edge1.NewYork2.Level3.net [4.71.184.1]

  8    15 ms    15 ms    16 ms  ae-33-89.car3.NewYork1.Level3.net [4.68.16.133]

  9    15 ms    15 ms    15 ms  att-level3-oc192.NewYork1.Level3.net [4.68.127.1
50]
 10    92 ms    92 ms    94 ms  tbr2.n54ny.ip.att.net [12.123.3.110]
 11    93 ms    93 ms    93 ms  cr2.n54ny.ip.att.net [12.122.16.221]
 12    92 ms    91 ms    91 ms  cr2.wswdc.ip.att.net [12.122.3.38]
 13    92 ms    93 ms    92 ms  cr1.attga.ip.att.net [12.122.1.173]
 14    91 ms    91 ms    91 ms  cr2.dlstx.ip.att.net [12.122.28.174]
 15    93 ms    92 ms    90 ms  gar5.dlstx.ip.att.net [12.122.138.5]
 16    94 ms    94 ms    92 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255
.82]
 17    92 ms    97 ms    94 ms  mdf1-bi8k-2-eth-2-3.dal1.attens.net [63.241.192.
222]
 18    94 ms    92 ms    92 ms  206.16.60.38

Trace complete.
Title: Re: Comcast user connection issues
Post by: DakOne on December 19, 2008, 09:15:39 PM
I've got Embarq DSL and am getting the same Disco issues about every 15 minutes from sign on.
Title: Re: Comcast user connection issues
Post by: rainnman on December 19, 2008, 09:44:07 PM
Just food for thought.  I am using pingplotter and just did a check on the system and found that my first 10 hops which are mainly comcast or level 3 were all in the green working just fine.  Hops 11 thru 19 which are all att were yellow or red and losing packets.  Seems to me at least today the culprit is att not comcast.
Title: Re: Comcast user connection issues
Post by: skopro on December 19, 2008, 10:15:38 PM
Mine started going crazy starting the 1st of dec.Normally i would have a 32 ping to the server,but it was at 117,ran ping plotter and found ridiculous amounts of PL.Has gotten alot better and haven't really had any major issues but thought i would post my results




Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/19/2008 9:10:17 PM to 12/19/2008 9:10:26 PM

 1    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms  [192.168.1.1]
 2    7 ms    7 ms    9 ms   10 ms    8 ms    8 ms    7 ms   12 ms   15 ms    8 ms  [96.169.36.1]
 3    8 ms    7 ms    7 ms   13 ms   16 ms    8 ms    6 ms   12 ms   12 ms    8 ms  ge-4-13-ur01.arvada.co.denver.comcast.net [68.85.220.61]
 4    8 ms    8 ms   10 ms   10 ms   10 ms    9 ms    9 ms   12 ms   15 ms    9 ms  te-9-1-ur02.arvada.co.denver.comcast.net [68.86.103.126]
 5    8 ms    9 ms   10 ms    9 ms   10 ms    8 ms    8 ms   16 ms   12 ms    9 ms  te-8-2-ar01.aurora.co.denver.comcast.net [68.86.103.41]
 6    9 ms   10 ms   13 ms   11 ms   11 ms   10 ms    9 ms   12 ms   12 ms   11 ms  te-0-4-0-0-cr01.denver.co.ibone.comcast.net [68.86.91.1]
 7   15 ms   10 ms   12 ms   10 ms  194 ms  194 ms   67 ms  142 ms   *        9 ms  te-4-3.car2.Denver1.Level3.net [4.79.82.53]
 8    9 ms   18 ms   14 ms   22 ms   17 ms   12 ms   *       12 ms   24 ms   18 ms  ae-32-54.ebr2.Denver1.Level3.net [4.68.107.126]
 9   15 ms   10 ms   23 ms   12 ms   13 ms   20 ms   10 ms   23 ms   16 ms   10 ms  ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]
10   26 ms   36 ms   29 ms   26 ms   35 ms   28 ms   38 ms   *       28 ms   34 ms  ae-2.ebr2.Dallas1.Level3.net [4.69.132.106]
11   32 ms   25 ms   36 ms   29 ms   *       *       27 ms   37 ms   30 ms   28 ms  ae-92-92.csw4.Dallas1.Level3.net [4.69.136.150]
12   24 ms   25 ms   25 ms   27 ms   28 ms   26 ms   28 ms   22 ms   78 ms   25 ms  ae-4-99.edge2.Dallas3.Level3.net [4.68.19.204]
13   53 ms   52 ms   52 ms   53 ms   54 ms   51 ms   51 ms   52 ms   54 ms   51 ms  [192.205.35.225]
14   55 ms   55 ms   54 ms   66 ms   56 ms   55 ms   56 ms   55 ms   55 ms   54 ms  tbr1.dlstx.ip.att.net [12.123.16.202]
15   57 ms   54 ms   55 ms   57 ms   56 ms   53 ms   56 ms   57 ms   55 ms   54 ms  cr1.dlstx.ip.att.net [12.122.18.145]
16   66 ms   52 ms   50 ms   54 ms   53 ms   51 ms   *       52 ms   51 ms  N/A     gar5.dlstx.ip.att.net [12.122.139.5]
17   55 ms   52 ms   55 ms   58 ms   56 ms   54 ms   57 ms   56 ms   55 ms  N/A     mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
18   59 ms   *       54 ms   56 ms   56 ms   53 ms   56 ms   56 ms   53 ms  N/A     mdf1-bi8k-1-eth-1-1.dal1.attens.net [63.241.192.250]
19   56 ms   52 ms   54 ms   57 ms   57 ms   52 ms   56 ms   54 ms   52 ms  N/A     [206.16.60.38]

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

(http://skopro.com/pl.jpg)
Title: Re: Comcast user connection issues
Post by: StokesAk on December 19, 2008, 10:46:40 PM
Its Fixed  :D  :D  :D  :D I can now play in all the arena without discoing evry second <<<<<<S>>>>>> Skuzzy thgank You for all the Help.
Title: Re: Comcast user connection issues
Post by: ROC on December 19, 2008, 11:22:59 PM
For comparison, I have not noticed any issues, Sacramento CA, Wavecable (used to be Charter)
If you need to show anyone that others are not having issues.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.


Tracing route to 206.16.60.38 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     9 ms    10 ms     9 ms  10.15.0.1
  3     8 ms    14 ms     9 ms  172.29.120.2
  4    11 ms    12 ms    11 ms  hrsp.rk.wavecable.com [76.14.96.1]
  5    16 ms    16 ms    14 ms  66.239.40.49.ptr.us.xo.net [66.239.40.49]
  6    16 ms    16 ms    16 ms  p3-0-0d0.mar2.roseville-ca.us.xo.net [207.88.80.
77]
  7    16 ms    15 ms    16 ms  p3-0-0d0.rar2.sanjose-ca.us.xo.net [65.106.5.209
]
  8    29 ms    30 ms    30 ms  207.88.12.181.ptr.us.xo.net [207.88.12.181]
  9    24 ms    28 ms    28 ms  207.88.12.182.ptr.us.xo.net [207.88.12.182]
 10    24 ms    25 ms    29 ms  206.111.12.146.ptr.us.xo.net [206.111.12.146]
 11    71 ms    70 ms    73 ms  tbr2.sffca.ip.att.net [12.123.13.70]
 12    65 ms    66 ms    66 ms  cr2.sffca.ip.att.net [12.122.19.77]
 13    61 ms    60 ms    61 ms  cr2.la2ca.ip.att.net [12.122.31.133]
 14    72 ms    72 ms    68 ms  cr2.dlstx.ip.att.net [12.122.28.177]
 15    65 ms    63 ms    61 ms  gar5.dlstx.ip.att.net [12.122.138.5]
 16    60 ms    62 ms    60 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255
.78]
 17    61 ms   518 ms    64 ms  mdf1-bi8k-2-eth-2-3.dal1.attens.net [63.241.192.
222]
 18    71 ms    65 ms    69 ms  206.16.60.38

Trace complete.


Tracing route to 206.16.60.38 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    10 ms     8 ms     9 ms  10.15.0.1
  3    12 ms    11 ms     9 ms  172.29.120.2
  4    13 ms    11 ms    13 ms  hrsp.rk.wavecable.com [76.14.96.1]
  5    20 ms    21 ms    30 ms  66.239.40.49.ptr.us.xo.net [66.239.40.49]
  6    15 ms    16 ms    16 ms  p3-0-0d0.mar2.roseville-ca.us.xo.net [207.88.80.
77]
  7    26 ms    27 ms    25 ms  p3-0-0d0.rar2.sanjose-ca.us.xo.net [65.106.5.209
]
  8    23 ms    24 ms    22 ms  207.88.12.181.ptr.us.xo.net [207.88.12.181]
  9    18 ms    18 ms    17 ms  207.88.12.182.ptr.us.xo.net [207.88.12.182]
 10    27 ms    28 ms    24 ms  206.111.12.146.ptr.us.xo.net [206.111.12.146]
 11    65 ms    69 ms    69 ms  tbr2.sffca.ip.att.net [12.123.13.70]
 12    61 ms    60 ms    60 ms  cr2.sffca.ip.att.net [12.122.19.77]
 13    64 ms    60 ms    60 ms  cr2.la2ca.ip.att.net [12.122.31.133]
 14    64 ms    62 ms    63 ms  cr2.dlstx.ip.att.net [12.122.28.177]
 15    63 ms    63 ms    62 ms  gar5.dlstx.ip.att.net [12.122.138.5]
 16    61 ms    62 ms    64 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255
.78]
 17    62 ms    61 ms    59 ms  mdf1-bi8k-2-eth-2-3.dal1.attens.net [63.241.192.
222]
 18    61 ms    60 ms    64 ms  206.16.60.38

Trace complete.


Tracing route to 206.16.60.38 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     9 ms     9 ms     9 ms  10.15.0.1
  3    10 ms     9 ms     9 ms  172.29.120.2
  4    13 ms    11 ms    11 ms  hrsp.rk.wavecable.com [76.14.96.1]
  5    13 ms    14 ms    14 ms  66.239.40.49.ptr.us.xo.net [66.239.40.49]
  6    21 ms    20 ms    19 ms  p3-0-0d0.mar2.roseville-ca.us.xo.net [207.88.80.
77]
  7    19 ms    14 ms    15 ms  p3-0-0d0.rar2.sanjose-ca.us.xo.net [65.106.5.209
]
  8    16 ms    19 ms    15 ms  207.88.12.181.ptr.us.xo.net [207.88.12.181]
  9    14 ms    16 ms    17 ms  207.88.12.182.ptr.us.xo.net [207.88.12.182]
 10    17 ms    17 ms    17 ms  206.111.12.146.ptr.us.xo.net [206.111.12.146]
 11    59 ms    59 ms    69 ms  tbr2.sffca.ip.att.net [12.123.13.70]
 12    59 ms    62 ms    66 ms  cr2.sffca.ip.att.net [12.122.19.77]
 13    60 ms    60 ms    61 ms  cr2.la2ca.ip.att.net [12.122.31.133]
 14    66 ms    69 ms    66 ms  cr2.dlstx.ip.att.net [12.122.28.177]
 15    61 ms    57 ms    58 ms  gar5.dlstx.ip.att.net [12.122.138.5]
 16    59 ms    60 ms    61 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255
.78]
 17    63 ms    62 ms    60 ms  mdf1-bi8k-2-eth-2-3.dal1.attens.net [63.241.192.
222]
 18    59 ms    59 ms    58 ms  206.16.60.38

Trace complete.

Title: Re: Comcast user connection issues
Post by: kvuo75 on December 19, 2008, 11:42:38 PM
I'm guessing they won't be calling me back within 24 hours then.   :rofl


no probs since 7pm my time -- about an hour before FSO time..

Title: Re: Comcast user connection issues
Post by: HighGTrn on December 19, 2008, 11:49:58 PM
You think this could have anything to do with our problem?

http://www.networkworld.com/news/2008/121908-undersea-cable-cuts-disrupt-internet.html
Title: Re: Comcast user connection issues
Post by: Sincraft on December 20, 2008, 12:20:52 AM
Skuzzy : Here is my info.  My hops to level 3 are GREAT but after that...
After running a ping plot my worst area is at the last 2 hops on your end.  I have ZERO packet loss OMG.  Far cry from the well overloaded routers just 30 miles to the east where I used to live.  I'm happy with it but the ping times and hops could be better. 

Anyway - here are my tracert results.

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1   xxxxxxxxxxxxxxxxxxxxxxxxxxxxx

  2    xxxxxxxxxxxxxxxxxxxxxxxxxx
  3    12 ms     9 ms     9 ms  ge-2-1-ur01.mckeesport.pa.pitt.comcast.net [68.8
6.102.241]
  4     9 ms     8 ms     9 ms  te-8-3-ar01.mckeesport.pa.pitt.comcast.net [68.8
6.100.45]
  5    16 ms    13 ms    14 ms  te-0-4-0-0-cr01.pittsburgh.pa.ibone.comcast.net
[68.86.90.101]
  6    14 ms    15 ms    14 ms  xe-8-0-0.edge1.Washington1.Level3.net [4.79.20.1
7]
  7    16 ms    16 ms    14 ms  ae-4-99.edge1.Washington3.Level3.net [4.68.17.20
3]
  8    15 ms    17 ms    15 ms  att-level3-oc192.Washington1.Level3.net [209.244
.219.142]
  9    86 ms    88 ms    87 ms  tbr2.wswdc.ip.att.net [12.123.8.118]
 10    86 ms    87 ms    87 ms  cr2.wswdc.ip.att.net [12.122.16.85]
 11    86 ms    87 ms    88 ms  cr1.attga.ip.att.net [12.122.1.173]
 12    87 ms    86 ms    88 ms  cr2.dlstx.ip.att.net [12.122.28.174]
 13    87 ms    87 ms    85 ms  gar5.dlstx.ip.att.net [12.122.138.5]
 14    86 ms    86 ms    86 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255
.78]
 15    87 ms    88 ms    89 ms  mdf1-bi8k-2-eth-2-6.dal1.attens.net [63.241.192.
46]
 16    89 ms    87 ms    86 ms  206.16.60.38

Trace complete.
Title: Re: Comcast user connection issues
Post by: drdeathx on December 20, 2008, 12:50:13 AM
I'm guessing they won't be calling me back within 24 hours then.   :rofl



Called Comcast.Told Tech to make a report seeing he said they were probably aware of it. I replied if all you techs say this I  bet no report has been made! Boom, up in running 1 hour later!!!

DRDEATH you truely rock!

 :aok :aok :aok :rock :rock :rock
Title: Re: Comcast user connection issues
Post by: Skuzzy on December 20, 2008, 05:44:42 AM
The problem was a routing issue between Comcast and AT&T.  At one point no one on Comcasts's network could reach any site in AT&T's network.  Bad routes injected into the Level3 network were aggravating the problem.  Someone, somewhere fat-fingered the routing tables.

There may have been one other ISP involved who actually caused the problem.

Getting this fixed is not going to solve the overall problem with Level3's network being oversold.

Title: Re: Comcast user connection issues
Post by: VonMessa on December 20, 2008, 05:55:20 AM
At least I was OK for FSO  :aok

And now we know the proper way to rattle their cage.  :devil
Title: Re: Comcast user connection issues
Post by: Paladin3 on December 20, 2008, 07:03:13 AM
Once again Skuzzy, MAJOR points for the help you gave me. Much appriciated sir.  :salute
Title: Re: Comcast user connection issues
Post by: Wayout on December 20, 2008, 07:26:31 AM
From the Detroit area.

(http://rockford.yi.org/ah/pingplot.jpg)
Title: Re: Comcast user connection issues
Post by: Max on December 20, 2008, 07:56:50 AM
<--- 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  :devil
Title: Re: Comcast user connection issues
Post by: TankBstr on December 20, 2008, 08:01:14 AM
Write Al Gore and complain to him. He invented the damn thing.
Title: Re: Comcast user connection issues
Post by: Chapel on December 20, 2008, 12:01:48 PM
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.
Title: Re: Comcast user connection issues
Post by: fudgums on December 20, 2008, 01:32:35 PM
<--- 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  :devil

 :aok now Skuzzy will be on Obamas top 5. If you know what I mean
Title: Re: Comcast user connection issues
Post by: oceans11 on December 20, 2008, 03:46:44 PM
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
Title: Re: Comcast user connection issues
Post by: Sincraft on December 20, 2008, 06:23:05 PM
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. 
Title: Re: Comcast user connection issues
Post by: ink on December 20, 2008, 07:27:55 PM
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.
Title: Re: Comcast user connection issues
Post by: OOZ662 on December 20, 2008, 11:28:21 PM
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]

(http://i236.photobucket.com/albums/ff255/OOZ662/PingPlotDec20.jpg)
Title: Re: Comcast user connection issues
Post by: drdeathx on December 21, 2008, 12:31:03 AM
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.


(http://i435.photobucket.com/albums/qq77/AAdeath/pp2.jpg)



(http://i435.photobucket.com/albums/qq77/AAdeath/turtles_slowskys.jpg)
Title: Re: Comcast user connection issues
Post by: Delirium on December 21, 2008, 01:20:04 AM
Skuzzy, do you want pingplots on everyone with Comcast or just those with problems?
Title: Re: Comcast user connection issues
Post by: Skuzzy on December 21, 2008, 05:39:18 AM
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.
Title: Re: Comcast user connection issues
Post by: Hawk78th on December 21, 2008, 08:48:51 AM
 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
Title: Re: Comcast user connection issues
Post by: BaldEagl on December 21, 2008, 08:56:10 AM
Everything was working good last night.

Thanks Skuzzy.  You might want to take the MOTD down.
Title: Re: Comcast user connection issues
Post by: dentin on December 21, 2008, 09:46:06 AM
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

Title: Re: Comcast user connection issues
Post by: Skuzzy on December 21, 2008, 10:31:50 AM
No Hawk, your problems are in the Level3, as are yours dentin.
Title: Re: Comcast user connection issues
Post by: HighGTrn on December 21, 2008, 10:39:19 AM
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. 
Title: Re: Comcast user connection issues
Post by: oceans11 on December 21, 2008, 10:43:49 AM
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


(http://i548.photobucket.com/albums/ii348/Oceans1167/aces.jpg)
Title: Re: Comcast user connection issues
Post by: HighGTrn on December 21, 2008, 10:50:09 AM
Looks like Scuzzy is definately right.  I have the same exact info. Its all fine until the traffic jumps from Level3 to ATT. That's when it goes to hell.  Will FIOS really fix the problem?  They all eventually have to hit a backbone somewhere.  That means ATT or Level3.  I don't think it will help in this situation.
Title: Re: Comcast user connection issues
Post by: Delirium on December 21, 2008, 11:01:24 AM
Just started having problems too... maybe I'm not computer savvy, but it looks like an AT&T issue to me.

(http://i242.photobucket.com/albums/ff14/DeliriumP38/206166038.gif)
Title: Re: Comcast user connection issues
Post by: Dawger on December 21, 2008, 11:08:38 AM
I'm not too far south of the server and I'm getting a bad ping.

(http://home.comcast.net/~micelihouston/206.16.60.38.png)
Title: Re: Comcast user connection issues
Post by: Delirium on December 21, 2008, 11:13:15 AM
Ok, disregard my earlier comment. I don't believe this moron either...

http://www.dslreports.com/forum/r21610238-Connectivity-Disconnecting-from-Warcraft


Quote
See »forums.comcast.net/comcastsuppor···id=17159 if you would like to track this. Here's what I posted there:

World of Warcraft Issues --> Comcast Assisting to Help Resolve

We have numerous reports from customers who play World of Warcraft (WoW) of performance problems. We have seen this here @ »forums.worldofwarcraft.com/threa···geNo=205 (as of this time, an amazingly long 205-page thread) and here @ »[Connectivity] Disconnecting from Warcraft and several other places like this »www.inquisitr.com/12664/comcast-···t-users/.

We proactively made contact with Blizzard Entertainment, who developed and operates WoW, about a week ago. An examination traceroutes from their forum and which they shared with us indicate that this is not an issue on our network, but in the path between the Comcast and Blizzard's Dallas WoW servers. Latency has not been demonstrated coming from any parts of the Comcast network. And for the avoidance of doubt, we are no way throttling or blocking WoW traffic.

The forum data also shows similar performance problems with several other providers customers trying to reach Blizzard. We continue to make ourselves available to Blizzard to assist them in this issue. We are also proactively working with the various networks between us to attempt to resolve the issue.

Regards

Jason
--
JL
Comcast

Title: Re: Comcast user connection issues
Post by: Nutzoid on December 21, 2008, 11:47:58 AM
Hey all, this is probably very basic for most of you, but how and what do you have to do to run a ping plot?

Thanks
Title: Re: Comcast user connection issues
Post by: Rich46yo on December 21, 2008, 11:50:27 AM
Really cold here in the Midwest. Plus its Sunday, "aint it? Im on vacation" My ping plot looks like the creature from the Black Lagoon. First time Ive ever had issue with this and comcast and have been getting bounced from the game, along with bad delays.

(http://i478.photobucket.com/albums/rr149/Rich46yo/206166038.png)
Title: Re: Comcast user connection issues
Post by: Colt44 on December 21, 2008, 12:00:48 PM
South Jersey area, out side of Philly..... compared to others I have seen....this can't be good.   I just started haveing issues last two days.


Target Name: 206.16.60.38.
         IP: 206.16.60.38
  Date/Time: 12/21/2008 12:56:45 PM to 12/21/2008 12:58:15 PM

 1    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms  [10.0.1.1]
 2    6 ms    4 ms    6 ms    5 ms    4 ms    5 ms    5 ms    6 ms    7 ms    6 ms  [73.204.161.1]
 3    5 ms    5 ms    7 ms    7 ms   88 ms    8 ms   14 ms    5 ms    6 ms    5 ms  ge-2-3-ur01.mayslanding.nj.panjde.comcast.net [68.85.195.33]
 4    7 ms    7 ms    7 ms    7 ms    7 ms    7 ms    6 ms    7 ms    6 ms    6 ms  te-2-2-ar01.absecon.nj.panjde.comcast.net [68.86.210.46]
 5    8 ms    7 ms    8 ms    8 ms    8 ms    8 ms    9 ms    9 ms    8 ms    8 ms  be-30-crs01.audubon.nj.panjde.comcast.net [68.86.208.22]
 6   11 ms   10 ms   11 ms   11 ms   11 ms   11 ms   12 ms   10 ms   10 ms   11 ms  be-60-crs01.plainfield.nj.panjde.comcast.net [68.86.208.1]
 7   13 ms   14 ms   15 ms   11 ms   13 ms   13 ms   14 ms   13 ms   12 ms   12 ms  pos-0-3-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.90.25]
 8   11 ms   12 ms   11 ms   15 ms   11 ms   12 ms   12 ms   11 ms   12 ms   15 ms  xe-11-1-0.edge1.NewYork2.Level3.net [4.71.186.13]
 9   12 ms   12 ms  167 ms   12 ms   15 ms   13 ms   12 ms   12 ms   12 ms   12 ms  ae-23-79.car3.NewYork1.Level3.net [4.68.16.69]
10  100 ms   98 ms   14 ms   12 ms   12 ms   13 ms   14 ms   16 ms   13 ms   13 ms  [192.205.33.93]
11  331 ms  331 ms  331 ms  331 ms  331 ms  332 ms   *      330 ms  331 ms  332 ms  tbr2.n54ny.ip.att.net [12.123.3.110]
12   *      331 ms   *      334 ms  332 ms  331 ms  331 ms  332 ms  331 ms  339 ms  cr2.n54ny.ip.att.net [12.122.16.149]
13  329 ms  330 ms  355 ms  331 ms   *      330 ms   *      330 ms  330 ms  330 ms  cr2.wswdc.ip.att.net [12.122.3.38]
14  331 ms  330 ms  332 ms  333 ms  331 ms  330 ms   *      331 ms  331 ms  330 ms  cr1.attga.ip.att.net [12.122.1.173]
15  332 ms  333 ms  331 ms  332 ms  331 ms  335 ms  332 ms  332 ms  331 ms  332 ms  cr2.dlstx.ip.att.net [12.122.28.174]
16  331 ms  330 ms  332 ms  331 ms  331 ms  374 ms  330 ms  330 ms   *      330 ms  gar5.dlstx.ip.att.net [12.122.138.5]
17  331 ms  331 ms  334 ms  332 ms  331 ms  331 ms  331 ms  331 ms  333 ms  331 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
18  330 ms  333 ms  330 ms  331 ms  330 ms  330 ms   *       *      330 ms  332 ms  mdf1-bi8k-2-eth-2-2.dal1.attens.net [63.241.192.218]
19  331 ms  331 ms  331 ms  331 ms  331 ms  331 ms   *      331 ms  330 ms  331 ms  [206.16.60.38]

Ping statistics for 206.16.60.38.
Packets: Sent = 10, Received = 9, Lost = 1 (10.0%)
Round Trip Times: Minimum = 330ms, Maximum = 331ms, Average = 330ms
Title: Re: Comcast user connection issues
Post by: Colt44 on December 21, 2008, 12:08:20 PM
Nutzoid... this is new to me also....  got to pingplotter.com, download freeware version... run it... go to edit button and hit copy as data...paste


then hope someone here can tell you how to proceed... 


anyone?  anyone?   Skuzzy help, layperson term please.   


Will it help to call comcast and bytch at 'em? 

 
Title: Re: Comcast user connection issues
Post by: Dawger on December 21, 2008, 12:10:10 PM
Hey all, this is probably very basic for most of you, but how and what do you have to do to run a ping plot?

Thanks

Go here
http://www.pingplotter.com/download.html

Download PP standard and install.

Type in the IP you want to ping in the window on the left.

Posting the results is a different question :)
Title: Re: Comcast user connection issues
Post by: Dawger on December 21, 2008, 12:12:01 PM
Fairly obvious Level 3 is killing us.

Title: Re: Comcast user connection issues
Post by: Shuffler on December 21, 2008, 12:12:34 PM
Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/21/2008 12:11:37 PM to 12/21/2008 12:12:22 PM

 1    1 ms    3 ms   17 ms   17 ms   12 ms   14 ms   19 ms    6 ms    1 ms    1 ms  [192.168.1.1]
 2    8 ms    8 ms    8 ms    8 ms    9 ms    8 ms    9 ms    8 ms   11 ms    8 ms  [192.168.1.1]
 3    8 ms   10 ms   10 ms    9 ms   12 ms    9 ms   10 ms    8 ms    9 ms   10 ms  ge-2-26-ur01.northshore.tx.houston.comcast.net [68.85.248.237]
 4   10 ms   11 ms    7 ms    9 ms    9 ms   10 ms    9 ms    8 ms    8 ms    9 ms  te-8-1-ur02.northshore.tx.houston.comcast.net [68.85.244.186]
 5   11 ms   10 ms   10 ms   11 ms    8 ms   11 ms   12 ms   10 ms    9 ms    9 ms  te-8-1-ur01.wallisville.tx.houston.comcast.net [68.85.244.181]
 6   11 ms    9 ms   13 ms   12 ms   12 ms   11 ms   10 ms   10 ms   10 ms   12 ms  te-9-3-ar02.royalton.tx.houston.comcast.net [68.85.244.137]
 7   12 ms   11 ms   11 ms   12 ms   11 ms   13 ms   17 ms   11 ms   11 ms   11 ms  po-17-ar02.greenspoint.tx.houston.comcast.net [68.85.244.130]
 8   16 ms   18 ms   19 ms   17 ms   17 ms   18 ms   16 ms   17 ms   17 ms   17 ms  te-0-4-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.91.49]
 9   17 ms   17 ms   17 ms   17 ms   18 ms   17 ms   16 ms   16 ms   16 ms   18 ms  xe-11-3-0.edge3.Dallas1.Level3.net [4.71.198.9]
10   84 ms   17 ms   19 ms   17 ms   19 ms   19 ms   60 ms   18 ms   18 ms   33 ms  ae-3-89.edge2.Dallas3.Level3.net [4.68.19.140]
11  296 ms  296 ms  295 ms  296 ms  296 ms  295 ms   *       *      295 ms  N/A     [192.205.35.141]
12   *       *       *       *       *       *      299 ms  297 ms   *      N/A     tbr1.dlstx.ip.att.net [12.123.16.202]
13   *       *       *       *       *       *       *       *       *      N/A     cr1.dlstx.ip.att.net [12.122.18.137]
14   *       *       *       *       *       *       *       *       *      N/A     gar5.dlstx.ip.att.net [12.122.139.5]
15   *       *       *       *       *       *       *       *       *      N/A      [-]
16   *       *       *       *       *       *       *       *       *      N/A      [-]
17  300 ms  297 ms  296 ms  299 ms  297 ms   *      295 ms  297 ms  297 ms  N/A     [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 10, Received = 8, Lost = 2 (20.0%)
Round Trip Times: Minimum = 295ms, Maximum = 300ms, Average = 297ms
Title: Re: Comcast user connection issues
Post by: Rich46yo on December 21, 2008, 12:40:35 PM
Let me ask this Skuzzy, succinctly. Now I just talked to the morons at comcast. They told me the only thing they can do is send a technician out. Which would resolve nothing right? I'm able to get online but I'm just not able to game. Now assuming comcast sent out somebody who can actually speak english he'd look at that and say, "there no nothing we can do", which is what comcast tech just told me. However they would charge me to tell me that in person.

So does anybody have any suggestions?
Title: Re: Comcast user connection issues
Post by: Soulyss on December 21, 2008, 12:44:18 PM
was doing ok here yesterday, today not so much.  Here's what I got, hope it helps

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/21/2008 10:40:56 AM to 12/21/2008 10:43:11 AM

 1    6 ms    8 ms   51 ms    5 ms   45 ms    9 ms   18 ms    9 ms    7 ms    7 ms  c-76-20-60-1.hsd1.ca.comcast.net [76.20.60.1]
 2    5 ms    8 ms   13 ms    7 ms    6 ms   12 ms    6 ms   10 ms    7 ms    7 ms  ge-2-2-sr01.davis.ca.sacra.comcast.net [68.87.213.49]
 3    7 ms    9 ms    6 ms    8 ms    8 ms   10 ms    7 ms   18 ms    9 ms    7 ms  te-9-1-ar01.sacramento.ca.sacra.comcast.net [68.87.212.25]
 4   10 ms   11 ms   12 ms    8 ms   11 ms   11 ms   10 ms    9 ms   11 ms   10 ms  te-0-6-0-0-ar01.oakland.ca.sfba.comcast.net [68.86.143.25]
 5   13 ms   10 ms   11 ms   12 ms   12 ms   13 ms   13 ms   14 ms   14 ms   13 ms  pos-0-2-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.90.141]
 6   14 ms   25 ms   14 ms   19 ms   16 ms   15 ms   14 ms   17 ms   18 ms   16 ms  pos-0-14-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.85.181]
 7   12 ms   14 ms   14 ms   47 ms   15 ms   13 ms   14 ms   17 ms   32 ms   37 ms  xe-10-3-0.edge1.SanJose1.Level3.net [4.71.118.5]
 8   14 ms   14 ms  163 ms   13 ms   15 ms   12 ms   12 ms   13 ms   15 ms   13 ms  ae-33-89.car3.SanJose1.Level3.net [4.68.18.133]
 9   25 ms   26 ms   47 ms   25 ms   24 ms   25 ms   35 ms   24 ms   25 ms   42 ms  level3-gw.sffca.ip.att.net [192.205.33.77]
10  303 ms  302 ms  305 ms  305 ms  384 ms  304 ms  314 ms  305 ms  303 ms  303 ms  tbr2.sffca.ip.att.net [12.122.82.150]
11  302 ms  304 ms   *      303 ms  303 ms  301 ms  301 ms   *      302 ms  303 ms  cr2.sffca.ip.att.net [12.122.19.93]
12  303 ms   *      303 ms  305 ms  302 ms  304 ms  303 ms  304 ms  301 ms  302 ms  cr2.la2ca.ip.att.net [12.122.31.133]
13  309 ms  301 ms  303 ms  303 ms  304 ms  303 ms  303 ms  301 ms  310 ms  313 ms  cr2.dlstx.ip.att.net [12.122.28.177]
14  304 ms  303 ms  303 ms  301 ms  304 ms  301 ms  356 ms  302 ms  305 ms  302 ms  gar5.dlstx.ip.att.net [12.122.138.5]
15  302 ms   *       *       *      307 ms   *      305 ms  306 ms  303 ms  305 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
16  304 ms  302 ms  304 ms  304 ms  305 ms  303 ms  302 ms  304 ms   *      306 ms  mdf1-bi8k-1-eth-1-3.dal1.attens.net [63.241.192.206]
17  304 ms  309 ms  304 ms  305 ms   *      303 ms  304 ms  302 ms   *      302 ms  [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 10, Received = 8, Lost = 2 (20.0%)
Round Trip Times: Minimum = 302ms, Maximum = 309ms, Average = 304ms
Title: Re: Comcast user connection issues
Post by: skopro on December 21, 2008, 12:45:48 PM
just logged on to see a ping go from 60-300

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/21/2008 11:43:55 AM to 12/21/2008 11:44:05 AM

 1    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms  [192.168.1.1]
 2    7 ms    8 ms    8 ms   10 ms   *        8 ms    9 ms    7 ms    7 ms    7 ms  [96.169.36.1]
 3    9 ms    7 ms    6 ms   10 ms    9 ms    8 ms    7 ms   *        7 ms    7 ms  ge-4-13-ur01.arvada.co.denver.comcast.net [68.85.220.61]
 4    9 ms    9 ms    9 ms   10 ms    8 ms    8 ms   10 ms   14 ms    8 ms    8 ms  te-9-1-ur02.arvada.co.denver.comcast.net [68.86.103.126]
 5   11 ms    8 ms   11 ms   10 ms   10 ms   10 ms   11 ms    9 ms   22 ms    8 ms  te-8-2-ar01.aurora.co.denver.comcast.net [68.86.103.41]
 6    9 ms   10 ms    9 ms    7 ms    7 ms   11 ms    9 ms   10 ms    9 ms    7 ms  te-0-4-0-0-cr01.denver.co.ibone.comcast.net [68.86.91.1]
 7    9 ms   10 ms    9 ms    8 ms    9 ms    9 ms    9 ms    8 ms    9 ms    9 ms  te-4-3.car2.Denver1.Level3.net [4.79.82.53]
 8   18 ms    8 ms   14 ms    8 ms   18 ms   13 ms    8 ms   15 ms    9 ms   19 ms  ae-32-54.ebr2.Denver1.Level3.net [4.68.107.126]
 9    9 ms   11 ms    9 ms   16 ms   10 ms   20 ms   13 ms   10 ms   18 ms   11 ms  ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37]
10   23 ms   23 ms   33 ms   26 ms   23 ms   31 ms   23 ms   33 ms   26 ms   23 ms  ae-2.ebr2.Dallas1.Level3.net [4.69.132.106]
11   34 ms   38 ms   31 ms   24 ms   35 ms   29 ms   25 ms   32 ms   25 ms   36 ms  ae-92-92.csw4.Dallas1.Level3.net [4.69.136.150]
12   24 ms   25 ms   28 ms   24 ms   24 ms   53 ms   23 ms   25 ms   24 ms  N/A     ae-4-99.edge2.Dallas3.Level3.net [4.68.19.204]
13   *      296 ms   *      295 ms   *      295 ms  295 ms  295 ms   *      296 ms  [192.205.35.225]
14  299 ms   *       *       *      296 ms   *       *       *      299 ms  296 ms  tbr1.dlstx.ip.att.net [12.123.16.202]
15  296 ms   *       *       *       *       *       *       *      298 ms  311 ms  cr1.dlstx.ip.att.net [12.122.18.145]
16  297 ms  N/A     N/A     N/A     N/A     N/A     N/A     N/A     N/A     N/A     gar5.dlstx.ip.att.net [12.122.139.5]
17   *       *       *      298 ms  N/A     N/A     N/A     N/A     N/A     N/A     mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
18   *       *       *       *       *       *      297 ms  N/A     N/A     N/A     mdf1-bi8k-1-eth-1-1.dal1.attens.net [63.241.192.250]
19  296 ms  295 ms  299 ms  295 ms  296 ms  295 ms  295 ms  295 ms  297 ms  N/A     [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 9, Received = 9, Lost = 0 (0.0%)
Round Trip Times: Minimum = 295ms, Maximum = 299ms, Average = 295ms
Title: Re: Comcast user connection issues
Post by: oceans11 on December 21, 2008, 12:57:39 PM
Fios , Since it is FIber runs directly on all verizon controlled equipment

I do not beleive they use either l3 or att

I had fios for 2 years and beleive me i was hitting 80 plus frame rate
Title: Re: Comcast user connection issues
Post by: Dustoff2 on December 21, 2008, 01:01:46 PM
doing good yeasterday, today is horrible

tracert 206.16.60.38

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  xxx.xxx.xx.x
  2     *        *        *     Request timed out.
  3     7 ms     7 ms     5 ms  ge-9-12-ur01.eagan.mn.minn.comcast.net [68.85.16
5.217]
  4     7 ms     5 ms     5 ms  te-2-1-ur02.webster.mn.minn.comcast.net [68.87.1
74.157]
  5     7 ms     5 ms     5 ms  te-8-3-ur01.webster.mn.minn.comcast.net [68.87.1
74.153]
  6     7 ms     7 ms     7 ms  te-2-1-ur02.minnehaha.mn.minn.comcast.net [68.87
.174.149]
  7     9 ms     7 ms     7 ms  te-8-3-ur01.minnehaha.mn.minn.comcast.net [68.87
.174.145]
  8    10 ms     8 ms     8 ms  te-8-1-ar02.roseville.mn.minn.comcast.net [68.87
.174.141]
  9    10 ms     8 ms    10 ms  68.87.174.217
 10    21 ms    18 ms    17 ms  te-0-2-0-4-cr01.chicago.il.ibone.comcast.net [68
.86.91.137]
 11    17 ms    17 ms    18 ms  xe-9-2-0.edge1.Chicago2.Level3.net [4.71.248.25]

 12    19 ms    17 ms    17 ms  vlan51.ebr1.Chicago2.Level3.n et [4.69.138.158]
 13    17 ms    18 ms    17 ms  ae-6.ebr1.Chicago1.Level3.net [4.69.140.189]
 14    20 ms    20 ms    19 ms  ae-14-53.car4.Chicago1.Level3.net [4.68.101.72]

 15    18 ms    18 ms    17 ms  192.205.33.209
 16     *        *      324 ms  tbr2.cgcil.ip.att.net [12.123.6.38]
 17   323 ms   323 ms   323 ms  cr2.cgcil.ip.att.net [12.122.17.197]
 18   322 ms     *        *     cr2.sl9mo.ip.att.net [12.122.2.22]
 19   323 ms   323 ms     *     cr2.kc9mo.ip.att.net [12.122.28.89]
 20     *        *      324 ms  cr1.dlstx.ip.att.net [12.122.28.85]
 21   322 ms   324 ms   323 ms  gar5.dlstx.ip.att.net [12.122.139.5]
 22   323 ms     *      324 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255
.82]
 23   323 ms   329 ms   324 ms  mdf1-bi8k-1-eth-1-3.dal1.attens.net [63.241.192.
206]
 24   324 ms   323 ms   323 ms  206.16.60.38

Trace complete.

Looks like the problem is att.net
Title: Re: Comcast user connection issues
Post by: woolyb on December 21, 2008, 01:05:50 PM
The problem has got to be ATT.

Host Information
1, -------------- ,192.168.1.1
2, -------------- ,73.155.227.1
3,ge-6-3-ur01.pottsville.pa.panjde.comcast.net,68.86.154.205
4,ge-9-24-ur01.pinegrove.pa.panjde.comcast.net,68.86.208.241
5,ge-2-24-ur01.lebanon.pa.panjde.comcast.net,68.86.208.237
6,te-9-1-ur01.hershey.pa.panjde.comcast.net,68.86.208.205
7, -------------- ,68.85.158.21
8, -------------- ,68.85.158.17
9,te-8-1-ar01.lowerpaxton.pa.panjde.comcast.net,68.86.208.193
10,be-60-crs01.ivyland.pa.panjde.comcast.net,68.86.208.46
11,be-40-crs01.401nbroadst.pa.panjde.comcast.net,68.86.208.33
12,pos-0-5-0-0-cr01.philadelphia.pa.ibone.comcast.net,68.86.90.13
13,ge-4-0-142.ipcolo2.Washington1.Level3.net,63.210.62.33
14,ae-1-69.edge1.Washington3.Level3.net,4.68.17.11
15,att-level3-oc192.Washington1.Level3.net,209.244.219.142
16,tbr2.wswdc.ip.att.net,12.123.8.102
17,cr2.wswdc.ip.att.net,12.122.16.69
18,cr1.attga.ip.att.net,12.122.1.173
19,cr2.dlstx.ip.att.net,12.122.28.174
20,gar5.dlstx.ip.att.net,12.122.138.5
21,mdf1-gsr12-1-pos-6-0.dal1.attens.net,12.122.255.78
22,mdf1-bi8k-2-eth-2-2.dal1.attens.net,63.241.192.218
23, -------------- ,206.16.60.38

Sample Information
"12/19/2008 8:17:08 PM",1,12,8,20,13,9,10,20,10,12,14,28,22,28,N/A,92,90,91,95,90,92,91,92
"12/19/2008 8:19:08 PM",1,8,9,9,9,10,10,9,10,17,15,20,18,28,N/A,92,92,98,91,90,89,246,92
"12/19/2008 8:21:08 PM",1,8,8,10,10,9,11,10,12,13,16,20,19,23,32,94,91,91,91,91,92,99,93
"12/19/2008 8:23:08 PM",1,6,9,9,9,9,9,8,13,13,17,17,21,20,21,91,88,92,90,90,99,100,92
"12/19/2008 8:25:08 PM",1,7,11,8,9,8,10,12,10,16,19,26,18,20,22,93,89,92,91,88,89,92,91
"12/19/2008 8:27:08 PM",5,9,10,10,10,10,9,10,12,15,15,35,24,21,22,101,91,91,92,89,92,92,92

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/21/2008 2:03:21 PM

 1    1 ms  [192.168.1.1]
 2    7 ms  [73.155.227.1]
 3    7 ms  ge-6-3-ur01.pottsville.pa.panjde.comcast.net [68.86.154.205]
 4    8 ms  ge-9-24-ur01.pinegrove.pa.panjde.comcast.net [68.86.208.241]
 5    8 ms  ge-2-24-ur01.lebanon.pa.panjde.comcast.net [68.86.208.237]
 6   20 ms  te-9-1-ur01.hershey.pa.panjde.comcast.net [68.86.208.205]
 7   25 ms  [68.85.158.21]
 8   11 ms  [68.85.158.17]
 9   13 ms  te-8-1-ar01.lowerpaxton.pa.panjde.comcast.net [68.86.208.193]
10   17 ms  be-60-crs01.ivyland.pa.panjde.comcast.net [68.86.208.46]
11   22 ms  be-40-crs01.401nbroadst.pa.panjde.comcast.net [68.86.208.33]
12   20 ms  pos-0-5-0-0-cr01.philadelphia.pa.ibone.comcast.net [68.86.90.13]
13   19 ms  ge-4-0-142.ipcolo2.Washington1.Level3.net [63.210.62.33]
14   19 ms  ae-1-69.edge1.Washington3.Level3.net [4.68.17.11]
15   23 ms  att-level3-oc192.Washington1.Level3.net [4.68.127.154]
16  345 ms  tbr2.wswdc.ip.att.net [12.123.8.102]
17  337 ms  cr2.wswdc.ip.att.net [12.122.16.69]
18  339 ms  cr1.attga.ip.att.net [12.122.1.173]
19  341 ms  cr2.dlstx.ip.att.net [12.122.28.174]
20  337 ms  gar5.dlstx.ip.att.net [12.122.138.5]
21  344 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
22  341 ms  mdf1-bi8k-2-eth-2-2.dal1.attens.net [63.241.192.218]
23  337 ms  [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 1, Received = 1, Lost = 0 (0.0%)
Round Trip Times: Minimum = 337ms, Maximum = 337ms, Average = 337ms
Title: Re: Comcast user connection issues
Post by: ImADot on December 21, 2008, 01:06:14 PM
Although Friday was tolerable, today just plain sux.  Up until very recently (like the last week), my ping times were never above 63ms to any arena.  Looks like Level3-->ATT is the problem (big surprise  :noid ).

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/21/2008 1:03:24 PM

 1    1 ms    0 ms    0 ms    0 ms    0 ms  [192.168.1.1]
 2   11 ms    6 ms    6 ms    7 ms    9 ms  [73.205.44.1]
 3   13 ms   12 ms    6 ms    7 ms    7 ms  ge-4-1-ur01.crosstown.mn.minn.comcast.net [68.85.164.1]
 4   15 ms    6 ms    9 ms    8 ms    7 ms  te-0-1-0-5-ar02.crosstown.mn.minn.comcast.net [68.86.232.1]
 5    8 ms    7 ms    6 ms   13 ms   10 ms  [68.87.174.217]
 6   18 ms   17 ms   17 ms   19 ms   21 ms  te-0-2-0-5-cr01.chicago.il.ibone.comcast.net [68.86.91.141]
 7   29 ms   16 ms   17 ms   19 ms   18 ms  xe-9-2-0.edge1.Chicago2.Level3.net [4.71.248.25]
 8   19 ms   19 ms   16 ms   19 ms   18 ms  vlan51.ebr1.Chicago2.Level3.n et [4.69.138.158]
 9   17 ms   21 ms   24 ms   24 ms   19 ms  ae-6.ebr1.Chicago1.Level3.net [4.69.140.189]
10   18 ms   17 ms  109 ms   21 ms   18 ms  ae-14-55.car4.Chicago1.Level3.net [4.68.101.136]
11   18 ms   21 ms   17 ms   19 ms  168 ms  [192.205.33.209]
12  329 ms   *      327 ms  326 ms  322 ms  tbr2.cgcil.ip.att.net [12.123.6.38]
13  326 ms  322 ms  321 ms  321 ms   *      cr2.cgcil.ip.att.net [12.122.17.237]
14  321 ms  321 ms  322 ms  322 ms  323 ms  cr2.sl9mo.ip.att.net [12.122.2.22]
15  N/A     321 ms  323 ms  321 ms  322 ms  cr2.kc9mo.ip.att.net [12.122.28.89]
16  324 ms  323 ms  324 ms  323 ms  334 ms  cr1.dlstx.ip.att.net [12.122.28.85]
17  471 ms   *      322 ms  321 ms  321 ms  gar5.dlstx.ip.att.net [12.122.139.5]
18  323 ms   *      321 ms  322 ms  325 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
19  N/A     324 ms   *      322 ms  323 ms  mdf1-bi8k-1-eth-1-2.dal1.attens.net [63.241.192.202]
20  326 ms  322 ms  321 ms  324 ms   *      [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 5, Received = 4, Lost = 1 (20.0%)
Round Trip Times: Minimum = 321ms, Maximum = 326ms, Average = 323ms
Title: Re: Comcast user connection issues
Post by: Alpha81 on December 21, 2008, 01:09:00 PM
From Kingston WA> About 15 miles west of Seattle as the crow flies  
COMCAST is my ISP



Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/21/2008 11:05:03 AM to 12/21/2008 11:06:33 AM

 1    1 ms    0 ms    0 ms    0 ms    0 ms    1 ms    0 ms  [192.168.1.1]
 2   11 ms    7 ms    7 ms    8 ms    8 ms    6 ms    8 ms  [192.168.1.1]
 3    9 ms    8 ms    8 ms    9 ms    8 ms    7 ms    8 ms  [68.87.205.45]
 4   14 ms   10 ms   10 ms   11 ms   10 ms    9 ms   11 ms  te-7-3-ar01.burien.wa.seattle.comcast.net [68.86.96.46]
 5   14 ms   14 ms   14 ms   15 ms   14 ms   13 ms   15 ms  [68.86.90.221]
 6   18 ms   14 ms   14 ms   15 ms   15 ms   15 ms   15 ms  pos-0-0-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.85.205]
 7   15 ms   83 ms   13 ms   14 ms   14 ms   13 ms   14 ms  te-3-2.car1.Seattle1.Level3.net [4.79.104.105]
 8   14 ms   14 ms   14 ms   15 ms   14 ms   16 ms   15 ms  ge-2-0-0-56.gar1.Seattle1.Level3.net [4.68.105.169]
 9  N/A     N/A     N/A     N/A     N/A      33 ms   33 ms  [192.205.33.145]
10  326 ms  322 ms  323 ms   *      322 ms   *      323 ms  tbr1.st6wa.ip.att.net [12.127.6.58]
11  N/A     N/A     N/A     322 ms   *      322 ms   *      cr1.st6wa.ip.att.net [12.122.23.129]
12  323 ms   *       *       *       *       *       *      cr2.sffca.ip.att.net [12.122.31.194]
13  322 ms   *       *       *       *       *       *      cr2.la2ca.ip.att.net [12.122.31.133]
14  322 ms   *       *       *       *       *       *      cr2.dlstx.ip.att.net [12.122.28.177]
15  322 ms   *       *       *       *       *       *      gar5.dlstx.ip.att.net [12.122.138.5]
16  322 ms   *       *       *       *       *       *      mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
17  322 ms   *       *       *       *       *       *      mdf1-bi8k-2-eth-2-1.dal1.attens.net [63.241.192.198]
18  322 ms  322 ms  326 ms  323 ms   *      322 ms  322 ms  [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 7, Received = 6, Lost = 1 (14.3%)
Round Trip Times: Minimum = 322ms, Maximum = 326ms, Average = 322ms
Title: Re: Comcast user connection issues
Post by: BaldEagl on December 21, 2008, 01:11:31 PM
Well, I spoke too soon.  It's still happening and it's all in the AT&T connections:

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 12/21/2008 1:09:49 PM to 12/21/2008 1:12:04 PM

 2    5 ms    5 ms    5 ms    5 ms    7 ms    7 ms    7 ms    6 ms    6 ms    6 ms  [73.112.244.1]
 3   10 ms    6 ms    6 ms    6 ms    6 ms    6 ms    6 ms    7 ms    6 ms    6 ms  ge-9-1-ur02.minnetonka.mn.minn.comcast.net [68.85.164.117]
 4    6 ms    7 ms    7 ms    7 ms    7 ms    7 ms    7 ms    7 ms    6 ms    6 ms  te-2-3-ur01.minnetonka.mn.minn.comcast.net [68.86.232.141]
 5    7 ms    6 ms    6 ms    6 ms    6 ms    6 ms    5 ms    5 ms    7 ms    7 ms  te-8-1-ur01.martin.mn.minn.comcast.net [68.86.232.37]
 6    8 ms    7 ms    6 ms    7 ms    7 ms    6 ms    6 ms    8 ms    6 ms    6 ms  te-2-3-ur01.martin.mn.minn.comcast.net [68.86.232.161]
 7    8 ms    6 ms    6 ms   10 ms    7 ms    8 ms    7 ms   17 ms    7 ms   11 ms  te-8-1-ur02.crosstown.mn.minn.comcast.net [68.86.232.33]
 8    8 ms    7 ms    6 ms    7 ms   10 ms    6 ms   11 ms    6 ms    6 ms    6 ms  te-2-1-ur01.crosstown.mn.minn.comcast.net [68.86.232.5]
 9   10 ms    7 ms    8 ms    7 ms    8 ms    7 ms    7 ms    6 ms    8 ms    7 ms  te-0-1-0-5-ar02.crosstown.mn.minn.comcast.net [68.86.232.1]
10   10 ms    7 ms   15 ms    7 ms   20 ms    6 ms    8 ms    8 ms    9 ms    7 ms  te-8-3-ar02.roseville.mn.minn.comcast.net [68.87.174.6]
11   26 ms   26 ms   25 ms   26 ms   26 ms   26 ms   25 ms   25 ms   26 ms   25 ms  [68.86.91.181]
12   27 ms   26 ms   26 ms   30 ms   27 ms   26 ms   26 ms   27 ms   27 ms   27 ms  te-4-4.car2.Denver1.Level3.net [4.79.82.57]
13   31 ms   26 ms   33 ms   25 ms   29 ms   37 ms   26 ms   32 ms   25 ms   29 ms  ae-31-55.ebr1.Denver1.Level3.net [4.68.107.158]
14   41 ms   50 ms   52 ms   41 ms   41 ms   41 ms   43 ms   45 ms   47 ms   49 ms  ae-2.ebr2.Dallas1.Level3.net [4.69.132.106]
15   45 ms   52 ms   42 ms   41 ms   60 ms   44 ms   48 ms   50 ms   52 ms   41 ms  ae-82-82.csw3.Dallas1.Level3.net [4.69.136.146]
16   40 ms   41 ms   44 ms   75 ms   51 ms   59 ms   40 ms   56 ms   41 ms   40 ms  ae-3-89.edge2.Dallas3.Level3.net [4.68.19.140]
17  322 ms  320 ms  321 ms  320 ms  320 ms  321 ms  320 ms  321 ms  331 ms   *      [192.205.35.141]
18  321 ms  321 ms   *      320 ms  320 ms  325 ms  321 ms  321 ms   *      325 ms  tbr2.dlstx.ip.att.net [12.122.86.210]
19  321 ms  321 ms  321 ms  321 ms  321 ms  320 ms  320 ms  320 ms  320 ms  320 ms  cr2.dlstx.ip.att.net [12.122.18.229]
20  320 ms  322 ms  322 ms   *      321 ms  323 ms   *      321 ms  322 ms  543 ms  gar5.dlstx.ip.att.net [12.122.138.5]
21  N/A     320 ms  320 ms  322 ms  320 ms  320 ms  320 ms  320 ms  320 ms   *      mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
22  322 ms  321 ms  321 ms  349 ms  321 ms  321 ms  321 ms  321 ms  322 ms  320 ms  mdf1-bi8k-2-eth-2-1.dal1.attens.net [63.241.192.198]
23  320 ms  320 ms  320 ms  328 ms   *      321 ms  321 ms  322 ms  322 ms  321 ms  [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 10, Received = 9, Lost = 1 (10.0%)
Round Trip Times: Minimum = 320ms, Maximum = 328ms, Average = 321ms
Title: Re: Comcast user connection issues
Post by: mrroadkill69 on December 21, 2008, 01:18:07 PM
Here is my trace from Salem, OR. Comcast is my ISP

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     5 ms     5 ms    12 ms  73.93.40.1
  3     7 ms     5 ms     6 ms  68.85.150.145
  4     8 ms     7 ms     7 ms  te-7-1-ar01.beaverton.or.bverton.comcast.net [68
.87.216.5]
  5    11 ms    11 ms    10 ms  te-0-4-0-5-cr01.portland.or.ibone.comcast.net [6
8.86.90.245]
  6    15 ms    13 ms    14 ms  pos-0-0-0-0-cr01.seattle.wa.ibone.comcast.net [6
8.86.85.205]
  7   111 ms   222 ms   220 ms  te-3-3.car1.Seattle1.Level3.net [4.79.104.109]
  8    14 ms    13 ms    13 ms  ge-1-0-0-51.gar1.Seattle1.Level3.net [4.68.105.9
]
  9    30 ms    30 ms    29 ms  att-level3-oc48.seattle1.level3.net [4.68.127.11
0]
 10     *      320 ms   319 ms  tbr1.st6wa.ip.att.net [12.127.6.58]
 11   319 ms   320 ms   319 ms  cr1.st6wa.ip.att.net [12.122.23.129]
 12     *      320 ms   319 ms  cr2.sffca.ip.att.net [12.122.31.194]
 13   318 ms   320 ms   319 ms  cr2.la2ca.ip.att.net [12.122.31.133]
 14   318 ms   320 ms   320 ms  cr2.dlstx.ip.att.net [12.122.28.177]
 15   319 ms     *      319 ms  gar5.dlstx.ip.att.net [12.122.138.5]
 16     *      319 ms   319 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255
.82]
 17   319 ms   320 ms   321 ms  mdf1-bi8k-2-eth-2-3.dal1.attens.net [63.241.192.
222]
 18   322 ms   321 ms   320 ms  206.16.60.38

Trace complete.

I was unable to get on this morning Pings were above 350. So much for the new Docsis 3 evolution

Title: Re: Comcast user connection issues
Post by: Chapel on December 21, 2008, 01:23:51 PM
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>tracert 206.16.60.38

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1     *        *        *     Request timed out.
  2     6 ms     7 ms     7 ms  68.85.148.141
  3    10 ms    10 ms    10 ms  te-7-3-ar01.troutdale.or.bverton.comcast.net [68
.87.216.126]
  4    15 ms    13 ms    14 ms  68.86.90.225
  5    14 ms    31 ms    14 ms  te-3-2.car1.Seattle1.Level3.net [4.79.104.105]
  6    16 ms    14 ms    21 ms  ge-2-0-0-52.gar1.Seattle1.Level3.net [4.68.105.4
1]
  7    29 ms    29 ms    30 ms  att-level3-oc48.seattle1.level3.net [4.68.127.11
0]
  8   322 ms     *      321 ms  tbr1.st6wa.ip.att.net [12.127.6.58]
  9   320 ms   320 ms   321 ms  cr1.st6wa.ip.att.net [12.122.23.129]
 10   322 ms   326 ms   326 ms  cr2.sffca.ip.att.net [12.122.31.194]
 11     *      320 ms   320 ms  cr2.la2ca.ip.att.net [12.122.31.133]
 12   324 ms   320 ms   321 ms  cr2.dlstx.ip.att.net [12.122.28.177]
 13   321 ms   319 ms   320 ms  gar5.dlstx.ip.att.net [12.122.138.5]
 14   323 ms     *      321 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255
.78]
 15     *      322 ms   327 ms  mdf1-bi8k-2-eth-2-3.dal1.attens.net [63.241.192.
222]
 16   321 ms   321 ms   321 ms  206.16.60.38

Trace complete.


Yup having the same issues as roadkill, down in Eugene, OR
Title: Re: Comcast user connection issues
Post by: Dawger on December 21, 2008, 01:36:39 PM
Fios , Since it is FIber runs directly on all verizon controlled equipment

I do not beleive they use either l3 or att

I had fios for 2 years and beleive me i was hitting 80 plus frame rate

ISP and frame rate ain't remotely connected, FWIW.

Title: Re: Comcast user connection issues
Post by: oceans11 on December 21, 2008, 01:38:42 PM
ISP and frame rate ain't remotely connected, FWIW.




Skuzzy

the connection to your server is what determines frame rrate correct?
The faster and cleaner the connection the better off you are I thought
Title: Re: Comcast user connection issues
Post by: Dawger on December 21, 2008, 01:52:39 PM
A good connection is always desirable but it still doesn't have anything to do with video performance.

Video performance is all related to hardware in your machine and its software/settings.

Frame rate is a video performance measurement.

Higher FPS is desirable (to a point)

Lower latency is desirable in an internet connection.
Title: Re: Comcast user connection issues
Post by: Dawger on December 21, 2008, 02:58:12 PM
My ping to HTC MA is now decent on ping plotter. DOn't know why but it is
Title: Re: Comcast user connection issues
Post by: Dustoff2 on December 21, 2008, 03:28:06 PM
could possible be because of me. At about the 13:00 hour, I logged onto Comcast live chat. After about half an hour of trying to convince them that there is an issue from level3 to att.com, they finally did a traceroute to 206.16.60.38 from their location. The tier 3 tech typed back that they do see the problem and will escalate the issue. I also was on ventrillo with a squadie at the same time he was doing the same thing. Perhaps they got the message? I don't know, but would like to think so. I was getting 323 ms at the att.net, now its around 80 ms.

dustoff  :salute
Title: Re: Comcast user connection issues
Post by: Rich46yo on December 21, 2008, 06:02:02 PM
could possible be because of me. At about the 13:00 hour, I logged onto Comcast live chat. After about half an hour of trying to convince them that there is an issue from level3 to att.com, they finally did a traceroute to 206.16.60.38 from their location. The tier 3 tech typed back that they do see the problem and will escalate the issue. I also was on ventrillo with a squadie at the same time he was doing the same thing. Perhaps they got the message? I don't know, but would like to think so. I was getting 323 ms at the att.net, now its around 80 ms.

dustoff  :salute

I asked on the phone for a tier 3 tech and she told me she didnt know what that was.

I can live with tech issues but I cant live with stupid people blowing me off even when they are at least smart enough to know, that I know, they are blowing me off. They once sent a tech by who couldnt speak english. :lol I had to get a mexican buddy on the phone to translate for us.
Title: Re: Comcast user connection issues
Post by: oceans11 on December 21, 2008, 06:14:46 PM
Can you guys post what your symptom's are
Like what is your computer doing .

My system hiccups through out the GAME and lately its been just  locksing up but it was doing fine last week


Is thiswhat everybody else on Comcast is experiencing?

Thanks
Title: Re: Comcast user connection issues
Post by: Dustoff2 on December 21, 2008, 06:15:36 PM
Unfortunately, I am a comm tech 3 for the company. It even took me a great deal of time to get to the right person that even new what I was talking about to do a traceroute.  :(    and trying to convince them that my system was good on my end, modem levels where good, ect. Next time I'm going to go the internal route and just call dispatch to get to a local tier 3 tech.

but I have to add that once I got to the right person that could help me, it was handled in a timely professional manner.

dustoff  :salute

Title: Re: Comcast user connection issues
Post by: BaldEagl on December 21, 2008, 06:46:41 PM
Can you guys post what your symptom's are
Like what is your computer doing .

My system hiccups through out the GAME and lately its been just  locksing up but it was doing fine last week


Is thiswhat everybody else on Comcast is experiencing?

Thanks

No.  We (I) lose UDP then get disconnected.  Your problem sounds like either a heat or power issue.  It could also be caused by programs running in the background but the first two are more likely.
Title: Re: Comcast user connection issues
Post by: oceans11 on December 21, 2008, 08:17:13 PM
No.  We (I) lose UDP then get disconnected.  Your problem sounds like either a heat or power issue.  It could also be caused by programs running in the background but the first two are more likely.

Impossible
I have had this system running aces for two years now
Besides it being a monster I went from XP to vista premium two weeks ago .

It was working fine untill sat Morning when all these problems started to happen
Now I do have comcast and I have already posted my trace route.

BUT perhaps I will re-vert back to XP to see if i still get the issues.

SYSTEM
amd quad 2.8
6 gig mem (corsair)
two raptor 15 k sata
evga 9 series video card
Cool master 800 watt PS
Asus P5 MB
4 fans full size case
Title: Re: Comcast user connection issues
Post by: OOZ662 on December 21, 2008, 10:11:25 PM
Besides it being a monster I went from XP to vista premium two weeks ago .

There's a mistake.

BUT perhaps I will re-vert back to XP

There's a solution.
Title: Re: Comcast user connection issues
Post by: ImADot on December 21, 2008, 10:24:47 PM
I'm running Vista Ultimate on a machine I build a couple of weeks ago.  Have had zero problems until a few days ago.  I've posted my PingPlotter results earlier.  The symptoms I've seen have been ping times in the high 300's instead of 60-80, and many dropped packets.  The problem seems to be between Level3 (Comcast's backbone provider) and ATT (seemingly the provider for HTC).

So I see it as warps, and discos.  Seems to be worse during the day, which seems logical since everyone's busy trying to buy their last-minute Xmas gifts online.
Title: Re: Comcast user connection issues
Post by: Skuzzy on December 22, 2008, 06:06:43 AM
No, it was another bad route propagation.  Bad routes can be propagated from any ISP.

Comcast took ownership of the problem, which means either they are the ones propagating the bad routes, or they were being good guys and working with the ISP who was propagating the bad route.

Richyo, first tier support at almost any large ISP is only going to work onthe local Internet connection.  For something like this, they are worthless. 


oceans11, frame rate has nothing to do with the network connection as the network connection works asynchronously to the game.
Title: Re: Comcast user connection issues
Post by: oceans11 on December 22, 2008, 06:49:38 AM
oceans11, frame rate has nothing to do with the network connection as the network connection works asynchronously to the game.


Understood

I am getting between 60 and 65. I thouight that was good
But now I am getting this lock up situation.
Ive followed your vista performace guide suggestions also .

Any suggestions before I revert back ?

Will start around 11 am est today if you cannot think of a good reason .
I need to rule out comcast over a local issue
Title: Re: Comcast user connection issues
Post by: The Fugitive on December 22, 2008, 08:36:21 AM
oceans11, start a new thread and post your Dxdiag report....well the first third, the whole thing won't fit. Someone might see a problem in it that may be causing you a problem.
Title: Re: Comcast user connection issues
Post by: Skuzzy on December 22, 2008, 10:22:58 AM
By the way, for those who want to contend it is an AT&T issue.

First off, if it was an AT&T issue, it would effect every player, regardless of which ISP they were coming from.

Secondly, if it was a fat-fingered route table for Comcast being propagated from AT&T, it would be in Comcast's best interest to get it fixed.

Thirdly, if it is a fat-fingered route table in Comcast, for the AT&T block of IP addresses, they are still the only ones who can fix it.

Does it mean AT&T is not to blame at all?  No.  It means the both AT&T and Comcast need to be told about things like this so they can finally get together and fix it.  Pointing fingers is really an exercise in futility in these types of problems.

The problem with both of these companies, is their arrogance is just as big as they are.  They will not pay attention to one user who is having a problem.  That is why it takes a flood of calls to make things happen.  In their minds, they can do no wrong at all.  They will always put the burden of proof on the end user when there is a problem.
Title: Re: Comcast user connection issues
Post by: Rich46yo on December 22, 2008, 10:46:36 AM
Quote
Richyo, first tier support at almost any large ISP is only going to work on the local Internet connection.  For something like this, they are worthless. 


Yeah, you know what they told me when I said I wanted tier 3 support? They said this is the only support available. :lol Then they told me the only thing they could do is send out a tech, hopefully one that speaka da Eeeengleeeesh, and he could check my problem. :lol And if he found no problem, that is if I can get online, they would have to charge me. :lol

I told her the entire gaming community knows what the story is and I know your just blowing me off.

My God what a lousy company. After X-mas Im going to have to make some kind of move. I just have to much going on right now.
Title: Re: Comcast user connection issues
Post by: DCCBOSS on December 22, 2008, 11:12:03 AM


Yeah, you know what they told me when I said I wanted tier 3 support? They said this is the only support available. :lol Then they told me the only thing they could do is send out a tech, hopefully one that speaka da Eeeengleeeesh, and he could check my problem. :lol And if he found no problem, that is if I can get online, they would have to charge me. :lol

I told her the entire gaming community knows what the story is and I know your just blowing me off.

My God what a lousy company. After X-mas Im going to have to make some kind of move. I just have to much going on right now.


Call them back or use the on line help with live chat and give them the IP # that posted on the message board and tell them to run the trace, I would keep on calling until they cooperate or as for their supervisor.

DCCBOSS :salute
Title: Re: Comcast user connection issues
Post by: VonMessa on December 22, 2008, 12:03:02 PM
By the way, for those who want to contend it is an AT&T issue.

First off, if it was an AT&T issue, it would effect every player, regardless of which ISP they were coming from.

Secondly, if it was a fat-fingered route table for Comcast being propagated from AT&T, it would be in Comcast's best interest to get it fixed.

Thirdly, if it is a fat-fingered route table in Comcast, for the AT&T block of IP addresses, they are still the only ones who can fix it.

Does it mean AT&T is not to blame at all?  No.  It means the both AT&T and Comcast need to be told about things like this so they can finally get together and fix it.  Pointing fingers is really an exercise in futility in these types of problems.

The problem with both of these companies, is their arrogance is just as big as they are.  They will not pay attention to one user who is having a problem.  That is why it takes a flood of calls to make things happen.  In their minds, they can do no wrong at all.  They will always put the burden of proof on the end user when there is a problem.

I would find some validity in this, as the issue is usually PEBKAC error and a waste of tech support time to fix a problem.  I find this at work a lot.  "Dan, my POS computer is broken.  Can you come up and fix it?" It is usually something stupid.


  I also encountered this a lot at a mower shop that I used to work at.

CUSTOMER:  "My mower wont start"
ME:  "Is there gas in it?"
CUSTOMER: "Of course I put gas in it, do you think I'm an idiot?"
ME:  "Not at all, sir, but that is the first thing in a mechanic's troubleshooting list.  I'll send someone over to pick it up"

They get really pissed when they get a bill for $60.  ($50 p/u and delivery fee and $10 for the fuel)

  Unfortunately, they (tech support folks) are oftentimes very rude to the end user and have an attitude of they know soooo much more because their little tech support flow-chart book imbues them with more knowledge than a "normal" person.

But, as you say, a flood of calls cannot be ignored.  :)
Title: Re: Comcast user connection issues
Post by: oceans11 on December 23, 2008, 11:08:00 AM
Skuzzy .
Fixed my problem , WENT BACK TO XP

However I think I might have uncovered what is causing everynbody's problem
There seems to be hardware problem with broadband users that also have VOIP service.
Most ISp's had to comply with   CALEA

"http://en.wikipedia.org/wiki/Communications_Assistance_for_Law_Enforcement_Act
Seems about to weeks ago this new protocol was initiated
I came across it when I logged into my  cisco pix.
It seems Comcast has uploaded to there broadband customers.
Is there a connection to the problem .
I am not sure but I blocked the port and suddenly I am not warping anymore.

CONCLUSION: I am not sure if Vista was my problem since I am not about to blow my system away
and do another install but I find it no coincidence that this coincided with when the troubles have started

Title: Re: Comcast user connection issues
Post by: Overlag on December 23, 2008, 07:26:12 PM
Tracing route to 206.16.60.38 over a maximum of 30 hops

  1    23 ms    99 ms    99 ms  192.168.0.1
  2    18 ms    13 ms    13 ms  78.33.38.42
  3    15 ms    12 ms    12 ms  78.33.38.41
  4   944 ms   205 ms   166 ms  62.249.192.121
  5    16 ms    12 ms    13 ms  87.127.236.102
  6    45 ms   211 ms   219 ms  64.214.147.1
  7    88 ms    88 ms  4294966576 ms  64.212.107.98
  8   130 ms  4294966622 ms   131 ms  12.122.86.94
  9   939 ms   131 ms   129 ms  12.122.16.145
 10   940 ms   131 ms   130 ms  12.122.5.242
 11   131 ms   130 ms   130 ms  12.122.3.226
 12   130 ms   130 ms   130 ms  12.122.2.209
 13   939 ms   129 ms   131 ms  12.122.2.125
 14   939 ms   130 ms   129 ms  12.122.28.73
 15   131 ms   131 ms   939 ms  12.122.28.66
 16   129 ms   130 ms   129 ms  12.122.138.5
 17   131 ms   130 ms   130 ms  12.122.255.82
 18   130 ms   940 ms   130 ms  63.241.192.218
 19   130 ms   131 ms   130 ms  206.16.60.38

Trace complete.

Pinging 206.16.60.38 with 32 bytes of data:

Reply from 206.16.60.38: bytes=32 time=937ms TTL=240
Reply from 206.16.60.38: bytes=32 time=129ms TTL=240
Reply from 206.16.60.38: bytes=32 time=129ms TTL=240
Reply from 206.16.60.38: bytes=32 time=938ms TTL=240
Reply from 206.16.60.38: bytes=32 time=128ms TTL=240
Reply from 206.16.60.38: bytes=32 time=129ms TTL=240
Reply from 206.16.60.38: bytes=32 time=129ms TTL=240
Reply from 206.16.60.38: bytes=32 time=128ms TTL=240
Reply from 206.16.60.38: bytes=32 time=-679ms TTL=240
Reply from 206.16.60.38: bytes=32 time=937ms TTL=240
Reply from 206.16.60.38: bytes=32 time=128ms TTL=240
Reply from 206.16.60.38: bytes=32 time=128ms TTL=240
Reply from 206.16.60.38: bytes=32 time=129ms TTL=240
Reply from 206.16.60.38: bytes=32 time=937ms TTL=240
Reply from 206.16.60.38: bytes=32 time=128ms TTL=240
Reply from 206.16.60.38: bytes=32 time=938ms TTL=240
Reply from 206.16.60.38: bytes=32 time=128ms TTL=240
Reply from 206.16.60.38: bytes=32 time=128ms TTL=240
Reply from 206.16.60.38: bytes=32 time=938ms TTL=240
Reply from 206.16.60.38: bytes=32 time=937ms TTL=240
Reply from 206.16.60.38: bytes=32 time=128ms TTL=240
Reply from 206.16.60.38: bytes=32 time=938ms TTL=240
Reply from 206.16.60.38: bytes=32 time=128ms TTL=240
Reply from 206.16.60.38: bytes=32 time=129ms TTL=240
Reply from 206.16.60.38: bytes=32 time=938ms TTL=240
Reply from 206.16.60.38: bytes=32 time=129ms TTL=240
Reply from 206.16.60.38: bytes=32 time=128ms TTL=240
Reply from 206.16.60.38: bytes=32 time=128ms TTL=240
Reply from 206.16.60.38: bytes=32 time=938ms TTL=240
Reply from 206.16.60.38: bytes=32 time=128ms TTL=240
Reply from 206.16.60.38: bytes=32 time=938ms TTL=240
Reply from 206.16.60.38: bytes=32 time=938ms TTL=240
Reply from 206.16.60.38: bytes=32 time=938ms TTL=240

Been laggin quiet bad lately to the point i just aint botherd to come on. Will be back in the new year i guess.
Title: Re: Comcast user connection issues
Post by: Anaxogoras on December 24, 2008, 11:18:40 AM
Comcast user here in western Indiana.  I average less than 1 disco a month, my ping time is usually around 60ms but it seems to have gone up during the holidays to 90-100ms.  Anyway, here's my stuff:

---------------------------

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Compaq_Owner>ping 206.16.60.38

Pinging 206.16.60.38 with 32 bytes of data:

Reply from 206.16.60.38: bytes=32 time=92ms TTL=237
Reply from 206.16.60.38: bytes=32 time=102ms TTL=237
Reply from 206.16.60.38: bytes=32 time=92ms TTL=237
Reply from 206.16.60.38: bytes=32 time=97ms TTL=237

Ping statistics for 206.16.60.38:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 92ms, Maximum = 102ms, Average = 95ms

C:\Documents and Settings\Compaq_Owner>tracert 206.16.60.38

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  192.168.1.1
  2     *        *        *     Request timed out.
  3     9 ms     8 ms     9 ms  ge-1-2-ur01.lafayette.in.indiana.comcast.net [68.85.178.193]
  4     9 ms     9 ms     9 ms  68.85.176.237
  5    21 ms    22 ms    22 ms  68.85.177.46
  6    24 ms    28 ms    25 ms  68.87.229.109
  7    28 ms    25 ms    26 ms  pos-0-13-0-0-cr01.chicago.il.ibone.comcast.net [68.86.90.53]
  8    56 ms    28 ms    25 ms  xe-10-1-0.edge1.Chicago2.Level3.net [4.71.248.17]
  9    26 ms    29 ms    28 ms  vlan51.ebr1.Chicago2.Level3.n et [4.69.138.158]
 10    27 ms    33 ms    35 ms  ae-6.ebr1.Chicago1.Level3.net [4.69.140.189]
 11    34 ms    28 ms    26 ms  ae-14-55.car4.Chicago1.Level3.net [4.68.101.136]

 12    28 ms    29 ms    26 ms  192.205.33.209
 13    91 ms    90 ms    91 ms  tbr2.cgcil.ip.att.net [12.123.6.70]
 14    91 ms    91 ms    93 ms  cr2.cgcil.ip.att.net [12.122.17.221]
 15    90 ms    91 ms    94 ms  cr2.sl9mo.ip.att.net [12.122.2.22]
 16   105 ms    91 ms    89 ms  cr1.sl9mo.ip.att.net [12.122.2.217]
 17    92 ms    90 ms    91 ms  cr2.dlstx.ip.att.net [12.122.3.221]
 18    97 ms    91 ms    90 ms  gar5.dlstx.ip.att.net [12.122.138.5]
 19    94 ms    90 ms    90 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
 20    90 ms    91 ms    90 ms  mdf1-bi8k-2-eth-2-6.dal1.attens.net [63.241.192.46]
 21    93 ms    90 ms    94 ms  206.16.60.38

Trace complete.
Title: Re: Comcast user connection issues
Post by: TilDeath on December 26, 2008, 12:47:05 PM
I don't know if this will help, but I am sure a flood of complaints will get some sort of attention. Anyone familar with this site? http://comcastmustdie.com (http://comcastmustdie.com)  Believe it or not Comcast monitors the site and does take care of the problems (to an extent) listed on the site and the issues with Comcast discussed.
Title: Re: Comcast user connection issues
Post by: Anaxogoras on December 26, 2008, 03:08:37 PM
Great link!  Bob Garfield also has a great show called On The Media, broadcast by WNYC.
Title: Re: Comcast user connection issues
Post by: Infidelz on December 26, 2008, 08:08:46 PM
hello Skuzzy. I don't have comcast but I have been disconnected several times today. Its OK once in a while, until you have a successfull ME262 mission and disco just prior to landing. Not only do you lose the system message you lose your perk points. Very dissapointed.

here is my tracert

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>tracert 206.16.60.38

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1     2 ms     2 ms     2 ms  192.168.1.1
  2    11 ms    13 ms    18 ms  d-216-36-16-1.cpe.metrocast.net [216.36.16.1]
  3    11 ms    13 ms    12 ms  static-216-36-30-138.cpe.metrocast.net [216.36.3
0.138]
  4    13 ms    13 ms    12 ms  static-216-36-30-246.cpe.metrocast.net [216.36.3
0.246]
  5    11 ms    13 ms    12 ms  dca-edge-19.inet.qwest.net [65.127.222.209]
  6    13 ms    13 ms    12 ms  dca-core-02.inet.qwest.net [205.171.9.41]
  7     *        *       14 ms  dcx-core-01.inet.qwest.net [67.14.28.2]
  8    13 ms    17 ms    18 ms  dcp-brdr-02.inet.qwest.net [205.171.251.34]
  9    14 ms    17 ms    18 ms  192.205.34.253
 10    62 ms    60 ms    58 ms  tbr2.wswdc.ip.att.net [12.123.8.190]
 11    60 ms    59 ms    61 ms  cr2.wswdc.ip.att.net [12.122.16.93]
 12    59 ms    58 ms    58 ms  cr1.attga.ip.att.net [12.122.1.173]
 13    59 ms    58 ms    62 ms  cr2.attga.ip.att.net [12.122.2.134]
 14    61 ms    60 ms    63 ms  cr1.dlstx.ip.att.net [12.122.2.225]
 15    59 ms    58 ms    60 ms  gar5.dlstx.ip.att.net [12.122.139.5]
 16    61 ms    61 ms    60 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255
.82]
 17    62 ms    59 ms    63 ms  mdf1-bi8k-2-eth-2-3.dal1.attens.net [63.241.192.
222]
 18    60 ms    61 ms    61 ms  206.16.60.38

Trace complete.

C:\Documents and Settings\Owner>

Number seven was a bit sluggish its seemed. Does everyone go through att to get to your servers? Maybe they have something in common with the problem?

INFIDELZ.
Title: Re: Comcast user connection issues
Post by: Skuzzy on December 27, 2008, 07:12:20 AM
Hop number 7 is in your ISP's network.  It's not even the gateway to the Internet.  You need to contact QWest abot it.
Title: Re: Comcast user connection issues
Post by: Infidelz on December 28, 2008, 10:24:54 AM
My ISP is metrocast. I see what your saying there, I will contact the CEO of QWest personnally as soon as he gets his bailout money.

I ran another one after a crash on the 27th and Windows gave ATT 2 stars for their performance (Number 11). My ISP only got 1 star (number 4). Clearly Att got more stars. Which side of the St. Louis Gateway is that on? 


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Scubi>tracert 206.16.60.38

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  192.168.1.1
  2     9 ms     9 ms     8 ms  d-216-36-16-1.cpe.metrocast.net [216.36.16.1]
  3     *       10 ms    12 ms  static-216-36-30-138.cpe.metrocast.net [216.36.30.138]
  4    13 ms    12 ms     *     static-216-36-30-246.cpe.metrocast.net [216.36.30.246]
  5    14 ms    13 ms    12 ms  dca-edge-19.inet.qwest.net [65.127.222.209]
  6    11 ms    13 ms    13 ms  dca-core-02.inet.qwest.net [205.171.9.41]
  7    14 ms    12 ms    13 ms  dcx-core-01.inet.qwest.net [67.14.28.2]
  8    15 ms    11 ms    14 ms  dcp-brdr-02.inet.qwest.net [205.171.251.34]
  9    17 ms    16 ms    12 ms  192.205.34.253
 10    61 ms    61 ms    58 ms  tbr2.wswdc.ip.att.net [12.123.8.190]
 11     *        *       58 ms  cr2.wswdc.ip.att.net [12.122.16.93]
 12    59 ms    58 ms    57 ms  cr1.attga.ip.att.net [12.122.1.173]
 13    59 ms    60 ms    57 ms  cr2.attga.ip.att.net [12.122.2.134]
 14    58 ms    58 ms    56 ms  cr1.dlstx.ip.att.net [12.122.2.225]
 15    57 ms    57 ms    59 ms  gar5.dlstx.ip.att.net [12.122.139.5]
 16    57 ms    57 ms    57 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
 17    57 ms    57 ms    59 ms  mdf1-bi8k-2-eth-2-3.dal1.attens.net [63.241.192.222]
 18    56 ms    58 ms    58 ms  206.16.60.38

Trace complete.

C:\Documents and Settings\Scubi>
Title: Re: Comcast user connection issues
Post by: Skuzzy on December 28, 2008, 11:35:43 AM
Once it starts happening, any information after that can be considered useless as that information will be tainted by the problems with the previous hops.

You need to contact your ISP.
Title: Re: Comcast user connection issues
Post by: SKColt on January 06, 2009, 08:21:22 AM
I am in Wichita KS. I just began having disco issues last night.

Colt

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 1/6/2009 8:17:10 AM to 1/6/2009 8:19:25 AM

 1   *       *       *       *       *       *       *       *       *       *       [-]
 2   10 ms   11 ms    8 ms   10 ms   13 ms   11 ms   10 ms    9 ms    9 ms   11 ms  ip72-202-128-1.ks.ks.cox.net [72.202.128.1]
 3   11 ms    9 ms   10 ms    9 ms    9 ms   16 ms   10 ms   11 ms    7 ms   10 ms  ip70-183-64-37.ks.ks.cox.net [70.183.64.37]
 4   16 ms   18 ms   18 ms   18 ms   17 ms   18 ms   18 ms   17 ms   17 ms   18 ms  kscydsrj02-ae2.rd.ks.cox.net [70.183.71.105]
 5   *       *       *       *       *       *       *       *       *       *       [-]
 6   *       *       *       *       *       *       *       *       *       *       [-]
 7   24 ms   24 ms   27 ms   23 ms   23 ms   25 ms   25 ms   24 ms   25 ms   25 ms  mtc3dsrj01-ge-100.0.rd.ok.cox.net [68.1.0.113]
 8   *       *       *       *       *       *       *       *       *       *       [-]
 9  N/A     N/A      30 ms  N/A     N/A     N/A     N/A     N/A     N/A      30 ms  ae-4-99.edge2.Dallas3.Level3.net [4.68.19.204]
10  N/A     N/A     N/A     N/A     N/A     N/A      75 ms   29 ms   *       *      [192.205.35.225]
11  N/A     N/A     N/A      29 ms   *       *       *       *       *       28 ms  tbr1.dlstx.ip.att.net [12.122.86.206]
12   *       31 ms   31 ms   29 ms   29 ms   28 ms   37 ms   29 ms   31 ms   31 ms  cr1.dlstx.ip.att.net [12.122.18.129]
13   55 ms   *       *       *       *       *       *       *       *       *      cr2.sl9mo.ip.att.net [12.122.2.22]
14   *       56 ms   54 ms   57 ms   53 ms   57 ms   56 ms   57 ms   56 ms   54 ms  cr1.sl9mo.ip.att.net [12.122.2.217]
15   58 ms   57 ms   56 ms   55 ms   56 ms   54 ms   55 ms   56 ms   56 ms   56 ms  cr2.dlstx.ip.att.net [12.122.3.221]
16  191 ms   *       *       *       *       *       *       *       *       *      gar5.dlstx.ip.att.net [12.122.138.5]
17   32 ms   29 ms   28 ms   30 ms   30 ms   33 ms   28 ms   29 ms   29 ms   30 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 = 28ms, Maximum = 33ms, Average = 29ms
Title: Re: Comcast user connection issues
Post by: Skuzzy on January 06, 2009, 09:11:17 AM
You need to get that to Cox.  The problems you are having lies within Cox's network.  First tier support will tell you nothing it wrong, as they are only responsible for your immediate Inter connection.  You will need to get this escalated and point them to the above post you have made.

Good luck.
Title: Re: Comcast user connection issues
Post by: SKColt on January 06, 2009, 11:32:37 PM
 I may have "stumbled" onto a solution.....maybe. The COX upper tier engineer pulled the recent logs for my modem, and told me the transmit levels were high, and had exceeded expected levels several times in the last three days. When I looked at the modem stats, the transmit level was at the upper edge. He suggested that COX come to the house to check and set levels.
 When I put my new system together this past weekend, I did not re-install my HDTV tuner card. I have a dedicated CATV drop for my PC desk. It hits a splitter, that feeds the modem and the HDTV tuner. Since I did not hook the tuner back up, I had an unterminated RF port on the splitter. I removed the splitter, and hooked the cable directly to the modem. The modem then displayed a transmit level 3.5Db lower then before, well within the range the COX engineer expected me to have.
 The ping plot did not look much better, but I then flew in AH for 4 straight hours without a burp! SKHammer emailed a ping plot to me(he is on the same ISP here in Wichita. He utilizes the same paths as I do, and never gets discoed. His plot had some of the same "anomalies" as mine.)
 COX is still coming out tomorrow morning to check the levels and the ping plots. Fingers remain crossed!!

Colt