» View Event Details | Created
Update
Mitigation actions have been taken and the situation has been stable for about 20 minutes. Our teams continue to monitor the situation closely.
Posted:
» View Event Details | Created
Resolved
The issue has been fixed. The metrics as well as the autoscaler should are back up and running.
Posted:
» View Event Details | Created
Post-Mortem
We have received additional information from our infrastructure provider regarding this incident.
The issue was caused by a network configuration change performed as part of an infrastructure upgrade. As a result of this change, several side effects were observed, including network connectivity disruptions and some virtual machines temporarily losing access to their attached storage volumes.
These combined effects significantly impacted our services and caused degraded availability for applications hosted in this region.
The configuration was corrected at 14:50 UTC, after which service began recovering and normal operations were restored. No data loss occurred as a result of this incident.
On the Scalingo side, configuration safeguards are in place to ensure that the various components of the platform are distributed across distinct infrastructure equipment. However, during this incident, even though the underlying impacted was reported as limited to two bays, it resulted in a broader impact, affecting approximately 30% of our virtual machines.
We are continuing to improve the platform's resilience by distributing its architecture across multiple infrastructure zones. Part of this work was already deployed to production for the frontend components of the platform late last year and earlier this year. Work is ongoing for the remaining components and will continue throughout the year.
Link to our infrastructure provider’s postmortem: https://status.outscale.com/incidents/y8cfpb24xs2d
Posted:
» View Event Details | Created
Resolved
All logs archive generated since the February, 26, 2026 16:00 UTC are now available. We are closing the incident. Please reach our Support team if you are still facing issue to access logs archive.
Posted:
» View Event Details | Created
Resolved
All affected databases have been restarted. The incident was caused by a hypervisor crash on our infrastructure provider’s side. We consider the incident resolved.
Posted:
» View Event Details | Created
Resolved
The maintenance is now over.
Posted:
