We are marking this incident as resolved. A RCA will be published here once it is compiled.
Posted May 11, 2026 - 08:30 UTC
Monitoring
The rollback was completed successfully. The team is currently checking the affected resources for potential residual inconsistencies. We are setting this incident into monitoring status.
Posted May 08, 2026 - 20:42 UTC
Update
We are currently rolling out the correction. We expect this to take several minutes and will update this page once the rollout is completed.
Posted May 08, 2026 - 18:42 UTC
Update
The team is now preparing to safely rollback identified changes on affected resources.
Posted May 08, 2026 - 17:13 UTC
Update
The team continues to audit affected resources to verify that all remaining inadvertent configuration changes are reverted.
Posted May 08, 2026 - 16:29 UTC
Identified
Our Kubernetes engineering team has identified the root cause of the issue. The incident stemmed from a defect in a configuration filtering mechanism. We are currently implementing mitigation steps and will provide further updates on our progress here.
Posted May 08, 2026 - 15:52 UTC
Investigating
Some customers may experience connection problems to the control plane and degraded functionality of kubernetes. Our engineers are working on a fix.
Posted May 08, 2026 - 15:15 UTC
This incident affected: Location DE/TXL (Managed Kubernetes), Location DE/FRA (Managed Kubernetes), and Location DE/FRA/2 (Managed Kubernetes).
