Component health
Each attached monitor has its own effective public state, including waiting-for-evidence and incident-driven states.
Background-service status pages
Your API can be green while the service customers need is red.
LatidoFlow status pages can show uptime and heartbeat monitors as separate components. Background-job incidents affect the shared service state even when an HTTP endpoint still returns 200.
Publish the service dependency, not only the website.
Attach uptime and heartbeat monitors as named public components. The page derives component state from current monitor health and open incidents, then aggregates those components into operational, degraded, monitoring, or major-outage status.
That means a healthy Billing API component can stay operational while a failed Billing exports component changes the overall page to a major outage. Visitors see the distinction instead of one status hiding the other.
What visitors can verify on the page
Run history
Components show completed-run success and recent recorded outcomes rather than a status label with no execution context.
Open incidents
An unresolved incident remains visible while recovery is still running; a pause does not erase it.
Operator updates
Teams can publish customer-facing incident messages directly on the page.
Maintenance context
Structured maintenance entries can include timing, impact, and an operator summary.
Access control
A status page can be public or protected with a shared password.
Confirmed subscriber delivery
Visitors can subscribe by email through confirmed double opt-in and use a signed unsubscribe link later. Delivery evidence records provider acceptance separately from inbox placement, reading, or human response.
Model components around customer-visible capabilities
A useful component answers what customers are waiting for: invoice exports, nightly catalog refreshes, settlement processing, or outbound notifications. Keep the public label customer-safe and attach the monitor that supplies the underlying execution evidence. Do not expose secrets, internal command arguments, or raw payloads in operator updates.
Keep exploring
Add one background dependency to your status page
Start with the asynchronous service whose failure can hurt customers while your web health check remains green.