--- title: X description: A monitor should not be Down on one screen and Unknown on another. Down, Degraded, Up, Paused and Unknown are now computed by one rule across the monitors… canonical: https://watchfor.io/changelog/2026-09-02-monitor-status-consistency --- [All updates](/changelog/page/5#2026-09-02-monitor-status-consistency) ⚡ Improved Sep 2, 2026 · v 6.4.3 # Monitor status is now consistent everywhere, with Degraded in the API A monitor should not be Down on one screen and Unknown on another. Down, Degraded, Up, Paused and Unknown are now computed by one rule across the monitors list, monitor page, dashboard overview and the REST API: an acknowledged critical incident keeps a monitor Down, a warning incident shows Degraded, and a confirmed incident always overrides Unknown. The API status field and /v1/summary counts now include "degraded", and the monitors list can filter by it. ## Why it mattered Status is the first thing you read, and it drives filters, counts and scripts. When the monitors list, the monitor page, the dashboard and the API each worked it out a little differently, one screen could say Down while another said Unknown, usually right after an incident was acknowledged or between two checks. ## The rule, top to bottom - Paused : you stopped the checks. Nothing else applies. - Down : a confirmed critical incident is open, whether it is firing or acknowledged. - Degraded : a warning incident is open. - Up : the latest check passed. - Unknown : no result yet. A confirmed incident always overrides it. ## Example At 02:14 a critical incident opens on your checkout API, and at 02:16 the on-call engineer acknowledges it. Acknowledging means "someone is on it", not "it is fixed", so the monitor stays Down on every screen and in the API until the incident resolves. A slow-response warning on the same monitor shows Degraded , never Down. ## In the API The status field can now be degraded , GET /v1/summary counts degraded monitors, and GET /v1/monitors?status=degraded filters by it, like the filter on the monitors list. The full precedence is in [Monitor status](/docs/core-concepts#monitor-status). Share this update --- Canonical page: https://watchfor.io/changelog/2026-09-02-monitor-status-consistency · Site guide: https://watchfor.io/llms.txt