Incidents
Feed incidents what went wrong, when, and when it ended
Every incident Feed Watch has recorded: stale and reverting feeds, price deviations, reserve and NAV moves, and config or owner changes. Newest first.
Incidents
Loading…
JSON: GET /v1/watch/incidents?chain=&kind=&since=&limit= · RSS feed · keyless, 0 credits. Alerts by email, webhook or Telegram for your own feeds come with a Workspace watch list.
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.