Status
Computed from real production data every 15 minutes. Not an SLA in v1; we publish a contracted SLA at Phase 4 Enterprise launch.
How to read it: the percentage for audits, page rendering and AI analysis is the success share of the most recent 20 runs on the current release (within the past 24 hours), so a problem that a release fixed stops showing as down once the new release has run successfully. Until the current release has at least 5 runs, the row keeps showing the runs before it and says so. The full 24-hour share is shown underneath for context. The two “on time” rows are the share of scheduled customer work (tracked prompt refreshes, Agency reports) that is not more than 24 hours overdue. Scheduled jobs are scored against their own schedule: a job that stops running shows as down. Jobs that run once a day or less often are scored by their latest run, and an earlier failure is noted.
Scheduled jobs
Runs recorded against each job's schedule. A job that stops running shows as down even if it never errors.