Component statuses explained
A component is always in exactly one status, and the status's color follows it everywhere UpAll draws components: the live status wall, the components list, each component's page, client portals, and public status pages.
| Status | What it tells you |
|---|---|
| Up (green) | Checks are succeeding within the degraded threshold; no open incident. |
| Degraded (amber) | Checks succeed, but responses exceed the degraded threshold — slow, not broken. |
| Down (red) | An automatic incident is open after consecutive failed checks. |
| Paused | The Enabled toggle is off; no checks are running. |
| Unknown (grey) | Stale — no fresh result for 3× the check interval plus 30 seconds. |
Up (green)
The healthy baseline: checks run on schedule and succeed, response times sit under the degraded threshold, and no incident is open.
Degraded (amber)
The target answers, but slower than the component's degraded threshold. No incident opens and no email goes out — amber is a visual signal inviting you to investigate a trend before it becomes an outage. Details in the degraded latency threshold.
Down (red)
The exact trigger is an open incident: the component's configured number of consecutive checks failed (Failures before incident, 1–10, default 3). The incident's start is backdated to the first failure of the streak. The component stays red until a check succeeds — that single success auto-resolves the incident and turns the component green again. Opening and resolution both email all active workspace staff. Details in how incidents open and close.
Paused
The Enabled toggle is off, so no checks run at all. This status is deliberate — a human chose it, typically for planned maintenance — and it stays visible in lists so a switched-off component can't be forgotten. See pausing components.
Unknown (grey)
Unknown means UpAll expected a result and none arrived: no fresh result for 3× the check interval + 30 seconds — about three and a half minutes of silence for a 1-minute component. It's a statement about the monitoring pipeline, not the target: the target may be perfectly fine while results aren't coming through. When components go stale, staff receive a stale-components email digest, once per episode (stale components).
The distinction between red and grey matters: red is "we checked, and it failed"; grey is "we have no answer". Don't read grey as reassurance or as an outage — read it as a question that needs answering.
Where the colors appear
The live status wall ranks every component worst-first, so red rises to the top with amber below it — one glance tells you where to start (the live status wall). Client portals and public status pages show the same statuses for the components shared there, so what your client sees always matches what your team sees.