Kinetic Hosting - Notice history

Network accessibility has been recovered. Due to the work performed, an IP change had to occur for the servers on the affected node.

Impacted clients should/will be notified about the IP change.

All servers have now been moved to other nodes while we look into the drive temperature issue. Affected clients should/well get an email informing them of the possible IP change due to the transfers

We implemented a fix and are currently monitoring the result.

The data center provider is still working to fully restore network stability. They've taken some actions to improve the situation, and are still working with their backbone network provider to fully resolve the issues.

All affected client services have been moved to another node. Clients should have or will receive an email informing them about the move and possible IP changes due to it.

We'll be continuing to work with the data center provider to get diagnostic work performed to identify the origin of the fault on the node and get it resolved.

We are still waiting on a response from the data center provider. In the mean time we've been able to get the node back online and will attempt to move as many client services to another node as we are able.

We've contacted the data center provider requesting an investigation into a possible hardware fault causing system instability.

They are checking the server and we are waiting for their response.

Due to reoccurring issues with the node, we're reinstating this status report and will contact the data center provider.

The node is now responding again, we'll monitor for the time being.

This incident has been resolved. Impacted nodes are accessible again.

A public network outage affected the node making it inaccessible for a period of time, it appears the network accessibility has recovered now and the node is back online and responding to requests again.

All client services have been moved off of the node.

You may now continue to use your services as normal.

The system was undergoing memory training which kept it offline longer than normal. It's now booted and responding to pings again.

Attempts to reboot the system and boot into rescue have failed. We're currently in contact with the data center provider to investigate further.

There was a fault with both primary and redundant public network switches the affected node is connected to.

Both network switches have fixed and the affected node is not accessible again.

The system is currently not responding to ping request and attempts to access it via rescue haven't been successful.

The data center provider has been contacted in an attempt to look further into the apparent network unavailability occurring.

Affected servers have now been moved to other nodes. Clients should have gotten a ticket/email notifying them of the move and possible IP changes due to it.

It appears there are still ongoing issues with this systems drive. We are working to get affect client servers moved to another node.