Monitoring checks
A check combines a target, a protocol, an interval, success criteria and a measurement source: the platform or a status agent. Test the configuration before enabling it, then choose whether it is public.
- Pause, resume, manual run and duplicate
- Bulk actions across checks
- Results tied to the configuration version
Status agents
For an internal service, install an agent with the CLI: a short-lived cps_… key allows status-agent:enroll, then the agent sends a heartbeat, fetches its configuration and submits results.
Incidents and maintenance
An incident has a state, an impact, components and dated updates; it can be acknowledged, resolved or merged with another incident that has the same cause. Maintenance announces a planned window.
Email subscriptions for visitors
Status page visitors can subscribe, confirm their address and unsubscribe with the link they receive. The page draft can be previewed before it is published.
Alerts
Create a channel, verify it and send a test before attaching it to a rule. The history shows each delivery, successful or not, without exposing channel secrets.
The public status.cdn.pizza page runs on the same monitoring engine.

