Skip to main content

Understand quote freshness, price changes and latency

A price can remain unchanged while the source successfully confirms it. Price-change age and quote freshness answer different questions.

Follow the original clocks

  • Source time: a provider clock when present and validated; it can be unavailable.

  • Confirmation time: the latest successful observation confirming the quote.

  • Price-change time: when the recorded price value changed.

  • Delivery time: when Oddswire sent the response.

For example, a price last changed several minutes ago may have been confirmed seconds ago. A newly delivered retained snapshot can still be old. Delivery does not refresh source evidence.

Interpret measurements correctly

Request-to-complete-response time measures a request. Native price-change-to-receipt time needs a valid source-change clock. Quote age is neither of those. Last-known measurements keep their original age and must not be presented as current live latency.

Display eligible state

Use the returned state and freshness limit. Withhold stale, suspended or unavailable prices from active calculations. Do not substitute an older price or reset timestamps on replay or refresh.

See Odds freshness versus price changes and Data conventions. These clocks do not establish a production speed guarantee.

Did this answer your question?