[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-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-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] Degraded response time on applications

» View Event Details | Created Tue, 24 Feb 2026 12:52:00 +0000

Resolved

The situation is now resolved.

Posted: Tue, 24 Feb 2026 13:05:00 +0000

Update

The source of the issue has been found. It was traced back to a volumetric attack on the platform. We are getting back to nominal levels. We continue to monitor the situation.

Posted: Tue, 24 Feb 2026 12:59:00 +0000

Investigating

We are investigating a dregraded response time on applications hosted on the osc-fr1 region.

Posted: Tue, 24 Feb 2026 12:52:00 +0000