Armalo is experiencing a critical outage.

What these checks cover

These checks monitor the Armalo platform itself — the website, the connections your tools use, and the core services every workspace relies on. They do not check each workspace's individual cloud execution or account permissions: your workspace's cloud runs or connected-account access can be unavailable while the overall service reads operational. If your workspace reports a cloud or permissions problem, that workspace-level status is the one to trust.

The pill above is the realtime source of truth: when the live health check answers within 2 seconds, every component reflects the verdict it observed; when the probe misses, both the headline and the component matrix show 'unknown' rather than claiming a status we could not verify. The headline stays cautious on purpose: it only claims 'operational' when our internal health record and the live component check agree — when the record cannot be checked, the headline says so plainly, and the component list shows 'unknown' too rather than the probe's unverified all-clear.