We would like to inform you that the incident on our Public Cloud offering in SBG5, have been resolved.
Start time : 01/04/2025 20:23 UTC End Time : 01/04/2025 21:35 UTC Root cause : Gateway overloading. Our technical teams resolved the issue. All impacted services are now operational.
We thank you for your understanding and patience throughout this incident.
Posted Apr 01, 2025 - 21:44 UTC
Update
We have new information regarding the incident that affected your service(s).
Please find below an update on the situation: Update : Most of instances are operational again. 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 01, 2025 - 21:03 UTC
Identified
We have determined the origin of the incident affecting our Compute - Instance offer on the specific SBG5 region.
Here is detail for this incident : Start time : 01/04/2025 20:23 UTC Impacted Service(s) : Some instances located in SBG5 are temporarily unavailable. Customers Impact : Customers are temporarily unable to access and use their instances in SBG5 region. 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 01, 2025 - 20:54 UTC
Investigating
We would like to inform you that we have an incident on our Public Cloud offer in the SBG5 regions.
Here is detail for this incident : Start time : 01/04/2025 20:23 UTC Impacted Service(s) : Some instances located in SBG5 are temporarily unavailable. Customers Impact : Customers are temporarily unable to access and use their instances in SBG5 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 01, 2025 - 20:38 UTC
This incident affected: Compute - Instance || SBG (SBG5).