scalr.io logo and current status indicator

scalr.io Incident History

Operational

scalr.io 7 components

checked Sep 7, 2026 5:30 PM UTC · scalr.io's official status page

scalr.io is up and running.

scalr.io is currently operational with all systems functioning normally.

All components operational

Email only. No password. No card.

Be the first to know

Statusfield watches scalr.io alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.

Email only. No password. Free.

scalr.io incident history

4 reports published by scalr.io in the last 30 days

When scalr.io breaks, it is typically resolved in 1h 2m — median across 14 resolved incidents over 90 days.

September 1, 2026

Investigating Network Issues

Last update
  1. resolvedSep 1 · 17:06 UTC

    This incident has been resolved.

Reported by scalr.io on their status page.

August 27, 2026

Runs slow to start or failing intermittently

Last update
  1. resolvedAug 27 · 16:09 UTC

    This incident has been resolved.

Reported by scalr.io on their status page.

August 25, 2026

Runs Failing with "Self-hosted agent pool assignment is required by policy."

Last update
  1. postmortemAug 25 · 19:09 UTC

    **Root cause** A regression in a release deployed the morning of 2026-08-25 caused the run policy engine to incorrectly flag self-hosted agent pool assignments as non-compliant, triggering the error above even for correctly configured workspaces. **Resolution** The release was rolled back, restoring normal behavior. No customer action is required. **Preventive measures** We are adding regression test coverage for this specific scenario \(self-hosted agent enforcement combined with valid pool assignment\) to prevent recurrence, and reviewing our release validation process for this code path. We apologize for the disruption this caused to your pipelines.

Reported by scalr.io on their status page.

August 20, 2026

Scalr Docs Outage

Last update
  1. resolvedAug 20 · 16:49 UTC

    This incident has been resolved.

Reported by scalr.io on their status page.