Live · Auto-refresh 60s

System Status

Real-time health of the data plane, signal engine, and autopilot. Snapshot auto-refreshes every 60 seconds via SSR revalidate.

All Systems OperationalGenerated 2026-09-03 01:01:45 UTC
DB Latency
9 ms
SELECT 1 round-trip
Last Closed Signal
00:58:40 UTC
2026-09-03
Open Incidents
0
currently in progress
24h Incidents
0
opened in the last 24 hours
30d Incidents
0
total opened in last 30 days

Components

Per-component health: thresholds are conservative. "Degraded" means slower than expected, "offline" means stale beyond the degraded ceiling.

ComponentStatusSignal
DatabaseOperational9ms SELECT 1
WorkerOperationalheartbeat 27s ago
Streamer (Binance WS)Operationalheartbeat 4s ago
ScannerOperationallast run 2m ago
Terminal EvalOperationallast eval 3m ago
AutopilotOperationallast cycle 27s ago
Latest Closed SignalOperational3m ago

Data watchdog (hourly)

Our own tables checked against their expected cadence every hour: a venue's open interest jumping more than 30% between snapshot buckets, a counted liquidation feed going silent, a stale board cache, a late worker job, a missing daily metric. Findings stay here until they clear.

Last check 2026-09-02 17:54 UTC

No open findings at the last check.

How this is measured

Heartbeats come from the internal worker_state table updated by the worker, streamer, scanner, evaluator, and autopilot. A component is degraded when its last update is older than the healthy ceiling, and offline when older than the degraded ceiling. DB latency is a live SELECT 1 measured each render. Open incidents are read from the transparency log. See methodology.

This page reports platform health, not market conditions. A green status does not constitute investment advice.