We would like to inform you that the incident on Public Cloud offer on the DE1 region has now been resolved.
Here is detail for this incident : Start time : 07/04/2025 08:59 UTC End time : 08/04/2025 02:49 UTC
We thank you for your understanding and patience throughout this incident.
Posted Apr 08, 2025 - 06:45 UTC
Update
We have new information regarding the incident that affected your service(s).
Please find below an update on the situation: Update : We are also experiencing an incident affecting our Managed Kubernetes Service. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
Posted Apr 07, 2025 - 10:05 UTC
Identified
We have determined the origin of the incident affecting our Public Cloud offer on the DE1 region. Here are some supplementary details : Start time : 07/04/2025 08:59 UTC Impacted Service(s) : Some instances located in DE1 are temporarily unavailable. Root Cause : This incident is caused by a infrastructure issue. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
Posted Apr 07, 2025 - 09:52 UTC
Investigating
We are currently experiencing an incident affecting our Public Cloud offering, which is causing temporary availability issues in the DE1 regions. Here is detail for this incident : Start time : 07/04/2025 08:59 UTC Impacted Service(s) : Some instances located in DE1 are temporarily unavailable. Customers Impact : Customers are temporarily unable to access and use their instances in DE1 region. Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it.
We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
Posted Apr 07, 2025 - 09:12 UTC
This incident affected: Compute - Instance || LIM (DE1) and Containers & Orchestration || Managed Kubernetes Service (DE1).