Kinetic Hosting - Notice history

Panel is now reachable again. We're monitoring it to make sure its stable

The drive has been replaced. We've restore all servers we believe to have been impacted

We're working to restore data to get the system back online ASAP

Network seems to have recovered. We'll keep monitoring to make sure it back to normal

Issue was caused by a fuse blowing blowing on the rack. The fault and the fuse have been fixed/replaced

All client servers have now been transferred off of TX-P58.

Everyone affected will get an email and ticket in the billing portal notifying them about the transfer.

Clients are now being moved onto a new node.

Just before the drive transplant was to take place, the data center provider found a fault with a RAM module. That module has now been replaced and the system is online again.

As a precaution we are still moving clients off the of the system, and will monitor it to try to catch any other issues that may exist.

Affected clients will get an email and ticket opened notifying them of their server being transferred and an IP change due to the transfer.

Anyone using a subdomain won't notice any changes in their connection address and should be able to continue connecting as usual.

We were able to get this issue pushed up in priority. The chassis replacement has taken place, but the system is still having trouble booting.

We are now working to getting the drives in an other system to transfer client servers off into another node.

We're currently waiting on the data center provider to diagnose and resolve the hardware issue.

Due to their delay we've asked for the drives to be transferred to another system to allow for us to migrate client data off.

We've been told that the earliest they will be able to complete the request and update us is December 29, 01:00 UTC.

The data center provider has been unable to identify faulty hardware causing this outage. They've said they will do a chassis swap of the hardware as another step of troubleshooting.

The data center provider has found the system to be stuck in a reboot loop.

They are attempting to diagnose possible hardware faults.

Issue solved. System is back online