Data sources, without overclaiming.
ResetPulse is useful when timing reports disagree, but a public signal still has limits. This page explains what is observed and what remains account-specific.
Public signal
ResetPulse watches a public signal surface and records the observable author, content, timestamp, and apparent reset scope. It does not read private Codex accounts.
Two clocks
Source time is when a public update says an event happened. Observation time is when the monitor saw it. The timeline keeps those measurements separate.
Evidence states
An early signal is published as a lead. A confirmed event requires the available evidence to line up; ambiguous or incomplete observations remain qualified.
Account limits
Plan, timezone, rolling-limit, banked-reset, and account-state differences can produce different outcomes. One public event is not a guarantee that every account changed simultaneously.
What the public record contains
The timeline and status endpoint expose event titles, summaries, source timestamps, observation timing, confidence state, and the public history. Absolute times on public pages and in the RSS feed are shown in UTC. Private source URLs, internal identifiers, credentials, and operational authorization details are intentionally omitted.
Parallel public collection
To reduce renderer and cache lag, ResetPulse checks the direct public profile page and a public timeline relay in parallel. Both lanes represent the same public source origin, so the relay can improve reachability and collection speed but is never counted as independent corroboration. The monitor health receipt keeps their HTTP status, parsed-item counts, and claim states separate.
Source relationship ledger
The public health receipt separates distinct origins from independently verified claims. A Reddit discussion can be a different public origin while remaining an unverified community report; a timeline relay can be a faster path to the same origin while counting as zero independent sources. This prevents a larger source count from becoming a larger claim. Read the live source relationship ledger or fetch the JSON receipt.
Independent service context
ResetPulse also checks a public service-status summary as context. An incident or an all-clear can help explain timing, but it never confirms a quota reset by itself. The monitor health API exposes collector freshness, last successful source-fetch health, and this boundary without revealing private source details.
Community observations
The live timeline and Rollout Lens may accept anonymous fixed-choice reports from a Codex surface. New reports are tied to the latest public event and contain only a public event id, normalized UTC observation time, surface, scope, broad plan/workspace type, limit window, and result; they contain no login, email, free text, credential, or account identifier. Reports remain unverified and segment breakdowns are shown only after a minimum sample threshold.
What ResetPulse does not claim
ResetPulse is not an official OpenAI product, does not provide an official quota guarantee, and cannot prove the private state of an individual account. When evidence is incomplete, the correct result is unknown rather than a universal rule.
Keep checking the record
See the live timeline, read the monitoring methodology, or review the alerts FAQ.