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-tickno data - Webhook delivery retries
webhook-retryno data - Email + SMS delivery
notifications-healthno data - Background job processor
process-jobsno data - Live class streaming
auto-stream100% successful1000 runs - SLO + incident alerting
evaluate-slo-alertsno data
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.