System status · live
What is up, what is stale, what is broken.
Every data source, every API endpoint, every scanner — current state, last refresh, and the operating targets we track. Updates every minute on page load.
Loading…
Coverage report
Loading…
RPC health
Loading…
Power queue
Priority detector refresh requests
Supported scanner · MEV loss index
Power requests enter the detector-refresh queue with a response target and a 24-hour refresh target for supported public snapshots.
Operating targets
What we track
| Surface | Target | Notes |
|---|---|---|
| Snapshot freshness (most scanners) | ≤ 24 hours | Daily cron; stablecoins + HL + Across refresh hourly |
| MEV detector run | hourly target | 100 blocks per run, finality depth 64 |
| Power refresh requests | response target < 4h, refresh target < 24h | Supported public detector snapshots; priority queue target, not a contractual freshness guarantee |
| API /api/snapshot/* | < 500ms p95 target | Edge-cached 60s; falls back to filesystem in dev |
| Methodology disclosure | public, hash-stamped | /benchmark + /status both expose the version + hash |
| Public methodology change | 14 days notice target | Posted on /benchmark + Twitter before activation |
| Incident response | acknowledged < 4h, resolved < 24h target | Founder oncall; PagerDuty wired post-launch |