Scalr Outage History

Some customers are unable to log into Scalr due to SSL errors.

We're experiencing an elevated level of run issues and are currently looking into the issue.

Some accounts are experiencing delays with runs starting.

We aare currently investigating an issue where some runs are stuck in a pending approval state without the ability to approve them.

We are currently investigating this issue.

We are currently investigating this issue.

Currently we are experiencing a CDN issue with the Scalr UI.

We are currently investigating this issue.

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 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/

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.

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.

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

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.

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

We are currently investigating this issue.

We are currently investigating this issue.

We are currently investigating this issue.

Some accounts are experiencing slow runs.

We are currently investigating this issue.

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.

GitHub is currently experiencing issues that might impact your workflows. Scalr.io is operating normally.