Wednesday, October 15, 2014
One of our Los Angeles nodes is with ColoCrossing and they are having network issues. They are currently working on it. Update: 20:25: The network is back online. The cause of the issue was: "The cause for the incident was due to a bug in the firmware our switches utilize. It had a bit of an impact on us because we just recently completed a significant network wide upgrade of all cabinet...
Monday, October 13, 2014
A large DDoS attack halted the NIC on node3ssd before we had any chance to take action. This is resolved and VMs are in the process of booting up.
Saturday, October 11, 2014
There is a huge DDoS attack happening on our Dallas Storage VPS network.
Wednesday, October 8, 2014
Node3ssd had to be rebooted for emergency unplanned maintanence. The server is back online and VMs should be coming up shortly.
Saturday, October 4, 2014
lapure1 went offline again. We are looking into it. Update: The node is back online. However, we are going to migrate off this server this week. Please open a ticket if you are having troubles.
Thursday, October 2, 2014
We are rebooting this server to make it recognize a disk replacement. It should come back in 10 minutes. Update 17:31: The raid volume isn't getting recognized. We are working on it. Update 17:43: The raid volume got recognized. However, the OS is not booting. We are working on it. This is a bigger issue now. Here are the details: Description of the issue: A drive...
Thursday, September 25, 2014
Due to CPU lock up, we are rebooting this node.
Tuesday, September 23, 2014
@8:45 AM BST: DALPURE3 became unresponsible moments ago. We have begun investigation. @8:49 AM BST: The network is back up. We are investigating the cause.
Monday, September 22, 2014
We have experienced a lock up on this node and had to proceed with a power cycle. Update: 11:30 AM: The node is back up and VPS's are booting. Update 11:50 AM: All VPS's look online. Please contact us if you have any issue.
Sunday, September 21, 2014
We are again seeing huge packet loss in this network. We are in contact with the DC. Update: 01:39 AM: The issue looks resolved.