Public comparison sample

Measure the clocks, not the slogans.

The freshness lab samples public monitor surfaces side by side. It keeps a collector check, a provider-reported signal timestamp, and a measured source-to-observation interval in different columns, so “updated” means something testable.

All timestamps are UTC. This page is read-only and never requests a Codex login, account identifier, cookie, or private source payload.

Forecast spread: when public surfaces disagree, the lab shows the range and preserves each source's estimate. It is a comparison of published snapshots, not a vote or a private-account forecast.

Live sample

Sampling public surfaces...

Loading public sample...

The lab keeps the external payloads out of the public response.

This is a live sample plus a persistent change history. External timing means publicly reported timestamp to ResetPulse observation; it is not a provider SLA, an account-level reset time, or proof that the compared services use independent sources.

How to read the comparison

Collector check

A recent successful check shows that a monitor can reach its configured surface. It does not prove that a source changed, that the signal is correct, or that every account reset.

Public signal time

A public feed may report when its latest signal was published. That is useful context, but it is not the same as the time a monitor first observed a new event.

Measured propagation

Only a source timestamp paired with a first-observed timestamp can produce a timing sample. ResetPulse publishes this as a separate evidence field and leaves it pending when the record is not sufficient.

Cross-source consensus

The live panel counts only available sources with explicit signal states, shows how many agree, and keeps minority states visible. It compares latest public signals only when their timestamps fall within the stated alignment window; a majority is a consistency check across nearby public records, not an official verdict or proof of every account.

Source independence

Several dashboards may reuse the same upstream post or feed. Until that relationship is independently verified, ResetPulse labels agreement as surface consistency rather than independent corroboration.

Why this helps

Readers can compare a real public sample instead of trusting a “fastest” badge. Developers can open the JSON contract and build their own audit view.

Share a verifiable comparison

Use the JSON sample for a technical discussion, the market comparison for context, or the integration guide when a reader wants a portable receipt or notification workflow. The lab is a comparison tool, not a request for votes or duplicate posts.