For as of yet unknown reasons, at approximately 3:02 AM MST one of the hardware nodes servicing our cluster started behaving erratically and negativity impacting the performance of customer containers on that hardware node. Systems administrators were immediately notified and the decision to reboot the affected hardware node was made at 4:43 AM. The hardware node full completed a reboot at 5:13 AM MST, at which point customer containers recovered. In total, 44 customers were affected.

Of course, we are very concerned about this unexpected outage. We plan to begin working with customers with containers on the affected hardware node immediately to begin to move them to other nodes. We are deeply sorry for this outage.