Incident History for Scalingo

The elevated error rate affecting application operations on osc-secnum-fr1 is resolved after maintenance completed.

Application operations such as scale, restart, one-off, and deployments are unstable on osc-secnum-fr1 due to an infrastructure provider's emergency maintenance.

The incident is resolved; all database instances on the affected server have been restarted and the incident is closed.

Operators are investigating a misbehaving database hosting node in osc-fr1 and will restart it, affecting starter plan databases.

The osc-fr1 metrics and autoscaler issue is now resolved and fixed.

Metrics and autoscaling in osc-fr1 are back to normal, and operators continue monitoring the situation.

Metrics and autoscaler are unavailable in osc-fr1 due to an incident; operators are working to restore service.

Scalingo's provider will perform urgent security updates from October 22 to 26, 2026, potentially causing performance impacts and brief unavailability.

The osc-fr1 network access degradation is resolved and the incident is closed.

Network access to the osc-fr1 region was degraded for a few minutes; performance has returned to normal and investigation continues.

Maintenance is complete; application and database metrics are available and the Autoscaler feature is active again.

Maintenance on metrics infrastructure in osc-fr1 is in progress, temporarily disabling application metrics and autoscaling for about two hours.

The network slowdown affecting access to the osc-secnum-fr1 platform is resolved after an hour of stability.

Mitigation is in place and network performance is trending back to normal for osc-secnum-fr1 platform access.

Root cause of the network slowdown affecting osc-secnum-fr1 platform access has been identified; mitigation is underway.

Scalingo is investigating networking slowdown affecting access to the osc-secnum-fr1 platform.

Network access to the osc-secnum-fr1 region is back to nominal since 16:40 and the incident is closed.

Scheduled maintenance on metrics infrastructure will make application metrics and autoscaling temporarily unavailable; applications continue running normally.

Network access to osc-secnum-fr1 is degraded with high packet loss, impacting deployment stability; operators are investigating.

The incident is resolved; the situation has been stable for over an hour and is considered over.

The situation is almost back to nominal and operators are still monitoring it.

Packet loss in osc-secnum-fr1 has returned to nominal and most deployments succeed, but operators are still working on the situation.

Team is still working on degraded network access and deployment performance in osc-secnum-fr1.

Network performance in osc-secnum-fr1 has returned to nominal levels and deployment performance is back to normal.

Metrics and autoscaling on osc-secnum-fr1 are resolved and back to normal; contact support if issues persist.

Metrics and autoscaling are unavailable on osc-secnum-fr1 due to an incident; operators are working to restore service.

Increased packet loss and latency to the Internet from osc-secnum-fr1 identified; provider engaged to resolve the issue.

The deployment issue on osc-fr1 is resolved and stable for 45 minutes; the incident is now closed.

Situation improving since 15:15; team continues to monitor deployment issue on osc-fr1.

Deployment issue on osc-fr1 identified as caused by elevated error rates in the infrastructure provider's object storage service.

The workaround did not produce the expected effect and the team is still working on the deployment issue.

All database instances on the affected host have been restarted and the incident is now closed.

The misbehaving node has been restarted and operators are applying post-restart procedures before restarting hosted database instances.

A database hosting node in osc-fr1 is misbehaving; operators are investigating and will restart the impacted node.

Metrics and autoscaler in osc-fr1 are resolved and back to normal; metrics may be missing for the incident period.

Metrics and autoscaler in osc-fr1 are recovering, and operators are monitoring the situation.

Application and database metrics are unavailable in osc-fr1, breaking autoscaling; operators are working to restore service.

The incident affecting access to public GitHub git repositories is resolved; no more downloading errors have been identified.

The database node issue in osc-secnum-fr1 is resolved and the situation is back to nominal state.

We are restarting the misbehaving database host; starter plan databases are down, business and enterprise plans unaffected.

One database host in osc-secnum-fr1 is misbehaving and under investigation.

GitHub acknowledged and explained the errors encountered during the incident; all details are available.

Incident resolved. GitHub limited unauthenticated requests; we updated our system to avoid impact. Some stacks may still need workaround.

Workaround deployed for GitHub access errors; monitoring situation.

Update: issue related to GitHub upgrade impacting some git versions; workaround being implemented.