Scalingo Outage History

Scalingo is up right now

Scalingo had 79 outages in the last 2 years totaling 34h 15m of downtime — averaging 3.2 incidents per month.

There were 79 Scalingo outages since October 2, 2025 totaling 34h 15m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://scalingostatus.com

Minor October 17, 2026

[osc-secnum-fr1] Network slowdown to access the platform

Detected by Pingoru
Oct 17, 2026, 07:51 AM UTC
Resolved
Oct 17, 2026, 09:12 AM UTC
Duration
1h 21m
Timeline · 4 updates
  1. investigating Oct 17, 2026, 07:51 AM UTC

    Our probes have identified networking slowdown to access the platform

  2. investigating Oct 17, 2026, 08:03 AM UTC

    Root cause of the incident has been identified, our team is working on a mitigation solution

  3. investigating Oct 17, 2026, 08:04 AM UTC

    Mitigation has been setup, network performance are trending to nominative state

  4. resolved Oct 17, 2026, 09:12 AM UTC

    Situation has been stable for 1h, closing the incident

Read the full incident report →

Minor October 5, 2026

[osc-secnum-fr1] Degraded network access to the region and deployment performance

Detected by Pingoru
Oct 05, 2026, 12:57 PM UTC
Resolved
Oct 05, 2026, 03:09 PM UTC
Duration
2h 12m
Timeline · 2 updates
  1. investigating Oct 05, 2026, 12:57 PM UTC

    Network access to osc-secnum-fr1 is degraded with higher than normal packet loss rate. It also impacts the stability of the deployment process. Our operators are currently investigating.

  2. resolved Oct 05, 2026, 03:09 PM UTC

    The network access is now back to nominal situation since 16:40. We're closing the incident? If you are still facing issues, please contact our customer support

Read the full incident report →

Minor October 3, 2026

[osc-secnum-fr1] Issues with some deployments and db tunnel

Detected by Pingoru
Oct 03, 2026, 08:50 PM UTC
Resolved
Oct 03, 2026, 09:53 PM UTC
Duration
1h 3m
Timeline · 2 updates
  1. investigating Oct 03, 2026, 08:50 PM UTC

    Deployments using "git push" and DB tunnels via SSH are facing issues, our team is investigating

  2. resolved Oct 03, 2026, 09:53 PM UTC

    The issue has been fixed, the situation is now stable, we are closing this incident. If you are still facing issues, please contact our support

Read the full incident report →

Minor September 30, 2026

[osc-secnum-fr1] Deployment slowness

Detected by Pingoru
Sep 30, 2026, 09:41 AM UTC
Resolved
Sep 30, 2026, 04:02 PM UTC
Duration
6h 21m
Timeline · 6 updates
  1. investigating Sep 30, 2026, 09:41 AM UTC

    We observed increased time of deployments on osc-secnum-fr1 region. We're analyzing the situation.

  2. investigating Sep 30, 2026, 10:20 AM UTC

    We're seeing an improvement on performances. Our operators are still monitoring the situation.

  3. investigating Sep 30, 2026, 12:27 PM UTC

    Our monitoring show degraded performances impacting deployments' duration. We continue to monitor the situation.

  4. investigating Sep 30, 2026, 03:28 PM UTC

    We just setup a workaround and are still actively monitoring the situation.

  5. investigating Sep 30, 2026, 03:43 PM UTC

    Applied workaround improved speed of new deployments. We continue to monitor until back to normal situation.

  6. resolved Sep 30, 2026, 04:02 PM UTC

    Closing the incident as deployment speed is back to a nominal state since the application of the workaround. If you're stilll facing issues, do not hesitate to contact our support.

Read the full incident report →

Minor September 28, 2026

[osc-secnum-fr1] Increased Internet latency and error rates affecting deployment performance

Detected by Pingoru
Sep 28, 2026, 01:41 PM UTC
Resolved
Sep 28, 2026, 03:09 PM UTC
Duration
1h 28m
Timeline · 1 update
  1. resolved Sep 28, 2026, 03:09 PM UTC

    Network performance in the `osc-secnum-fr1` region has returned to nominal levels. Deployment performance has also returned to normal. If you are still experiencing issues, please contact our Support Team.

Read the full incident report →

Minor September 25, 2026

