TL;DRThe archive can be classified into launches, incident compensation, milestones, holidays and system changes. Those labels explain past events; they do not make a new launch or incident a reliable predictor of another reset.
Sources SOURCES
Distilled from public community discussions. This page only breaks them down and verifies — it never reposts the original; opinions belong to their authors.
Facts FACTS
Check these claims against the listed sources. For allowance mechanics, first-party account displays outrank community summaries.
- Launch triggers recur through the archive: the very first reset (2025-09-17) shipped alongside GPT-5-Codex; 2026-04-09 arrived with the $100 tier; model-launch moments have repeatedly carried resets with them.
- Incident compensation shows up at high frequency: the 2025-11-05 outage recovery, the 2025-12-02 billing-system rewrite that trued up the errors, the early-March 2026 incident cluster (several resets inside nine days), and the 2026-05-23 compensation for a stats bug that overcharged.
- Milestones appear in dense runs: 3M (2026-04-07), 7M (2026-07-13), 8M (2026-07-14), 9M, 10M (2026-07-21), 15M, 20M, 25M (2026-08-31).
- Holidays and tributes: the 2025-12-25 Christmas reset and the 2026-04-17 first-anniversary reset. Early July 2026 produced the densest wave on record — multiple resets across roughly three-plus weeks, alongside the temporary removal of the 5-hour limit.
Concepts CONCEPTS
Not everything said in a community thread is a fact — each concept carries its nature label. Read the label first.
Classifying past announcements by launch, incident, milestone, holiday or system change makes the archive easier to browse. It does not establish a future reset probability.
Triggers bunch, so resets bunch: the three July weeks that took users from 7M to 10M saw several resets land back-to-back, while a fortnight with zero triggers can produce zero resets. A drought is not an anomaly — it is part of the shape. Plan against the triggers while quoting the average, and long gaps stop ambushing you.
Some incidents in the archive were followed by compensation, but OpenAI makes no blanket promise that every outage will produce a reset or cover every account.
Takeaways TAKEAWAYS
Launches, milestones and holidays are visible calendar events, while incidents are not. Use the five buckets to interpret old announcements, not to schedule current quota.
A watch signal means the team has posted something relevant but has not necessarily stated a reset time or scope. Keep the account-based plan until an explicit announcement and Usage verification arrive.
The full event-by-event originals sit in our reset-history archive, each tagged with its type and its historical ranking at the time. Worth one slow read to build the intuition yourself — skim it once and the five buckets become reflex.
Keep reading NEXT
Want today's verdict? Back to the live radar.