🟢 Data Freshness
Real-time health and freshness status of every metric in the Algo Tick sensor network. Each metric shows its last update time, ingest latency (chain→local), and current status.
100%
System Health
11
Fresh Metrics
0
Stale Metrics
11
Total Tracked
How Freshness Works
Every data point has two timestamps: time_chain (when the event occurred on-chain or at the exchange)
and time_local (when our sensor ingested it). The difference is the ingest latency.
A metric is fresh if updated within 2 minutes,
warm if within 10 minutes, and
stale otherwise.
Metric-Level Freshness
| Metric | Pack | Last Update | Ingest Latency | Status |
|---|---|---|---|---|
eth_basefee_live | macro_congestion | 4s ago | 3.7s | fresh |
eth_block_number | macro_congestion | 0s ago | -9ms | fresh |
eth_block_tx_count | macro_congestion | 0s ago | -9ms | fresh |
eth_block_utilization_pct | macro_congestion | 0s ago | -6ms | fresh |
eth_burn_rate_live | macro_congestion | 0s ago | -6ms | fresh |
eth_priority_fee_gwei | macro_congestion | 0s ago | -5ms | fresh |
hlp_funding_rate | derivative_execution | 0s ago | -9ms | fresh |
hlp_liquidation_alerts | derivative_execution | 0s ago | -2ms | fresh |
hlp_mark_price | derivative_execution | 0s ago | -9ms | fresh |
hlp_open_interest | derivative_execution | 0s ago | -8ms | fresh |
hlp_orderbook_imbalance_pct | derivative_execution | 0s ago | -8ms | fresh |
📡 Ingest Pipeline
Data flows through the following pipeline:
- Source → Sensor: WebSocket/gRPC connections to exchanges, L1 nodes, and bridge contracts
- Sensor → Redis: Sub-millisecond publish to the in-memory message bus
- Redis → API: Live snapshot available immediately via REST and WebSocket
- Redis → R2: Parquet files written every hour to the data lake with Hive partitioning
Don't just stare at the dashboard. Automate it.
Every metric on this page is available via our sub-millisecond API.
Build trading bots, backtest strategies, and power AI agents with institutional-grade data.