❯ EVENT HISTORY
Recent Codex reset history
Official reset announcements with dates and original sources. Global usage resets and saved banked resets are listed separately.
Recent official events
Times below are UTC and describe when the official notice was published, not the exact instant every account changed.
- 11 October 2026, 04:01 UTC — official global reset completion. The completion reply says propagation is complete and links to the earlier global-reset promise. This is a broad announcement, not proof of receipt in every account. Completion source · Earlier promise.
- 7–8 October 2026 — separate banked reset delivery. A saved-reset grant was announced on October 7 at 19:19 UTC; its linked completion followed on October 8 at 03:44 UTC. These are two updates about a banked grant, not two global usage resets. Sources and how banked resets work.
- 7 October 2026, 03:35 UTC — official reset completion. The official announcement says the reset was processed after the community vote. Completion source.
- 2 October 2026, 21:18 UTC — official propagation notice. A completion post followed the scheduled global reset for paid ChatGPT accounts. Completion source · Earlier schedule. A later official reply reported Pro 500 delivery issues under investigation; this broad announcement does not prove every account received it. Account-delivery caveat.
- 8 September 2026, 04:05 UTC — global reset confirmed. The official completion reply followed the earlier global-reset announcement. Completion source · Earlier announcement.
- 3–4 September 2026, Pacific Time — banked reset offers. These were saved resets for eligible accounts, not automatic global resets. Multiple announcement updates do not establish additional grants. Eligibility and how to use a banked reset.
This is a dated editorial summary. Check the live dashboard for newer observations.
Not every report is an event
Public posts can be early clues, but an individual user seeing capacity return does not establish a global reset. Likewise, a service incident may explain reduced availability without indicating that usage capacity has changed.
What enters the history
A candidate event is held briefly while direct public evidence is checked. Only confirmed events are used by the history, chart, and subscription flow. Later corrections can retract a still-pending candidate so it does not become a false historical data point.
Why this improves the forecast
- Fewer false events means less distorted interval statistics.
- Clear boundaries make the public chart easier to interpret.
- Notifications remain tied to confirmed changes rather than speculation.