Kinetic Hosting - Notice history

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

This incident has been resolved.

Panel is now restored. We're motoring to make sure its fully stable

This incident has been resolved.

We received an update from the data center provider about the cause. There was a brief network routing issue that affected some parts of their London location, which was corrected shortly after it's discovery.

The data center provider was able to restore network accessibility and the node appears to be responding to pings and sending monitoring data again.

We'll continue to monitor for the time being.

The node appears to be booted into the OS and running, but a networking loss has occurred. The data center provider has been contacted.

We've seen a recovery in network stability and have since been notified that the upstream data center issues are resolved.

We also observed some of the affects impact our Brazil location, and have been notified that the incident may have impacted systems in DC, Texas, and Florida as well. All of which appear to have been resolved now.

We'll continue to monitor for the time being.

Affected client servers have now been moved to another system. Impacted clients should have/will receive an email notifying them of possible IP changes due to being migrated.

We are still working to move affected client servers to another system.

While attempting to do so earlier, we encountered many issues attempting to keep the system stable enough to perform recovery work, while going back and forth with the data center provider about the true cause of the outage.

We were eventually able to get a chassis swap performed by a data center technician on the downed system to get it back online, allowing us to properly implement our normal recovery procedures and move affected clients off the system as a precaution.

Attempts to get support from the data center provider have been, unfruitful to say the least. But we've since been able to access the system again, and are currently working to get affected client data moved to another system.

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.

It appears the data center provider is finished with the maintenance affecting the listed systems. We'll continue to monitor for the time being.

EUE-ENG-P62-A6-CG is now back online.

The cause of the outage was due to a data center technician servicing an adjacent system to EUE-ENG-P62-A6-CG and accidentally disconnected the incorrect cabling.

Everything is now back as it should be and accessible again.

The data center provider has finished their swap over of the network switches. We're currently monitoring to observe if the instability persists or not.

The data center provider has installed a new network switch and is now working to swap the affected systems such as over to it.

The data center provider has looked into the issue. It's been identified as a failure of a service on the network switch USC-TX-P22-A6-CG is routed through.

They are working to either replace the switch, or move connections of the affected systems on the rack to another available network switch.