Status

The cache is best-effort by design. Degraded means slower builds, never failed builds — a remote miss falls back to building locally, exactly as it would on a machine that had never seen the cache. Nothing on this page can break a build.

Checking…

What each check means

Check	Fails when	You'd notice
database	The control plane can't reach Postgres.	Dashboard and token minting are down. Existing tokens keep working — the edge verifies them against a cached keyset.
cas_edge	cache.bento.build isn't answering its health route.	Cache reads and writes fall back to local. Builds are slower, not broken.
jwks	No active signing key exists to mint or verify against.	Newly minted tokens would be unverifiable. Existing ones are unaffected.
metering_freshness	Builds are landing but no meter write has arrived for 24 hours.	Usage numbers on the dashboard lag reality. Caching itself is unaffected.

The same rollup is available as JSON at GET /v1/status — unauthenticated, rate-limited per IP, and shaped for an agent to poll: { status, checks: [{ name, status, detail? }], generated_at }.