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.

Active IncidentGenerated 2026-04-21 16:56:52 UTC
DB Latency
11 ms
SELECT 1 round-trip
Last Closed Signal
16:53:22 UTC
2026-04-21
Open Incidents
0
currently in progress
30d Incidents
1
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
DatabaseOperational11ms SELECT 1
WorkerUnknownheartbeat no data
Streamer (Binance WS)Unknownheartbeat no data
ScannerUnknownlast run no data
Terminal EvalUnknownlast eval no data
AutopilotOfflinelast cycle 40h ago
Latest Closed SignalOperational4m ago

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.