Request-time status is rendered from the reviewed UTC ledger.
The canonical route is server-rendered so crawlers and visitors receive the current verified answer in the initial HTML.
UTC date: request time
LIVE RESET STATUS
Did Codex Reset Today?
This page answers from the reviewed public reset ledger in UTC. It does not infer a reset from a personal account timer, an outage, a banked credit, or an ambiguous social post.
Latest reviewed automatic reset
The latest reviewed event is rendered at request time.
What “today” means here
The status uses UTC so every visitor sees the same auditable date boundary. A broad reset and a targeted reset are reported separately instead of being blended into one claim.
Your personal reset can be different
Your five-hour and weekly usage windows are account-specific. Check your own Codex usage screen for those timers; this page tracks public automatic-reset evidence only.
SOURCE RULE
A reset is confirmed only when the source and scope support it
Primary-source wording is reviewed for reset type, audience, timestamp precision and scope. If a post says a reset happened but does not establish whether it was broad or targeted, that uncertainty is preserved rather than filled in.
SEP 12 AUDIT
“Reset all propagated” is tracked as scope-unresolved context
Tibo’s 12 September 2026 post confirms that a reset propagated, but the post itself does not name Codex or ChatGPT Work and does not explicitly identify a broad user population. Because a verified Astra-targeted reset appears nearby in time, this project does not silently promote the propagation post into the broad/global ledger.
NEXT RESET
Want probability instead of confirmation?
Use the live 24/48-hour outlook for the current experimental estimate, or read the CNR-0.4.2 research results to see how the next-generation model is being evaluated.