No incidents reported
Due to a operation error, our status system send many mails with a "status change" to subscribed customers. There were no problem at all and we are very sorry about this.
Currently we are investigating some problems with creating or scaling our Kubernetes Services. All other Services are not affected.
We're currently investigating an outage of one our compute nodes. Further updates will be posted.
Around 22:04 (GMT+2) one of out CPU nodes restarted.
The auto-recovery of all workloads were triggered and all systems are back operational.
Investiagtion of what caused the restart is ongoing.
We are investigating partial outage of our API.
We are investigating a higher latency than expected on our distributed storage in FRA2 at the moment.