Aces High Bulletin Board
Help and Support Forums => Technical Support => Topic started by: Vulgar on November 04, 2008, 08:09:41 AM
-
Skuzzy,
Game has become nearly unplayable these past two weeks. Have you any suggestions. It looks like it is the level3-gw.la2ca.ip.att.net [192.205.33.229] causing packet loss. Any way to get att to check their routers.
Target Name: N/A
IP: 206.16.60.39
Date/Time: 11/4/2008 6:45:39 AM to 11/4/2008 6:47:54 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 * * * * * * * * * * [-]
3 7 ms 9 ms 7 ms 15 ms 7 ms 13 ms 11 ms 7 ms 23 ms 10 ms ip68-0-128-113.tc.ph.cox.net [68.0.128.113]
4 12 ms 12 ms * 13 ms 15 ms * 17 ms 13 ms * 13 ms [72.214.144.69]
5 15 ms 12 ms 12 ms 13 ms 14 ms 26 ms 14 ms 12 ms 14 ms 13 ms chnddsrj01-so010.91.rd.ph.cox.net [70.169.76.5]
6 13 ms 13 ms 13 ms 14 ms 14 ms 13 ms 14 ms 13 ms 67 ms 16 ms ae-11-11.car2.Phoenix1.Level3.net [4.69.133.34]
7 33 ms 30 ms 27 ms 24 ms 24 ms 22 ms 35 ms 31 ms 31 ms 27 ms ae-4-4.ebr2.LosAngeles1.Level3.net [4.69.133.38]
8 23 ms 35 ms 34 ms 32 ms 30 ms 29 ms 29 ms 30 ms 32 ms 27 ms ae-62-62.csw1.LosAngeles1.Level3.net [4.69.137.18]
9 22 ms 26 ms 23 ms 28 ms 22 ms 22 ms 23 ms 34 ms 33 ms 23 ms ae-1-69.edge1.LosAngeles1.Level3.net [4.68.20.7]
10 N/A 23 ms N/A 197 ms 23 ms N/A 23 ms N/A N/A 24 ms level3-gw.la2ca.ip.att.net [192.205.33.229]
11 47 ms 46 ms 47 ms 50 ms 46 ms 62 ms 50 ms 49 ms 48 ms 48 ms cr2.la2ca.ip.att.net [12.122.129.10]
12 47 ms 47 ms 47 ms 47 ms 49 ms 46 ms 47 ms 48 ms 48 ms 49 ms cr2.dlstx.ip.att.net [12.122.28.177]
13 46 ms 47 ms 62 ms 49 ms 48 ms 53 ms 48 ms 56 ms 50 ms 47 ms gar5.dlstx.ip.att.net [12.122.138.5]
14 57 ms 49 ms 48 ms 50 ms 47 ms 47 ms 63 ms 47 ms 51 ms 52 ms mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
15 47 ms 59 ms 48 ms 51 ms 47 ms 411 ms 48 ms 47 ms 47 ms 50 ms mdf1-bi8k-1-eth-1-2.dal1.attens.net [63.241.192.202]
16 47 ms 47 ms 48 ms 48 ms 48 ms 49 ms 48 ms 48 ms 47 ms 48 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 = 47ms, Maximum = 49ms, Average = 47ms
Target Name: N/A
IP: 206.16.60.39
Date/Time: 11/4/2008 6:46:24 AM to 11/4/2008 6:48:39 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 * * * * * * * * * * [-]
3 15 ms 7 ms 13 ms 11 ms 7 ms 23 ms 10 ms 9 ms 8 ms 10 ms ip68-0-128-113.tc.ph.cox.net [68.0.128.113]
4 13 ms 15 ms * 17 ms 13 ms * 13 ms 12 ms 20 ms 29 ms [72.214.144.69]
5 13 ms 14 ms 26 ms 14 ms 12 ms 14 ms 13 ms 14 ms 13 ms 13 ms chnddsrj01-so010.91.rd.ph.cox.net [70.169.76.5]
6 14 ms 14 ms 13 ms 14 ms 13 ms 67 ms 16 ms 15 ms 14 ms 15 ms ae-11-11.car2.Phoenix1.Level3.net [4.69.133.34]
7 24 ms 24 ms 22 ms 35 ms 31 ms 31 ms 27 ms 22 ms 32 ms 33 ms ae-4-4.ebr2.LosAngeles1.Level3.net [4.69.133.38]
8 32 ms 30 ms 29 ms 29 ms 30 ms 32 ms 27 ms 24 ms 35 ms 37 ms ae-62-62.csw1.LosAngeles1.Level3.net [4.69.137.18]
9 28 ms 22 ms 22 ms 23 ms 34 ms 33 ms 23 ms 25 ms 23 ms 23 ms ae-1-69.edge1.LosAngeles1.Level3.net [4.68.20.7]
10 N/A N/A 24 ms N/A 23 ms 23 ms N/A N/A N/A 26 ms [192.205.33.225]
11 50 ms 46 ms 62 ms 50 ms 49 ms 48 ms 48 ms 47 ms 48 ms 48 ms cr2.la2ca.ip.att.net [12.122.129.10]
12 47 ms 49 ms 46 ms 47 ms 48 ms 48 ms 49 ms 47 ms 48 ms 47 ms cr2.dlstx.ip.att.net [12.122.28.177]
13 49 ms 48 ms 53 ms 48 ms 56 ms 50 ms 47 ms 48 ms 47 ms 47 ms gar5.dlstx.ip.att.net [12.122.138.5]
14 50 ms 47 ms 47 ms 63 ms 47 ms 51 ms 52 ms 47 ms 48 ms 48 ms mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
15 51 ms 47 ms 411 ms 48 ms 47 ms 47 ms 50 ms 50 ms 48 ms 49 ms mdf1-bi8k-1-eth-1-2.dal1.attens.net [63.241.192.202]
16 48 ms 48 ms 49 ms 48 ms 48 ms 47 ms 48 ms 49 ms 47 ms 50 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 = 47ms, Maximum = 50ms, Average = 48ms
-
Oh no. Cox has gone with Level3 as well.
Those guys must be giving away bandwidth. First Comcast, then Road Runner, and now Cox.
It's the gateway between Level3 and AT&T. I'll file a trouble ticket, but I am not sure what will be done as this has been a generic problem with Level3 for some time now.
-
After reading some of the other post's and noticing my hop's doubled. Along with a unreliable bandwith increase. Reads as a good advertising move. Looks like they are using Gorilla sales tactics after many years of great service. Loss of a 10% customer base has little impact over the servicing savings!
Looks like we getting bent over without the lube, despite the sales pitch! As you well know. I doubt the little guy will get a say so in this matter.
Thanks for your input and any and all help. I will attempt to send some letters, but I assume they will just get thrown in the waste basket!
I am in the states right now, will check the route when I get home in Mexico, to see if that has changed as well. My connect in the states has been great for a number of years. Superior in reliability, but not any better than when my connect in Mexico is actually working!
-
After reading some of the other post's and noticing my hop's doubled. Along with a unreliable bandwith increase. Reads as a good advertising move. Looks like they are using Guerrilla Sales tactics after many years of great service. Loss of a 10% customer base has little impact over the servicing savings!
Looks like we getting bent over without the lube, despite the sales pitch! As you well know. I doubt the little guy will get a say so in this matter.
Thanks for your input and any and all help. I will attempt to send some letters, but I assume they will just get thrown in the waste basket!
I am in the states right now, will check the route when I get home in Mexico, to see if that has changed as well. My connect in the states has been great for a number of years. Superior in reliability, but not any better than when my connect in Mexico is actually working!