# Monitor health, readiness, and status

Use `GET /healthz` to check that the HTTP process is alive. It returns `200 {"status":"ok"}`; it does not indicate licensing readiness. Use `GET /readyz` for load-balancer routing and availability alerts. It returns `200 {"status":"ready"}` only when the Gateway can serve its role; it returns 503 for conditions such as standby, unavailable state, or invalid/expired license.

Authenticated status interfaces are `GET /v1/status` (service, license and HA summary), `/v1/license` (safe license metadata), `/v1/entitlements` (limit, live and available capacity), and `/v1/ha` (mode, peer connection and split-brain warning). They are the supported means to inspect node role and peer state. There is no separate version or node-ID HTTP endpoint; use `keystone-gateway version` and `node-id` locally.

Alert on readiness failure, negative/near-zero license expiry time, capacity exhaustion responses, `keystone.gateway.peer.reachable = 0`, `keystone.gateway.ha.split_brain_possible = 1`, and a rise in lease rejections. See [observability](https://portal.cjcit.io/knowledge-base/keystone_gateway/0.2/operations/observability/).