Skip to content
Live · Auto-refresh 60s

System Status

Real-time health of the data plane: recorders, caches and streams. Snapshot auto-refreshes every 60 seconds via SSR revalidate.

All Systems OperationalGenerated 2026-10-23 10:15:31 UTC
DB Latency
6 ms
SELECT 1 round-trip
Last Data Point
10:15:25 UTC
2026-10-23
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.

ComponentStatusHealth
DatabaseOperational6ms SELECT 1
WorkerOperationalheartbeat
Streamer (Binance WS)Operationalheartbeat
Market cacheOperationalrefreshed
Venue snapshotsOperationallast run
Liquidation streamOperationallast print

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-10-23 09:51 UTC

LevelCheckSubjectDetail
warnfeed_stale:orderbook_depthweexno record in the registry's lookback window

How this is measured

Heartbeats come from the internal worker_state table updated by the worker, the streamer and the market recorders. 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.