What happen to Bluevm California's node?

What happen to Bluevm California's node?
Is that the server is already gone?

Alert: Could not Connect to the server beryllium.bluevm.com. This is most likely due to underlying network problem. Make sure that the server is accessible from this particular node by running telnet slave-id 8889

Download and upload speedtest: wget dl.getipaddr.net/speedtest.sh -O- | bash || You can find my other useful scripts on GitHub. Run a website with lots of spammers/trolls? Use our
free Proxy Detection || You can contact me on Twitter

@breton : The OP is probably more likely to get any update here than any other medium. Maybe @BlueVM could shed some light on the full situation? - It's quite ironic that I frequently get emails from hypervm@199.19.106.130 (I assume their own monitoring IP) with issues such as :

We are aware of the issue... the raid controller appears to have failed and since it's on board we're coordinating a replacement of the motherboard with the datacenter. Unfortunately this is taking far longer than expected and we will be compensating customers effected by this outage with a free month of service. We are expecting a replacement of the board to be completed tomorrow morning or early afternoon in PST.

Customers who are "in a rush" to have a vps back online can request that we create a new VPS for them instead of waiting for the old vps to come back online.

@aubs, that would be correct. We have filtering setup, but it isn't perfect. We're working on getting the server moved to a better location with better filtering and a larger pipe (1 gbps instead of 100 mbps).