Author Topic: Server down? (Read 611 times)

Krusty · « **on:** November 17, 2006, 06:30:46 PM »

Anybody not getting a connection right now?

edit, Trusty old "Pingtrace" tells me that AT&T is screwing around again. Almost total loss of packets through their Dallas routing. Crappy AT&T...

Waffle · « **Reply #1 on:** November 17, 2006, 06:47:02 PM »

Dallas has been horrible for me the last few weeks.

Krusty · « **Reply #2 on:** November 17, 2006, 06:49:43 PM »

Last time it was like this for about 24 hours straight... Hopefully it won't screw over my weekend flying! Argh!

EDIT:

Hop IP Address Host Name Sent Recv RTT Av RTT Min RTT Max RTT % Loss

1 192.168.0.1 [Unknown] 15 15 0ms 0ms 0ms 0ms 0%
2 --- [No response] --- --- --- --- --- --- ---
3 68.86.105.153 [Unknown] 15 15 9ms 12ms 8ms 37ms 0%
4 68.86.103.126 10g-9-1-ur02.arvada.co.denver.comcast.net 15 15 11ms 10ms 9ms 15ms 0%
5 68.86.103.41 10g-8-2-ar01.aurora.co.denver.comcast.net 15 15 13ms 10ms 8ms 17ms 0%
6 68.86.103.170 [Unknown] 15 15 9ms 10ms 8ms 19ms 0%
7 12.124.157.53 [Unknown] 15 15 11ms 9ms 9ms 13ms 0%
8 12.127.4.154 gbr2-a30s2.dvmco.ip.att.net 15 1 30ms 30ms 30ms 30ms 94%
9 12.122.1.42 tbr2-p013601.dvmco.ip.att.net 15 1 34ms 34ms 34ms 34ms 94%
10 12.122.12.125 tbr2-cl33.dlstx.ip.att.net 15 1 33ms 33ms 33ms 33ms 94%
11 12.122.12.90 gbr6-p40.dlstx.ip.att.net 15 1 29ms 29ms 29ms 29ms 94%
12 12.123.17.13 ar13-p3110.dlstx.ip.att.net 14 1 31ms 31ms 31ms 31ms 93%
13 12.116.144.38 [Unknown] 14 14 33ms 37ms 33ms 42ms 0%
14 12.193.161.229 beta.hitechcreations.com 14 14 34ms 37ms 34ms 51ms 0%

zorstorer · « **Reply #3 on:** November 17, 2006, 09:43:47 PM »

Quote

Originally posted by Krusty
Last time it was like this for about 24 hours straight... Hopefully it won't screw over my weekend flying! Argh!

EDIT:

Hop IP Address Host Name Sent Recv RTT Av RTT Min RTT Max RTT % Loss

1 192.168.0.1 [Unknown] 15 15 0ms 0ms 0ms 0ms 0%
2 --- [No response] --- --- --- --- --- --- ---
3 68.86.105.153 [Unknown] 15 15 9ms 12ms 8ms 37ms 0%
4 68.86.103.126 10g-9-1-ur02.arvada.co.denver.comcast.net 15 15 11ms 10ms 9ms 15ms 0%
5 68.86.103.41 10g-8-2-ar01.aurora.co.denver.comcast.net 15 15 13ms 10ms 8ms 17ms 0%
6 68.86.103.170 [Unknown] 15 15 9ms 10ms 8ms 19ms 0%
7 12.124.157.53 [Unknown] 15 15 11ms 9ms 9ms 13ms 0%
8 12.127.4.154 gbr2-a30s2.dvmco.ip.att.net 15 1 30ms 30ms 30ms 30ms 94%
9 12.122.1.42 tbr2-p013601.dvmco.ip.att.net 15 1 34ms 34ms 34ms 34ms 94%
10 12.122.12.125 tbr2-cl33.dlstx.ip.att.net 15 1 33ms 33ms 33ms 33ms 94%
11 12.122.12.90 gbr6-p40.dlstx.ip.att.net 15 1 29ms 29ms 29ms 29ms 94%
12 12.123.17.13 ar13-p3110.dlstx.ip.att.net 14 1 31ms 31ms 31ms 31ms 93%
13 12.116.144.38 [Unknown] 14 14 33ms 37ms 33ms 42ms 0%
14 12.193.161.229 beta.hitechcreations.com 14 14 34ms 37ms 34ms 51ms 0%
[/B]

You know they only die when someone is not there to fix it

Skuzzy · « **Reply #4 on:** November 18, 2006, 08:09:24 AM »

You do realize you are tracing to the WEB server, not the game servers? They are in two different physical locations.

Try tracing to 206.16.60.38.

By the way, I tried tracing back to your third hop from the game server and as soon as the trace hits Comcast's network it really takes a dive. Lot of timeouts and packet loss. It is an asynchronous route.