Oracle failure and stale prices

Reference data and execution are different

An oracle can aggregate external prices and publish an update onchain. A trader may still face spreads, impact, limits, or a closed market when trying to execute.

Data can become stale or disputed

Exchange outages, network congestion, source divergence, or delayed updates can reduce confidence in a reference. Protocols may apply deviation bounds, freshness checks, or fallback sources.

Protective controls change availability

A venue may pause new positions, restrict a market to reduce-only, widen parameters, or wait for a reliable update.

• Check market status
• Compare timestamp and source
• Do not infer liquidity from the oracle value alone

Freshness is only one dimension of data quality

A recent timestamp can still carry a bad value if sources diverge or a feed is misconfigured. A sound design considers source count, confidence, deviation, update cadence, market status, and fallback behavior. Traders should compare the provider’s reference with independent executable markets when conditions look abnormal.13

Protective behavior can include price clamps, order bands, new-order pauses, reduce-only mode, or queued orders until the underlying session resumes. These controls trade availability for integrity and can leave an existing position exposed while new hedges are restricted.42

Do not confuse a stale quote with a free option

A visible old price is rarely guaranteed executable. A transaction may be rejected, settled from a newer oracle update, or wait for a market reopening. Repeated submissions add operational risk and can execute later under different conditions.21