Outage in Scalr
Runs Are Not Using the Account Level Default Agent Pool
Resolved MinorIncident Report
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.
Components affected
Scalr PlatformNeed to monitor Scalr outages?
One place to monitor all your cloud vendors. Get instant alerts when an outage is detected.
Try IsDown risk-free
14-day free trial · No credit card required
Latest Updates ( sorted recent to last )
RESOLVED
19 days ago - at 10/07/2025 10:14PM
This incident has been resolved.
IDENTIFIED
19 days ago - at 10/07/2025 08:42PM
The issue has been identified and a fix is being implemented.
INVESTIGATING
19 days ago - at 10/07/2025 08:42PM
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.
Latest Scalr outages
Docker Registry Outage Impacting Runs - about 1 month ago
Issues with AzureDevops Integration - about 2 months ago
Issues with Gitlab integration - 2 months ago
Scalr Website Down (Does not impact the application) - 2 months ago
The Status Page Aggregator Built for IT Teams
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 4522 services available
Integrations with
