Resolved -
The incident is over, Provisioning is back working normally.
We are working on the RCA and publish it here asap.
May 6, 05:55 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 4, 15:33 UTC
Investigating -
On our ongoing provisioning resolution work, we had to set the Managed K8s service to "read-only",
means no Cluster or Nodepool or Autoscale actions are possible at the moment,
while the running workloads are not affected.
We will let you know asap when the K8s system is back.
May 4, 13:04 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 4, 12:00 UTC
Update -
We are continuing to work on a fix for this issue.
May 4, 11:42 UTC
Update -
Provisioning was enabled again, however we are still working on the overall resolution.
May 4, 11:26 UTC
Update -
We temporarily deactivated provisioning in order to fix the underlying issue.
May 4, 10:18 UTC
Update -
We are continuing to work on a fix for this issue.
May 4, 09:53 UTC
Update -
We are continuing to work on a fix for this issue.
May 4, 09:22 UTC
Update -
We are continuing to work on a fix for this issue.
May 4, 08:45 UTC
Identified -
Currently, there is an increased processing time for provisioning orders initiated via Data Center Designer or API.
Customers may experience timeouts or errors in some provisioning-related operations.
Occasionally, connections to the Data Center Designer may be interrupted.
May 4, 04:10 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 3, 21:22 UTC
Identified -
Currently, there is an increased processing time for provisioning orders that are initiated via Data Center Designer or API.
Occasionally, connections may be lost in the direction of the Data Center Designer.
Availability and accessibility of your virtual data center resources will remain unaffected.
We will inform you as soon as the functionality has been restored.
May 3, 18:53 UTC