Skip to main content
GET
System status

Response

200 - application/json

System status.

status
enum<string>
required

Overall system health, the worst of any individual service or venue. degraded means at least one input crossed 60s of staleness; down means at least one crossed 5 minutes (or a process is hard-down).

Available options:
operational,
degraded,
down
timestamp
integer<int64>
required

Server time as Unix milliseconds.

uptime
string
required

Time since the last pipeline incident (data freshness > 60s OR a critical process scraped as down) within the trailing 7-day window, as a Go duration string (e.g. "3h12m40s", "168h0m0s" for a full incident-free week). Sourced from Prometheus, so it is stable across api-server restarts — rolling deploys do NOT reset this value. If Prometheus is unreachable, falls back to the process uptime of the serving container as a degraded-mode best-effort value.

venues
object
required
platform
object
components
object

Health of each customer-facing service. Three keys are returned:

  • data_pipeline — events ingested from venues into queryable storage. Reflects worst-of(ingest path liveness, venue freshness).
  • rest_api — HTTP API for historical and recent data.
  • streaming — WebSocket feed for real-time data.

The status page deliberately exposes services rather than the underlying processes — internal implementation components (message bus, storage engine, individual binaries) are folded into these three to give customers a clear answer without leaking the architecture.