» Published on Wed, 04 Mar 2026 13:33:00 +0000

• 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

  » Updated Thu, 12 Mar 2026 15:29:00 +0000

• Resolved

  Post-incident checks have been performed, we are closing this incident. Please reach our support team at [email protected] if you are still experiencing issues.

  » Updated Wed, 04 Mar 2026 14:43:00 +0000

• Update

  The access to the region is stable since 15 minutes. Our team is performing post-incident checks. Please reach our support team at [email protected] if you are still experiencing issues.

  » Updated Wed, 04 Mar 2026 14:13:00 +0000

• Update

  The osc-secnum-fr1 region is accessible again since 14:49 CET. Furthermore, our infrastructure provider opened an incident on his side: https://status.outscale.com/incidents/y8cfpb24xs2d.

  » Updated Wed, 04 Mar 2026 14:00:00 +0000

• Investigating

  The osc-secnum-fr1 region is unreachable since 14:26 CET. Our team is investigating

  » Updated Wed, 04 Mar 2026 13:33:00 +0000