The root cause of the incident has been identified and successfully resolved.
All components are now operating normally.
We will continue to monitor the environment to ensure ongoing stability.
Thank you for your patience and understanding.
Posted Feb 19, 2026 - 15:33 CET
Identified
Unfortunately, extended monitoring has shown that the previously applied patch did not result in an improvement.
The issue is currently still under investigation. Our teams are continuing to analyze the root cause in order to identify the problem and implement appropriate corrective actions.
We will provide further updates as soon as new information becomes available.
Posted Feb 18, 2026 - 19:16 CET
Monitoring
The root cause of the incident affecting the RabbitMQ service in our Secure Public Cloud has been identified, and a patch has been successfully applied.
The service is now operating normally. We have moved the incident status to Monitoring to ensure continued stability.
Running workloads were not affected during the incident.
Our team will continue to closely monitor the environment. We will provide further updates if necessary.
Posted Feb 18, 2026 - 01:01 CET
Investigating
We are currently experiencing an incident affecting the RabbitMQ service in our Secure Public Cloud. As a result, it is currently not possible to perform changes to existing resources.
Running workloads are not affected by this incident and continue to operate normally.
Our team is already working on analysis and resolution. We will provide updates as soon as more information becomes available.
Posted Feb 17, 2026 - 20:05 CET
This incident affected: Secure Public Cloud (Compute, Volumes (Block-Storage), Object-Storage (S3), Network-Services, Dashboard, API, KMS, LBaaS).