Skip to main content

Developer operations

Background-service signals.
Without calling them API uptime.

A rolling view of selected scheduled services that support delivery and automation. For declared customer-facing incidents, use the public system status page.
  • 24-hour job window
  • 60-second revalidation
  • No tenant data exposed
All systems operational

Updated every minute from the background-job run ledger.

  • Scheduled job dispatch
    dispatch-tick
    100% successful
    79 runs
  • Webhook delivery retries
    webhook-retry
    100% successful
    79 runs
  • Email + SMS delivery
    notifications-health
    100% successful
    7 runs
  • Background job processor
    process-jobs
    100% successful
    399 runs
  • Live class streaming
    auto-stream
    100% successful
    396 runs
  • SLO + incident alerting
    evaluate-slo-alerts
    100% successful
    40 runs
How to read this page: these are scheduled-job outcomes, not synthetic HTTP uptime checks and not a contractual SLA. Review system status for declared incidents and service levels for the formal availability framework.