Clarify lastSeenTimestampNs/lastUpdateTimestamp non-monotonicity on v8/v11 feeds - #4032
Open
sebastian-lerner-link wants to merge 3 commits into
Open
Clarify lastSeenTimestampNs/lastUpdateTimestamp non-monotonicity on v8/v11 feeds#4032sebastian-lerner-link wants to merge 3 commits into
sebastian-lerner-link wants to merge 3 commits into
Conversation
added 3 commits
August 6, 2026 16:58
Same root cause (median timestamp over configured data providers), same fix pattern (expect advancement as the norm; a single stalled or backward-moving report is expected and fine on its own; only escalate if it recurs across multiple consecutive reports or exceeds your own staleness threshold). No reason to ship this as two separate branches.
observationsTimestamp reflects report generation time, not confirmation that the underlying price changed, so it doesn't actually solve the freshness question. The recommendation stays lastUpdateTimestamp: reliable in the normal case, not bulletproof on low-DP feeds, with reliability improvements in progress.
Replace "small/low number of configured data providers" with a mechanism-first explanation: fewer providers means each one carries more weight in the median, without characterizing feeds as thin. Also drop "expected" from the single-occurrence framing so it reads as "not concerning" rather than "supposed to happen."
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
lastUpdateTimestamp) and v11 (lastSeenTimestampNs) feeds, the timestamp is a median across configured data providers, and can pause or occasionally move backward when the set of providers included in a report changes between reports.observationsTimestampas a suggested fix on the v8 page — it reflects report generation time, not confirmation that the underlying price changed, so it doesn't actually solve freshness detection. The recommendation stayslastUpdateTimestamp, described as reliable in the normal case but not guaranteed monotonic, with reliability improvements called out as active work.Test plan