» Published on Mon, 29 Jan 2024 19:15:00 +0000

• Post-Mortem

  A postmortem on this incident is available. It explains why the databases were unavailable on the osc-fr1 region. If you have any questions, don’t hesitate to contact our support team. https://doc.scalingo.com/security/postmortems/spm-2024-002

  » Updated Wed, 31 Jan 2024 13:20:00 +0000

• Update

  Our engineers are currently preparing a Postmortem.

  » Updated Tue, 30 Jan 2024 14:23:00 +0000

• Resolved

  We now consider the incident as resolved, we are still monitoring the situation to make sure the platform is stable.

  » Updated Tue, 30 Jan 2024 00:47:00 +0000

• Update

  If you are still experiencing problems accessing your databases, please contact our support team.

  » Updated Mon, 29 Jan 2024 23:50:00 +0000

• Update

  Most databases are back online. We are in the process of fixing the last databases that could cause problems.

  » Updated Mon, 29 Jan 2024 23:35:00 +0000

• Update

  We have successfully tested the solution on a small subset of databases. We are now running the procedure for all the databases affected by the incident.

  » Updated Mon, 29 Jan 2024 23:02:00 +0000

• Update

  A solution is currently being worked out by our engineers.

  » Updated Mon, 29 Jan 2024 22:34:00 +0000

• Update

  We have identified a network configuration issue, given the incident's scope, Starter and Business plans are affected.

  » Updated Mon, 29 Jan 2024 21:34:00 +0000

• Update

  The underlying issue has been identified, our team is actively working to restore normal operations.

  » Updated Mon, 29 Jan 2024 20:39:00 +0000

• Update

  The incident is still in progress, and access to your databases may still be affected.

  » Updated Mon, 29 Jan 2024 20:00:00 +0000

• Update

  Databases are restarting on the impacted node.

  » Updated Mon, 29 Jan 2024 19:25:00 +0000

• Investigating

  One of our database host is mis-behaving. Our team has been alerted and the host is being restarted.

  » Updated Mon, 29 Jan 2024 19:15:00 +0000