» Published on Wed, 24 Jun 2026 20:13:00 +0000

• Resolved

  A workaround has been set up and the region is back to nominal performances.

  The incident is considered as closed on our side.

  » Updated Wed, 24 Jun 2026 21:57:00 +0000

• Update

  Our operators are still monitoring the situation. We observed an improvement on the network access to the region.

  The deployments and container operations are still in a degraded mode but should be working as expected soon after the deployment of a workaround on our infrastructure provider side.

  » Updated Wed, 24 Jun 2026 21:52:00 +0000

• Update

  The situation is improving. Databases are accessible again and most containers operations are working again. Our team is monitoring the situation.

  » Updated Wed, 24 Jun 2026 21:20:00 +0000

• Update

  App containers operations (restart, scaling, deployments, etc) are currently unavailable due to an unavailability on the storage backend. Our operators are currently investigating and monitoring the situation.

  » Updated Wed, 24 Jun 2026 20:39:00 +0000

• Investigating

  Access to Scalingo hosted databases from inside and outside the Scalingo network can be disrupted. Connections may fail with a No route to host error. Our team is investigating.

  » Updated Wed, 24 Jun 2026 20:13:00 +0000