What we watch, and what counts
Every event in the record comes from a named public source. If we can’t point at one, it doesn’t go in, however many people report it.
Watched sources
The check times below are the real schedule. We look for announcements first, and the reset status is evaluated a minute later, each every five minutes.
| Source | What it gives us | Checked | Weight |
|---|---|---|---|
| @thsottiaux | Codex lead. Most resets are announced here first. | every 5 min | Primary |
| @OpenAI, @OpenAIDevs | Launches, milestones, and occasional reset confirmations. | every 5 min | Primary |
| status.openai.com | Outages and fixes. Context for make-good resets. | every 5 min | Supporting |
| OpenAI developer forum, Codex category | What users report about limits, and official OpenAI replies quoted in those discussions. | every 5 min | Supporting |
| Codex release notes | Efficiency changes that have come before make-good resets. | every 5 min | Supporting |
| Visitor reports on this site | A sense of propagation timing only. | live | Never classifying |
How a post becomes evidence
Three stages, each with its own colour. An event can stop at any of them and stay there.
Announced
A post names a reset, scheduled or in progress. We capture the text, hash it, and store our own copy within minutes.
Shown as possible or announced until completion is confirmed.
Scope confirmed
The wording says who it covers: all paid subscriptions, all users, or a named plan. Without that sentence the event stays “scope unverified” forever.
This is the stage that earns a scope tag: Everyone, Plus only, Pro only or Unknown.
Propagation verified
A public completion post states that the reset has happened. Visitor reports are not a substitute for that source.
A confirmation alert cites the public announcement that says the reset went out. It does not claim that every account changed at the same instant.
What never counts
- Screenshots without a live link, and quotes we cannot resolve to a post.
- Deleted posts we did not capture ourselves before deletion.
- Reddit, Discord, Hacker News and forum reports, however consistent.
- The 5-hour and weekly resets your plan already gives you, arriving on schedule.
- Banked credits, for the reset clock.
- Plan or pricing changes, unless they change an allowance.
- Anything passed on second-hand, however senior the person.
When sources disagree
The narrower statement wins. If one post says “everyone” and a reply says “Pro first”, the event is recorded as Pro with a note, not as everyone.
If a post is edited or deleted after capture, the archived copy stands as the basis of the classification and the evidence page raises a red notice.
If a classification turns out to be wrong, it is corrected in place and the correction stays in the history record. A cancelled alert’s replacement requires review.