Resolved
Last updated: September 25, 2026 at 02:09 PM UTC
Deployment failures on osc-fr1
Affected Components
Updates
Resolved
September 25, 2026 at 02:09 PM UTC
The deployment issue on osc-fr1 is resolved and stable for 45 minutes; the incident is now closed.
Monitoring
September 25, 2026 at 01:41 PM UTC
Situation improving since 15:15; team continues to monitor deployment issue on osc-fr1.
Identified
September 25, 2026 at 01:24 PM UTC
Deployment issue on osc-fr1 identified as caused by elevated error rates in the infrastructure provider's object storage service.
Investigating
September 25, 2026 at 01:17 PM UTC
The workaround did not produce the expected effect and the team is still working on the deployment issue.
Monitoring
September 25, 2026 at 12:51 PM UTC
A workaround is in place for deployment failures on osc-fr1, and the team continues monitoring the situation.
Investigating
September 25, 2026 at 12:19 PM UTC
Scalingo is investigating an issue causing some deployments to fail on osc-fr1.
Resolved
September 24, 2026 at 02:05 PM UTC
Deployments incident in osc-secnum-fr1 is resolved and the situation is back to normal.
Monitoring
September 24, 2026 at 01:51 PM UTC
Deployment durations are back to normal as the situation improves in the osc-secnum-fr1 region.
Investigating
September 24, 2026 at 01:32 PM UTC
Scalingo is investigating a high error rate affecting deployments in the osc-secnum-fr1 region.
Resolved
September 24, 2026 at 10:10 AM UTC
The deployment incident in osc-secnum-fr1 is resolved; the error rate dropped heavily and the incident is closed.
Monitoring
September 24, 2026 at 10:06 AM UTC
A workaround has been set up for the deployment incident in osc-secnum-fr1; users are invited to trigger another deployment.
Investigating
September 24, 2026 at 10:02 AM UTC
Scalingo is investigating a high error rate in deployments in the osc-secnum-fr1 region.
Investigating
September 24, 2026 at 09:57 AM UTC
Scalingo is investigating a high error rate in deployments in the osc-secnum-fr1 region.