We have removed the affected node from the cluster and normal service has resumed.
Identified · UTC
We are continuing to work on a fix for this incident It appears a faulty storage node has caused some core services to reboot we are working on the issue