Which plan actually received the signal?
A public reset can reach Business, Pro, and personal surfaces at different times—or affect a weekly, five-hour, or banked window differently. Record the narrowest anonymous observation so the disagreement becomes measurable instead of anecdotal.
This page stores only fixed choices, a UTC observation time, and the public event ID. No email, login, cookie, account identifier, free text, or private usage value is collected. A segment appears publicly only after at least three reports.
The page defaults to the latest primary public signal. A shared event link can explicitly target a corroborating or contextual signal, whose role remains visible.
Share this event report with the same public event selected, so later replies stay attached to the evidence being discussed.
Loading public signal…
The public event is loading.
Report one observed result
Choose the closest categories. “Not sure” is valid and remains separate from both outcomes.
Thresholded rollout pattern
Loading the thresholded aggregate…
What this can prove
It can show a thresholded pattern among anonymous reports tied to one public signal. It cannot prove eligibility, identify a person, or replace the exact state shown by your Codex client. Mixed results are useful: they reveal rollout or window differences without turning one account into a universal verdict.