[osc-fr1] Issue with deployment

Detected by Pingoru
Sep 25, 2026, 12:18 PM UTC
Resolved
Sep 25, 2026, 02:08 PM UTC
Duration
1h 50m
Timeline · 1 update
  1. resolved Sep 25, 2026, 02:08 PM UTC

    The situation is stable since 45 minutes. We are closing this incident. Please reach our Support Team if you are still facing issues.

Read the full incident report →

Minor September 19, 2026

[osc-fr1] A database hosting node is misbehaving

Detected by Pingoru
Sep 19, 2026, 10:07 AM UTC
Resolved
Sep 19, 2026, 10:52 AM UTC
Duration
45m
Timeline · 1 update
  1. resolved Sep 19, 2026, 10:52 AM UTC

    All database instances present on the host have been restarted. The incident is now considered closed. If you are still facing issues, please contact our customer support.

Read the full incident report →

Minor September 11, 2026

[osc-fr1] Metrics and autoscaler are not working

Detected by Pingoru
Sep 11, 2026, 10:05 AM UTC
Resolved
Sep 11, 2026, 10:30 AM UTC
Duration
25m
Timeline · 1 update
  1. resolved Sep 11, 2026, 10:30 AM UTC

    The application, database metrics and auto-scaling feature are now back to a normal state. Metrics may be missing for the incident period. If you are still facing other issues, please contact our Support Team.

Read the full incident report →

Minor August 12, 2026

[osc-fr1] Issue with database provisioning and plan change

Detected by Pingoru
Aug 12, 2026, 03:29 PM UTC
Resolved
Aug 12, 2026, 03:45 PM UTC
Duration
16m
Timeline · 1 update
  1. resolved Aug 12, 2026, 03:45 PM UTC

    The issue started at 16:35 CEST and was fixed at 17:05 CEST. The database that are still provisioning should succeed in the coming minutes. If you are still facing issues, please contact our Support Team.

Read the full incident report →

Minor July 27, 2026

[osc-fr1] Issue with application operations

Detected by Pingoru
Jul 27, 2026, 07:08 PM UTC
Resolved
Jul 27, 2026, 07:18 PM UTC
Duration
10m
Timeline · 1 update
  1. resolved Jul 27, 2026, 07:18 PM UTC

    The issue started at 20:57 CEST and was resolved at 21:12 CEST. During that time, deployments were failing and application related operations may have failed. If you are still facing issues, please contact our support team.

Read the full incident report →

Minor July 23, 2026

[osc-fr1] Urgent Maintenance on Databases

Detected by Pingoru
Jul 23, 2026, 04:00 PM UTC
Resolved
Jul 23, 2026, 06:41 PM UTC
Duration
2h 41m
Timeline · 1 update
  1. resolved Jul 23, 2026, 06:41 PM UTC

    All affected databases have been restarted. The operation is now over. If you are still facing issue, please contact our Support Team.

Read the full incident report →

Minor July 22, 2026

[osc-secnum-fr1] Deployment slowdown

Detected by Pingoru
Jul 22, 2026, 02:11 PM UTC
Resolved
Jul 22, 2026, 03:26 PM UTC
Duration
1h 15m
Timeline · 1 update
  1. resolved Jul 22, 2026, 03:26 PM UTC

    Incident is considered resolved on our side, please reach support if you experience any additional problem

Read the full incident report →

Minor July 9, 2026

[osc-fr1] Some app and database hosts are misbehaving

Detected by Pingoru
Jul 09, 2026, 01:08 PM UTC
Resolved
Jul 09, 2026, 03:01 PM UTC
Duration
1h 53m
Timeline · 1 update
  1. 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.

Read the full incident report →

Minor July 8, 2026

[osc-fr1] Database operation issues

Detected by Pingoru
Jul 08, 2026, 08:05 AM UTC
Resolved
Jul 08, 2026, 08:53 AM UTC
Duration
48m
Timeline · 1 update
  1. 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.

Read the full incident report →

Minor July 6, 2026

[osc-fr1] Google Storage API access issue

Detected by Pingoru
Jul 06, 2026, 08:24 AM UTC
Resolved
Jul 06, 2026, 09:17 AM UTC
Duration
53m
Timeline · 1 update
  1. 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.

Read the full incident report →