Scalingo Outage History
Scalingo is up right nowPingoru has recorded 107 incidents for Scalingo: 101 in the last 12 months and 32 in the last 90 days.
Incidents, newest first
Minor July 9, 2026 [osc-fr1] Some app and database hosts are misbehaving 1h 53m
Started Jul 09, 2026, 01:08 PM UTC· resolved Jul 09, 2026, 03:01 PM UTC
- resolved Jul 09, 2026, 03:01 PM UTC
The situation has now been stable for a while. The incident is considered as closed on our side. If your are still encountering issues, please contact our customer support.
Minor July 8, 2026 [osc-fr1] Database operation issues 48m
Started Jul 08, 2026, 08:05 AM UTC· resolved Jul 08, 2026, 08:53 AM UTC
- resolved Jul 08, 2026, 08:53 AM UTC
The pening operations have been processed.The incident is now considered closed on our side. If you're still facing issues, please contact our customer support.
Minor July 6, 2026 [osc-fr1] Google Storage API access issue 53m
Started Jul 06, 2026, 08:24 AM UTC· resolved Jul 06, 2026, 09:17 AM UTC
- resolved Jul 06, 2026, 09:17 AM UTC
A work-around has been setup. Access to the Google Storage API is now possible again from the `osc-fr1` region. If you are still facing issues, please contact our support team.
Minor July 2, 2026 [osc-fr1] Database node misbehaving 18m
Started Jul 02, 2026, 04:50 PM UTC· resolved Jul 02, 2026, 05:08 PM UTC
- resolved Jul 02, 2026, 05:08 PM UTC
All the databases have been restarted. We are closing this incident. If you are still facing issues, please contact our support.
Minor June 29, 2026 [osc-secnum-fr1] Deployment issues 2h 20m
Started Jun 29, 2026, 01:54 PM UTC· resolved Jun 29, 2026, 04:14 PM UTC
- resolved Jun 29, 2026, 04:14 PM UTC
The situation is back to the nominal state. Deployments are no longer delayed, and execution times have returned to their standard levels. The disruption was caused by increased latency affecting the object storage service provided by our infrastructure provider.
Minor June 25, 2026 [osc-fr1] Deployment issues 1h 36m
Started Jun 25, 2026, 10:26 AM UTC· resolved Jun 25, 2026, 12:02 PM UTC
- resolved Jun 25, 2026, 12:02 PM UTC
The situation is back to the nominal state. Deployments are no longer delayed, and execution times have returned to their standard levels. The disruption was caused by increased latency affecting the object storage service provided by our infrastructure provider.
Minor June 24, 2026 [osc-fr1] Database access can be disrupted 1h 44m
Started Jun 24, 2026, 08:13 PM UTC· resolved Jun 24, 2026, 09:57 PM UTC
- resolved Jun 24, 2026, 09:57 PM UTC
A workaround has been set up and the region is back to nominal performances. The incident is considered as closed on our side.
Minor June 24, 2026 [osc-secnum-fr1] Network disruption to access region applications 61d 17h
Started Jun 24, 2026, 07:42 PM UTC· resolved Aug 25, 2026, 12:44 PM UTC
- postmortem Aug 25, 2026, 12:44 PM UTC
During the evening of June 24, starting at approximately 21:30, Scalingo experienced significant disruptions affecting both the osc-secnum-fr1 and osc-fr1 regions. The incident occurred during an extreme heatwave affecting the area where one of our infrastructure provider's datacenters is located. Under these conditions, cooling systems at the datacenter began to fail, resulting in severe overheating and impacting some of the provider's infrastructure. Although Scalingo's infrastructure is not directly hosted in the affected datacenter, the incident had cascading effects on some services we rely on: * **osc-secnum-fr1:** A critical network component operated by our infrastructure provider was hosted in the affected datacenter, resulting in network unavailability towards the region. Connectivity was restored at approximately 23:10, after which applications and databases in the region became reachable again. We observed no additional impact resulting from the incident after connectivity was restored. * **osc-fr1:** Although object storage data is replicated across multiple sites, we identified that our provider's API used to access the service was hosted exclusively in the affected zone. This resulted in minor disruptions to operations relying on object storage, including some deployment operations.
Minor June 17, 2026 [osc-fr1] Database node mis-behaving 39m
Started Jun 17, 2026, 04:08 PM UTC· resolved Jun 17, 2026, 04:47 PM UTC
- resolved Jun 17, 2026, 04:47 PM UTC
All affected databases have been restarted. If you are still facing issue, please contact our support team.
Minor June 17, 2026 [osc-fr1] Deployment slowdown 1h 30m
Started Jun 17, 2026, 11:45 AM UTC· resolved Jun 17, 2026, 01:15 PM UTC
- resolved Jun 17, 2026, 01:15 PM UTC
The performances are back to the nominal state. We are closing this incident.
Minor June 10, 2026 [osc-fr1] Addon provisionning and plan changes disrupted 18m
Started Jun 10, 2026, 02:27 PM UTC· resolved Jun 10, 2026, 02:45 PM UTC
- resolved Jun 10, 2026, 02:45 PM UTC
A fix has been applied and new database operations should succeed. if you're still facing any issue, please contact our customer support
Minor May 28, 2026 [osc-fr1] database related operations are taking more than than usual to be processed 11m
Started May 28, 2026, 08:22 AM UTC· resolved May 28, 2026, 08:33 AM UTC
- resolved May 28, 2026, 08:33 AM UTC
All the pending operations have been processed. If you are still facing issues, please contact our customer support.
Minor May 25, 2026 [osc-fr1] DBDR and Private Networks features are misbehaving 8m
Started May 25, 2026, 12:52 PM UTC· resolved May 25, 2026, 01:00 PM UTC
- resolved May 25, 2026, 01:00 PM UTC
The feature service level is back to the nomnal situation after our operators intervention. The incident is considered as closed on our side. If you are still experiencing issues, please contact our customer support.
Minor May 18, 2026 [osc-fr1] Autoscaling and Metrics unavailable 1h 45m
Started May 18, 2026, 08:26 AM UTC· resolved May 18, 2026, 10:11 AM UTC
- resolved May 18, 2026, 10:11 AM UTC
Situation has been stable over the last hour. Closing the incident
Minor April 30, 2026 [osc-fr1 & osc-secnum-fr1] High latency issue accessing applications 10d 21h
Started Apr 30, 2026, 02:22 PM UTC· resolved May 11, 2026, 12:06 PM UTC
- postmortem May 11, 2026, 12:06 PM UTC
The post-mortem is now live available at: https://doc.scalingo.com/security/postmortems/spm-2026-001
Minor April 30, 2026 [osc-fr1 & osc-secnum-fr1] Urgent maintenance affecting application-related operations 8h 21m
Started Apr 30, 2026, 09:40 AM UTC· resolved Apr 30, 2026, 06:01 PM UTC
- resolved Apr 30, 2026, 06:01 PM UTC
The maintenance operation has been completed on both the `osc-fr1` and the `osc-secnum-fr1` regions.
Minor April 14, 2026 [osc-secnum-fr1] Some API operations are failing 7m
Started Apr 14, 2026, 08:43 AM UTC· resolved Apr 14, 2026, 08:50 AM UTC
- resolved Apr 14, 2026, 08:50 AM UTC
The root cause has been found. The API is back to its nominal state.
Minor April 8, 2026 [osc-secnum-fr1] Scheduled maintenance affecting the TCP Gateway and publicly exposed databases - April 8, 2026 7m
Started Apr 08, 2026, 06:00 PM UTC· resolved Apr 08, 2026, 06:07 PM UTC
- resolved Apr 08, 2026, 06:07 PM UTC
The maintenance is now done. TCP Addons and publicly exposed database might have experienced up to 5mn of downtime. If you still have issue please contact us on the support.
Minor April 7, 2026 [osc-fr1] Scheduled maintenance affecting the TCP Gateway and publicly exposed databases - April 7, 2026 –
Started Apr 07, 2026, 06:00 PM UTC· resolved Apr 07, 2026, 06:00 PM UTC
- resolved Apr 07, 2026, 06:00 PM UTC
The maintenance is now done. TCP Addons and publicly exposed database might have experienced up to 5mn of downtime. If you still have issue please contact us on the support.
Minor April 7, 2026 [scalingo.com] Scheduled maintenance affecting the public website - April 7, 2026 2h 18m
Started Apr 07, 2026, 02:00 PM UTC· resolved Apr 07, 2026, 04:18 PM UTC
- resolved Apr 07, 2026, 04:18 PM UTC
scalingo.com is now accessible again. The maintenance is over.
Minor March 13, 2026 [osc-fr1] A node is misbehaving 3h 34m
Started Mar 13, 2026, 05:36 AM UTC· resolved Mar 13, 2026, 09:10 AM UTC
- resolved Mar 13, 2026, 09:10 AM UTC
All containers were migrated. Please reach our support team at [email protected] if you are still experiencing issues.
Minor March 9, 2026 [osc-secnum-fr1] Network performance degradation 229d 9h
Started Mar 09, 2026, 02:59 PM UTC· resolved Oct 25, 2026, 12:45 AM UTC
- investigating Mar 09, 2026, 02:59 PM UTC
We have observed degraded network performance in the osc-secnum-fr1 region. Investigations are currently ongoing.
- investigating Mar 09, 2026, 03:18 PM UTC
We are currently taking steps to mitigate the situation.
- investigating Mar 09, 2026, 03:20 PM UTC
Mitigation actions have been taken and the situation has been stable for about 20 minutes. Our teams continue to monitor the situation closely.
Minor March 5, 2026 [osc-secnum-fr1] Autoscaling and Metrics unavailable 10m
Started Mar 05, 2026, 03:19 PM UTC· resolved Mar 05, 2026, 03:29 PM UTC
- resolved Mar 05, 2026, 03:29 PM UTC
The issue has been fixed. The metrics as well as the autoscaler should are back up and running.
Minor March 4, 2026 [osc-secnum-fr1] Region unreachable 8d 1h
Started Mar 04, 2026, 01:33 PM UTC· resolved Mar 12, 2026, 03:29 PM UTC
- postmortem Mar 12, 2026, 03:29 PM UTC
We have received additional information from our infrastructure provider regarding this incident. The issue was caused by a network configuration change performed as part of an infrastructure upgrade. As a result of this change, several side effects were observed, including network connectivity disruptions and some virtual machines temporarily losing access to their attached storage volumes. These combined effects significantly impacted our services and caused degraded availability for applications hosted in this region. The configuration was corrected at 14:50 UTC, after which service began recovering and normal operations were restored. No data loss occurred as a result of this incident. On the Scalingo side, configuration safeguards are in place to ensure that the various components of the platform are distributed across distinct infrastructure equipment. However, during this incident, even though the underlying impacted was reported as limited to two bays, it resulted in a broader impact, affecting approximately 30% of our virtual machines. We are continuing to improve the platform's resilience by distributing its architecture across multiple infrastructure zones. Part of this work was already deployed to production for the frontend components of the platform late last year and earlier this year. Work is ongoing for the remaining components and will continue throughout the year. Link to our infrastructure provider’s postmortem: https://status.outscale.com/incidents/y8cfpb24xs2d
Minor March 2, 2026 [osc-secnum-fr1] Urgent Network Maintenance - March 2, 2026 10m
Started Mar 02, 2026, 07:00 PM UTC· resolved Mar 02, 2026, 07:10 PM UTC
- resolved Mar 02, 2026, 07:10 PM UTC
The maintenance is now over.