To be fair, this problably isn't Rackshack.net's fault. Still annoying though. Doing a traceroute reveals the following:

1 0.626 194.145.128.235 quar168.esatclear.ie
2 0.595 194.145.128.254 hades.esatclear.ie
3 0.570 193.120.57.41 -
4 0.557 193.95.140.2 ge1-0.core002.bmt.esat-x.com
5 0.591 193.95.131.1 pos2-0.core001.cwt.esat-x.com
6 0.597 193.95.129.2 ge1-0.core002.cwt.esat-x.com
7 0.595 193.120.59.17 pos3-0.tr9.dublin.esat.net
8 0.593 193.120.12.75 fe1-0-0.border0.dublin.esat.net
9 0.641 4.24.153.49 s5-0-9.nycmny1-cr2.bbnplanet.net
10 0.643 4.24.7.5 p0-0.nycmny1-nbr2.bbnplanet.net
11 0.650 4.24.10.177 p9-0.phlapa1-br1.bbnplanet.net
12 0.697 4.24.10.90 p15-0.phlapa1-br2.bbnplanet.net
13 0.706 4.24.10.185 so-0-0-0.washdc3-nbr2.bbnplanet.net
14 0.721 4.24.10.29 so-7-0-0.washdc3-nbr1.bbnplanet.net
15 0.711 4.24.4.214 p2-0.vienna1-nbr2.bbnplanet.net
16 0.711 4.24.144.94 mae-east-atm-gtei.time.net
17

As you can see, it seems to stall on mae-east-atm-gtei.time.net. Anyone else having problems accessing their RaQ at Rackshack.net today?

It's up again now.

What might have happened is someone at mae-east-atm-gtei.time.net rebooted a server or replaced a router.