Skip to main content

Bucketed availability over an arbitrary window for a single check

GET 
/api/v1/orgs/:org/checks/:check/availability/buckets

Cuts [from, to) into uniform, hour-aligned availability cells — the data behind the check-detail chart's availability strip. Deliberately a separate route from /api/v1/orgs/{org}/checks/{check}/availability, which speaks trailing calendar tokens with a tz, has no from/to at all and is capped at 12 periods.

Counting is the shared engine's: lifecycle markers and abandoned attempts are excluded from BOTH numerator and denominator, warning counts as up, and maintenance probes count exactly like any other (maintenance exclusion is SLO-only). A cell with no countable probes has hasData=false, availabilityPct=null and status="noData" — no data is not 100%.

Cells are aligned OUTWARD to bucket boundaries, so the series may start before from and end after to. The window object is the exact [from, to) fold (it also includes the month tier, which is deliberately never attributed to a single cell) and is what a client renders when the window is too short for a legible strip.

Request​

Responses​

Bucketed availability