Read expiry and recheck

Read observation time and expiry #

Observation time tells you when PeelSignal recorded the check. Source timestamps tell you when the underlying evidence was produced. Expiry tells you the limit assigned to that receipt under its policy.

Use the displayed values. The service does not promise one universal lifetime for every feed or receipt.

Policy 1.0.0 caps receipt lifetime at 300 seconds from observation and at the feed timestamp plus its reviewed age bound. An already stale feed can produce an already expired receipt.

When a receipt expires #

An expired receipt remains a historical record. Its original statuses and evidence stay visible, with an expiry notice. It should not be read as a statement of current conditions.

A page refresh or cached response cannot extend the recorded expiry. An old Fresh result can belong to an expired receipt.

Request current evidence #

Select Recheck to run another observation. Open its details and compare its timestamps with the older receipt. Conditions may have changed, or a source may now be unavailable.

A recheck creates a new receipt even when the panel labels remain the same. The new ID and observation time distinguish the checks.

Keep source age in view #

Freshness rules use the reviewed metadata for the supported feed. A recent request time cannot make an old source value recent.

If a required timestamp or threshold is missing, the affected check stays Unknown. See Price integrity.

Explorer and market retrieval times record when PeelSignal received their data. They do not establish that indexed fields reflect the receipt’s RPC block or that a market quote was updated at retrieval. Pair creation time describes when a pool was created, not the freshness of its price.