Scalr Outage History

Scalr experienced a service incident where some accounts encountered longer than usual wait times for runs to execute, affecting the Scalr Worker and Scalr Platform components. The issue was identified and a fix was implemented after investigation. The incident was resolved after 2.4 hours of monitoring confirmed the fix was successful.

SSL errors prevented some customers from logging into the Scalr Platform for 55 minutes. The issue was identified as related to a release, which was subsequently rolled back to restore service.

Scalr experienced elevated run errors affecting the Scalr Platform and Scalr Worker components for 59 minutes. The service team implemented a fix and monitored the results before confirming full resolution. The incident was classified as minor severity.

Some Scalr accounts experienced delays with runs starting, affecting the Scalr Platform for 1.3 hours. The issue was identified and a fix was implemented, with the incident fully resolved after monitoring confirmed the solution was effective.

The Scalr Platform experienced an issue where workspace runs became stuck in a pending approval state, preventing users from approving them. This affected the platform's workflow approval functionality for 3.6 hours. The issue was identified and resolved with a fix implementation, followed by monitoring to ensure stability.

Some Scalr accounts experienced stuck runs that prevented normal platform operations. The issue affected the Scalr Platform for 32 minutes before being identified and resolved with a fix implementation.

The Scalr Platform and Scalr Worker experienced API performance degradation for 1 hour on April 28th, 2026. The issue was identified and a fix was implemented within 25 minutes of the incident start. The service was fully restored and monitoring confirmed the resolution.

Scalr experienced a major incident where BitBucket VCS-triggered runs were failing on the Scalr Platform. The issue lasted 8 minutes and was under investigation as of the last update. No resolution details were provided in the available incident information.