CMDash status

Incident history

What this page can and can’t tell you

• Database, Cache & background jobs, and File & report storage are real, direct checks of CMDash’s infrastructure — the same dependencies GET /health/ready reports — recorded every 5 minutes.
• Those checks run from inside CMDash’s own environment. They are not a measurement of your specific network path, browser, or region, and a component reading “operational” here does not guarantee every feature of the product is reachable from where you sit.
• Application reflects CMDash’s automated browser-based canary, which logs in every 15 minutes and exercises real product flows (dashboard, compliance, integrations, risk register) against production. It reports only a coarse pass/fail plus flow counts — never the underlying error message, which stays in CMDash’s own CI system — and, like the other three components, reads as “no recent data” rather than a stale “operational” if the canary itself stops running.
• Availability is the share of recorded checks that did not fail over the window — not the share of days without a failure — so one failed check among hundreds does not turn a day red. Slow-but-answering checks count as available. Canary runs that never executed are canary infrastructure problems and are excluded rather than counted as product downtime. A percentage appears only once enough days and checks have been recorded; until then the tile says so and states when measurement began. Nothing is estimated or filled in for earlier dates.
• A gray “no data” bar in the history means no check was recorded that day — it is never shown as green, and history only goes back as far as CMDash has actually been recording it.
• Incident history above is curated by the CMDash team, not generated automatically.