Scalr had 32 outages in the last 2 years totaling 579h 51m of downtime — averaging 1.3 incidents per month.
There were 32 Scalr outages since June 3, 2024 totaling 579h 51m of downtime. Each is summarised below — incident details, duration, and resolution information.
Some accounts are experiencing longer than usual wait times for runs to execute.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Some customers are unable to log into Scalr due to SSL errors.
The issue has been identified and a fix is being implemented.
The release is being rolled back and we expect the fix to be completed in ~10-15 minutes
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We're experiencing an elevated level of run issues and are currently looking into the issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Some accounts are experiencing delays with runs starting.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We aare currently investigating an issue where some runs are stuck in a pending approval state without the ability to approve them.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
We are continuing to monitor for any further issues.
This incident has been resolved.
**Update #1** On April 28 at approximately 15:00 UTC and again on April 29 at approximately 15:22 UTC, a load spike affected our internal task queue, which slowed down the mechanism Scalr uses to transition runs between pipeline stages. In some cases, the transition task failed before it could complete, leaving runs stuck in a waiting state with no automatic recovery path. Both times, the queues cleared on their own while our engineering team investigated. We have already shipped an improvement \(released April 30\) that makes this transition task significantly more resilient to lock contention, greatly reducing the likelihood of runs getting stuck. We are continuing to investigate the underlying cause of the queue spikes and will share further updates as the investigation progresses.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
Please follow updates [here](https://status.scalr.io/incidents/mjzqwnbjnt9f).
We are currently investigating this issue.
We've identified the root cause and are actively working on a fix.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Currently we are experiencing a CDN issue with the Scalr UI.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
We've implemented a hotfix that should significantly decrease number of errors.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
Runs are not using agents if the agent is set as the default for the account. A workaround, for now, is to set the agent pool in the workspace settings explicitly. A fix is in progress to ensure that the account-level defaults are used as expected.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
The Docker Registry outage is impacting Scalr's ability to pull images, resulting in run failures. We are actively monitoring the status at https://www.dockerstatus.com/
From Docker: We are continuing to work on implementing a fix. We will update as the status evolves. https://www.dockerstatus.com/
This incident has been resolved.
We're currently investigating an issue where Azure VCS integration cannot be created or reauthorised with Scalr-managed Azure application:"AADSTS700016: Application with identifier 'c375f129-2031-43cf-8e01-a8cdac263bf1' was not found in the directory 'Default Directory'". If you encounter this issue, please temporarily use another authentication method such as a Custom Azure Application or a Personal Access Token.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We're currently investigating an issue where GitLab integration can stop working with an error: "The provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client." If you experience this issue, please manually re-authorize GitLab connection from the Integrations page. Contact support if you have further questions.
Issue is related to a GitLab incident: https://gitlab.com/gitlab-com/gl-infra/production/-/issues/20398 . If your integration is affected, please re-authorize GitLab integration to fix it.
The scalr.com website is down due to an issue with Cloudflare. This does not impact the scalr.io or the Scalr application. Users can continue to sign up at scalr.io
This incident has been resolved.
Some users are experiencing intermittent connection issues with the Azure provider.
We are continuing to investigate the intermittent connection issues between Google Cloud and Azure. This is impacting a few customers. Please get in touch with us for further options if this is impacting your ability to execute runs.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We want to inform you of a recent issue affecting our auto-apply functionality. We've identified a bug where auto-apply is automatically disabled when the latest state comes from a branch that differs from your workspace branch. The bug was introduced today, and our engineering team is actively working on a fix that will be deployed within the next 12-24 hours. We wanted to make you aware in the event that you see a workspace that should be auto-applied, but is waiting on approval. We apologize for the inconvenience, and please let us know if you have any questions by opening a ticket at support.scalr.com
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We're currently working on a fix for runs that are failing with: │ Error: Failed to parse command-line flags │ │ flag provided but not defined: -var-file
**RCA** A fix was released to ensure `.tfvars` files are properly loaded during the `init` phase with `for-each` feature, that was introduced in the OpenTofu [1.9.0](https://opentofu.org/blog/opentofu-1-9-0/) version. Technical details: * To fix the issue we added processing of the `.tfvars` on `init`, `validate, `and `fmt` phases for runs with the flag `-var-file.` * But consuming the `.tfvars` file using the `-var` and `-var-file` options was introduced in OpenTofu [1.8.0](https://opentofu.org/docs/v1.8/intro/whats-new/), and exception handling was missed for any versions less than 1.8.0. * Because of this, all runs with `.tfvars` files in the VCS-driven workspaces with OpenTofu < 1.8.0 and all Terraform versions supported by Scalr were affected.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Some accounts are experiencing slow runs.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The Scalr platform is operational, this is just a notification about a bug in the resources report feature. We recently found a bug in the resource report showing that all resources for an account have been deleted. We can confirm that the resources have not been deleted, and there is no impact to state files. The bug only impacts the resources report functionality, nothing else. We are in the process of fixing the report and temporarily removing it from the UI while the fix goes in. We apologize for the inconvenience this may cause.
The issue has been identified and a fix is being implemented.
This incident has been resolved.