New Multi-region uptime checks and custom-domain status pages

Scalr Outage History

Daily provider-status observations and published incident history for Scalr.

Operational

Scalr is operational. Verified . Official provider source.

Looking for an update now? Check the current status, or follow Scalr for future changes.

73.7% of 57 verified observed days had no reported provider issue

90-Day Trend

Jul 24Oct 21

Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.

Monthly Status Summary

Month Issue-free days Days Tracked Days with issues
September 2026 83.3% 30 5

This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.

Recorded Daily Status (Last 91 Days)

Jul 23 Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

September 2026
Investigating Network i\Issues
minor Observed active window 1h 25m

View incident details and source

Started:

Scalr Platform Scalr Worker
investigating
We are investigating reports of errors affecting Scalr customers. Customers may see timeouts or failed requests in their runs. We are looking into this and will post another update as soon as we have more information.
August 2026
Runs slow to start or failing intermittently
minor Observed active window 15m

View incident details and source

Started:

Scalr Platform Scalr Worker
investigating
We are currently investigating this issue.

Legacy Incident Archive

11 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.

April 2026
BitBucket VCS-triggered runs failing
major Source not attested
Last archived state: resolved
View archived record details
identified
We are continuing to work on a fix for this issue.
identified
We've identified the root cause and are actively working on a fix.
investigating
We are currently investigating this issue.