Gateway Health Checks

Verify a Livepeer gateway is alive and routing jobs - health endpoints, status commands, deposit checks, and orchestrator reachability for Video, AI, and Dual gateways.

This is the first of five monitoring guides. Run these checks after starting a gateway, after any configuration change, or when something seems wrong. Health checks are quick - for full observability setup, see .

Universal Checks

Video AI Dual

These checks run on all Gateway operational and node mode configurations.

HTTP health endpoint

Confirms the gateway process is running and responding on the configured -httpAddr port (default: 8935).

Check Command

curl http://localhost:8935/health

A healthy gateway returns HTTP 200 with a JSON body. Any non-200 response or connection refused means the process is not running or the port is wrong.

Expected Response

{
  "status": "OK"
}

Node status via livepeer_cli

Confirms the gateway’s identity, network connection, active sessions, and (for on-chain gateways) deposit and reserve balances.

• Select Option 1: Get node status from the interactive menu.

CLI Command

# Standard (binary on host)
livepeer_cli -host 127.0.0.1 -http 5935

# Docker container
docker exec -it <container_name> livepeer_cli -host <container_hostname> -http 5935

The status output appears under BROADCASTER STATS (the CLI uses the legacy term “Broadcaster” for Gateway).

Hardware status

Confirms GPU availability, memory usage, and temperature. Useful for AI and Dual gateways where GPU resources are shared.

Check Command

# GPU utilisation, memory, temperature
curl http://localhost:8935/hardware/stats

# GPU model and system info
curl http://localhost:8935/hardware/info

Node Type Checks

Automation

Health Checks can be automated and notify operators of issues.

Cron Script Automation

Cron Script Automation

#!/usr/bin/env bash
# gateway-health.sh - run every 5 minutes via cron

GATEWAY_PORT="${1:-8935}"
ALERT_EMAIL="[e-mail]"

if ! curl --silent --fail --max-time 5 http://localhost:${GATEWAY_PORT}/health > /dev/null 2>&1; then
  echo "Gateway on port ${GATEWAY_PORT} is not responding" | \
    mail -s "ALERT: Livepeer Gateway Down" "$ALERT_EMAIL"
fi

Add to crontab

# Add to crontab
*/5 * * * * /path/to/gateway-health.sh 8935

Docker HEALTHCHECK Automation

HEALTHCHECK

HEALTHCHECK --interval=30s --timeout=10s --retries=3 \
  CMD curl --silent --fail http://localhost:8935/health || exit 1

For full observability with time-series metrics, alerting, and dashboards, see .

Related Pages

Tools & Dashboards

Explorer, Livepeer Tools, livepeer_cli for visual monitoring.

Monitoring Setup

Prometheus + Grafana for production observability.

Troubleshooting

Fix common errors by symptom.