Comcast user connection issues

[BaldEagl]

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?

[Paladin3]

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.

[Skuzzy]

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.

[Paladin3]

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  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?

[Paladin3]

Just saw how I can save it, so I'll try to do that as well. What length of time is preferred for diagnosis?

[Skuzzy]

Between 3 and 5 minutes should be sufficient.  It should be done immediately after a disco from the arena.

[Paladin3]

Roger that sir. Much appriciated, and I have to say, great response time. 

[Paladin3]

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 

[Skuzzy]

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.

[Skuzzy]

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.

[Paladin3]

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.

[Skuzzy]

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.

[BaldEagl]

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

[BaldEagl]

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.

[Skuzzy]

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