[osc-fr1] A database node is misbehaving

» View Event Details | Created Mon, 02 Mar 2026 05:25:00 +0000

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: Mon, 02 Mar 2026 06:19:00 +0000

Investigating

A database node is currently not responding. We are proceeding with a restart in order to restore service.

Starter plans hosted on this node are temporarily unreachable.

Customers with a Business plan are not impacted by this incident.

We will keep you informed as the situation evolves.

Posted: Mon, 02 Mar 2026 05:25:00 +0000

[osc-fr1] Recent logs archive are not available

» View Event Details | Created Mon, 02 Mar 2026 13:31:00 +0000

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: Mon, 02 Mar 2026 13:41:00 +0000

Investigating

Logs archive generated since ~26 February are not available in the osc-fr1 region. Our team is investigating the issue

Posted: Mon, 02 Mar 2026 13:31:00 +0000

[osc-secnum-fr1] Urgent Network Maintenance - March 2, 2026

» View Event Details | Created Mon, 02 Mar 2026 19:00:00 +0000

Resolved

The maintenance is now over.

Posted: Mon, 02 Mar 2026 19:10:00 +0000

Update

The maintenance is about to start. We expect some instability of the osc-secnum-fr1 network in the next few minutes.

Posted: Mon, 02 Mar 2026 19:00:00 +0000

Scheduled

Details:

An urgent network maintenance operation will take place in the osc-secnum-fr1 region on March 2, 2026, at 20:00 CET. This intervention is part of our ongoing improvements to strengthen the reliability and resilience of our architecture.

During this operation, external network connectivity to applications and publicly exposed databases may be disrupted for up to 10 minutes.

Impact:

• Access to applications and publicly exposed databases from the Internet may be unavailable for up to 10 minutes.
• The Scalingo API and Database API will be temporarily unreachable from the Internet.
• Deployments initiated during the maintenance window may fail.
• Internal connectivity (including application-to-database communication within the region) will remain unaffected.

Our team will closely monitor the operation to minimize service disruption.

If you have any questions, please contact our support team at [email protected] or through the in-app chat.

Sincerely, Scalingo

Posted: Mon, 02 Mar 2026 19:00:00 +0000

[osc-secnum-fr1] Region unreachable

» View Event Details | Created 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

Posted: 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.

Posted: 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.

Posted: 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.

Posted: Wed, 04 Mar 2026 14:00:00 +0000

Investigating

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

Posted: Wed, 04 Mar 2026 13:33:00 +0000

[osc-secnum-fr1] Autoscaling and Metrics unavailable

» View Event Details | Created Thu, 05 Mar 2026 15:19:00 +0000

Resolved

The issue has been fixed. The metrics as well as the autoscaler should are back up and running.

Posted: Thu, 05 Mar 2026 15:29:00 +0000

Investigating

The autoscaling and metrics systems are currently unavailable.

We are currently working on it.

Posted: Thu, 05 Mar 2026 15:19:00 +0000

[osc-secnum-fr1] Network performance degradation

» View Event Details | Created Mon, 09 Mar 2026 14:59:00 +0000

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: Mon, 09 Mar 2026 15:20:00 +0000

Update

We are currently taking steps to mitigate the situation.

Posted: Mon, 09 Mar 2026 15:18:00 +0000

Investigating

We have observed degraded network performance in the osc-secnum-fr1 region. Investigations are currently ongoing.

Posted: Mon, 09 Mar 2026 14:59:00 +0000

[osc-fr1] A node is misbehaving

» View Event Details | Created Fri, 13 Mar 2026 05:36:00 +0000

Resolved

All containers were migrated. Please reach our support team at [email protected] if you are still experiencing issues.

Posted: Fri, 13 Mar 2026 09:10:00 +0000

Investigating

One of our hosting node is misbehaving. Containers running on that node have been migrated to other nodes.

Posted: Fri, 13 Mar 2026 05:36:00 +0000

[osc-fr1] Issue with application operations

» View Event Details | Created Thu, 26 Mar 2026 08:51:00 +0000

Resolved

The issue has been mitigated. Our team is monitoring the situation, if you are still facing issues, please contact our support team.

Posted: Thu, 26 Mar 2026 09:21:00 +0000

Investigating

We have identified an issue with a component handling part of the operations related to applications. You may experience issues with deployments and scaling operations. Our team is working on a fix.

Posted: Thu, 26 Mar 2026 08:51:00 +0000