Operations
Platform status
RELIASTRA’s own health is reported the same way we report vendors: explicitly, with distinct states for distinct causes.
Current state
The platform is operational. Scheduler and worker liveness are published as time-limited heartbeats and surfaced through the API health endpoint - a pipeline that has stopped is reported as broken rather than presenting an empty history.
Programmatic health
Operators can poll GET /health on the API for the deployment contract (Postgres, Redis, worker and scheduler liveness). See the operating-model documentation for the runtime contract.
Vendor status vs platform status
This page reports RELIASTRA’s own health. Live third-party posture lives on Track, where each vendor page shows current state, uptime, latency and incident history measured independently.
Reporting a problem
Write to support@reliastra.com with the affected surface, time window (UTC) and any request IDs.
Know when your dependencies fail. Prove what happened.
Monitor the external APIs your product relies on, correlate their failures with your incidents, and generate verifiable evidence when a vendor causes downtime.