ATS dieing randomly (Connection/Server Issue)

Actually,
The downtimes are where the CIA and FBI quickly fix up, edit, and delete posts and any seriously incriminating evidence that may be here on ATS all in the span of a few minutes. Similar to what they've done to wikipedia.

I'd better say i'm kidding in case a few people take me seriously.
FYI I'm in Sydney Australia and have experienced a few short downtimes too.

Had a few timeout's over the last couple of day's, these numbers didn't look massively bad though?


1 30 ms 28 ms 31 ms rt-lostg02.dial.aol.com [195.93.23.194]
2 * * * Request timed out.
3 28 ms 50 ms 30 ms accessl2-los-ae6.router.aol.com [172.17.169.108]

4 29 ms 29 ms 29 ms pop1-log-S3-0-0.atdn.net [66.185.134.197]
5 28 ms 31 ms 29 ms p16-0-0-0.r22.londen03.uk.bb.gin.ntt.net [129.25
0.8.125]
6 105 ms 105 ms 105 ms p64-2-1-0.r21.nycmny01.us.bb.gin.ntt.net [129.250.2.38]
7 111 ms 111 ms 111 ms as-0.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.9]
8 145 ms 142 ms 145 ms p64-3-1-0.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.24]
9 145 ms 145 ms 143 ms po-2.r03.dllstx09.us.bb.gin.ntt.net [129.250.4.38]
10 139 ms 141 ms 201 ms te7-1.cer01.dal01.dallas-border.com [157.238.228.10]
11 139 ms 139 ms 139 ms po51.fcr01.dal01.dallas-datacenter.com [66.228.118.150]
12 141 ms 140 ms 140 ms 75.126.76.151-static.reverse.softlayer.com [75.126.76.151]

ive been getting them also..

***removed ip***
3 10 ms 8 ms 10 ms dD5E0FB61.access.telenet.be [213.224.251.97]
4 8 ms 9 ms 7 ms dD5E0FD49.access.telenet.be [213.224.253.73]
5 10 ms 10 ms 12 ms dD5E0FD1A.access.telenet.be [213.224.253.26]
6 9 ms 9 ms 10 ms dD5E0FD1E.access.telenet.be [213.224.253.30]
7 11 ms 9 ms 14 ms dD5E0FD22.access.telenet.be [213.224.253.34]
8 17 ms 11 ms 17 ms dD5E0FD26.access.telenet.be [213.224.253.38]
9 11 ms 15 ms 10 ms dD5E0FD8E.access.telenet.be [213.224.253.142]
0 17 ms 17 ms 16 ms Level3-Telenet-London [195.50.113.185]
1 22 ms 18 ms 20 ms ae-32-52.ebr2.London1.Level3.net [4.68.116.62]
2 91 ms 89 ms 89 ms ae-4.ebr1.NewYork1.Level3.net [4.69.132.109]
3 92 ms 90 ms 89 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]
4 100 ms 94 ms 99 ms ae-64-64.ebr4.NewYork1.Level3.net [4.69.134.113]
5 100 ms 92 ms 105 ms ae-3.ebr4.Washington1.Level3.net [4.69.132.93]
6 102 ms 92 ms 105 ms ae-74-74.csw2.Washington1.Level3.net [4.69.134.182]
7 93 ms 92 ms 103 ms ae-71-71.ebr1.Washington1.Level3.net [4.69.134.133]
8 122 ms 108 ms 115 ms ae-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
9 * * * Request timed out.
0 * * * Request timed out.
1 125 ms 125 ms 124 ms unknown.Level3.net [209.246.152.246]
2 125 ms 123 ms 124 ms border3.tge3-1-bbnet1.ext1.dal.pnap.net [216.52.191.22]
3 127 ms 131 ms 128 ms softlayer-6.border3.ext1.dal.pnap.net [216.52.189.30]
4 124 ms 126 ms 126 ms po52.fcr01.dal01.dallas-datacenter.com [66.228.118.158]
5 126 ms 127 ms 129 ms 75.126.76.151-static.reverse.softlayer.com [75.126.76.151]

[edit on 24-8-2007 by justyc]

I haven't had any problems, but here's my traceroute anyway if it could prove useful:

$ traceroute www.abovetopsecret.com
traceroute to www.abovetopsecret.com (75.126.76.151), 64 hops max, 40 byte packets
1 10.0.1.1 (10.0.1.1) 0.799 ms 0.477 ms 0.476 ms
2 bdl1.nyr-ubr4.nyr.ny.cable.rcn.net (10.22.224.1) 6.009 ms 13.696 ms 5.940 ms
3 vl4.aggr1.nyw.ny.rcn.net (208.59.246.1) 8.124 ms 31.324 ms 7.580 ms
4 tge1-3.core4.nyw.ny.rcn.net (207.172.19.106) 8.130 ms 7.459 ms 8.987 ms
5 ge2-0.core2.nyw.ny.rcn.net (207.172.19.113) 35.628 ms 23.245 ms 7.940 ms
6 pos5-0.core1.phdl.pa.rcn.net (207.172.19.6) 9.624 ms 25.640 ms 9.927 ms
7 pos6-0.core2.lnh.md.rcn.net (207.172.19.9) 13.461 ms 12.168 ms 36.974 ms
8 ge1-0.border1.lnh.md.rcn.net (207.172.15.21) 16.409 ms 13.010 ms 22.084 ms
9 so-5-3-3.mpr1.iad1.us.above.net (64.125.12.1) 14.479 ms 27.718 ms 16.423 ms
10 so-0-0-0.mpr2.iad1.us.above.net (64.125.29.110) 30.466 ms 51.982 ms 36.179 ms
11 so-2-0-0.mpr2.dca2.us.above.net (64.125.28.129) 17.883 ms 16.719 ms 28.840 ms
12 so-5-0-0.mpr2.atl6.us.above.net (64.125.28.50) 41.555 ms 69.198 ms 41.560 ms
13 so-5-3-0.cr1.dfw2.us.above.net (64.125.29.26) 69.400 ms 46.102 ms 54.763 ms
14 so-1-0-0.mpr1.dfw2.us.above.net (64.125.28.198) 46.175 ms 60.287 ms 59.411 ms
15 ge4-13.cer01.dal01.dallas-border.com (64.124.79.202) 52.732 ms 57.164 ms 72.946 ms
16 po51.fcr01.dal01.dallas-datacenter.com (66.228.118.150) 52.742 ms 54.682 ms 52.007 ms
17 75.126.76.151-static.reverse.softlayer.com (75.126.76.151) 52.010 ms 50.626 ms 52.480 ms
$

Well since the hiccup i thnk all has been running fine now. I haven't had any hassles today.

Another drop (for me anyway) a few times in the last few minutes. The traceroute timed out at po51.fcr01.dal01.dallas-datacenter.com [66.228.118.150].

Perhaps it was routine maintenance for the datacenter, since that router has been posted/complained about on other sites as having problems. One example

This one was indeed a 12-minute outage of the network within our datacenter that connects to our load-balancer.

I always check out the various other conspiracy forums when ATS is down. Coincidentally, they always get very slow and lag a lot when ATS isn't working.

I guess no one else can handle the amount of people that ATS has, props to the amigos and staff at ATS for keeping downtime to a minimum

Well, I wouldn't have checked this thread if I hadn't mysteriously had some problems myself just now, and low and behold...

Originally posted by elevatedone
I'm sorry, I'm sorry...

I told a joke to the other new Mods and we laughed so hard we fell off the bikes that provide the power to the servers. We'll get back on in a minute.
There could be injuries.

There ya go.
I know you understand