Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Scalr Outage History

Every past Scalr outage tracked by IsDown, with detection times, duration, and resolution details.

There were 59 Scalr outages since March 2022. The 14 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Minor April 29, 2026

April 2026: Workspace runs stuck in pending approval

Detected Apr 29, 2026 11:22 AM EDT · Resolved Apr 29, 2026 2:57 PM EDT · Duration about 4 hours

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.

Minor April 28, 2026

April 2026: Some accounts experiencing stuck runs

Detected Apr 28, 2026 11:13 AM EDT · Resolved Apr 28, 2026 11:45 AM EDT · Duration 32 minutes

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.

Major April 28, 2026

April 2026: API Performance Degradation

Detected Apr 28, 2026 4:53 AM EDT · Resolved Apr 28, 2026 5:55 AM EDT · Duration about 1 hour

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.

Minor April 14, 2026

April 2026: BitBucket VCS-triggered runs failing

Detected Apr 14, 2026 4:59 AM EDT · Resolved Apr 14, 2026 7:23 AM EDT · Duration about 2 hours

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.