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 PlatformTrusted by 1000+ teams
Need to monitor Scalr outages?
Stop finding out about outages from your users. Monitor 6,020+ cloud services and get alerted the moment something breaks.
Ready to take control?
Start Free Trial
No credit card required
Set up in 2 minutes
14-day free trial
Latest Updates ( sorted recent to last )
RESOLVED
6 months ago - at 10/07/2025 10:14PM
This incident has been resolved.
IDENTIFIED
6 months ago - at 10/07/2025 08:42PM
The issue has been identified and a fix is being implemented.
INVESTIGATING
6 months 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
Scalr UI works inconsistently - 4 months ago
Docker Registry Outage Impacting Runs - 7 months ago
Issues with AzureDevops Integration - 7 months ago
Issues with Gitlab integration - 8 months ago
The Status Page Aggregator with Early Outage Detection
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 · 6020 services available
Integrations with
