Feed health
Oracle feed health fresh, stale and reverting feeds, per chain
Every oracle feed FeedPlumb watches, read from public chain data about every 2 minutes. The figures load live from the Feed Watch API on this site.
Now
Loading…
JSON: GET /v1/{chain}/watch/summary and GET /v1/{chain}/watch/feeds on this host, keyless, 0 credits.
XDC Network blocks and gas
Loading…
JSON: GET /v1/watch/chain-health?chain=xdc (also chain=base), keyless, 0 credits.
Latest incident per chain
Loading…
How Feed Watch decides
- Fresh
- The last update is no older than the feed's heartbeat plus 10 minutes. Plugin (PLI) feeds on XDC publish no heartbeat, so 24 hours is used.
- Stale
- The last update is older than that. An incident opens and closes when the feed updates again.
- Reverting
- latestRoundData() on the feed fails, so no round can be read.
- Deviation
- The answer differs from an independent reference price by more than 1 %, or by more than twice the feed's own deviation threshold if that is larger. References older than 1 hour are not used.
- Reserve drop and NAV move
- A reserve feed round at least 5 % below the previous one, or a NAV round that moves 2 % or more.
- Config and owner change
- The feed proxy points to a new aggregator, or its owner changes. Checked every hour.
- Scan
- Every feed is read about every 2 minutes through public RPC endpoints. Base is in preview.
The boards on the Data Dashboard use a wider window (1.5 times the heartbeat), so a feed can show as stale here a little earlier. Full rules: Methodology.
Operational data from public blockchain sources. Nothing on this page is financial, legal or tax advice.