System status
Measured from the running system when you loaded this page — not a number somebody types in after an incident.
-
Checking…
API and event ingest
The endpoints your app posts events to, and the dashboard reads from.
-
Checking…
Database
Where monitors, flows, alerts and history are stored.
-
Checking…
Event ingest
Heartbeat pings and flow step events sent by your app.
-
Checking…
Silence and stall detection
The sweeps that decide a heartbeat has gone silent or a flow has stalled.
-
Checking…
Domain, certificate and expiry checks
Uptime probes, SSL and registration lookups, and the daily expiry reminders.
-
Checking…
Alert delivery
Sending alerts to email, Slack, Discord, SMS and phone, and re-sending unacknowledged ones.
How this page is measured
- Nothing here is hardcoded. Each line is a real check made when you loaded the page: a database round trip that is timed, the age of each background job's last run, and the number of alerts waiting in the delivery queue.
- “No data” is a state. A background job that has never recorded a run reads as no data, never as healthy — the same rule the uptime history follows, where a domain with no checks shows null rather than 100%.
- Late is judged against the schedule. A job due every five minutes is not late at six. It reads degraded once it is several intervals behind, and down when it has clearly stopped.
- This page has no history yet. It reports now. Past incidents are not listed here, so treat the absence of an incident log as exactly that.
Releases are listed in the changelog. Anything wrong here, or an outage this page missed, goes to [email protected].