Tibo confirmed completion: Done and dusted.
Codex Reset History & Tibo Timeline
Explore archived Codex reset events and Tibo updates. Automatic resets and saved reset grants are counted separately, with times shown in your display timezone.
CODEX RESET HISTORY
Codex reset timeline
54 public resets · 10 saved reset grants · Since 2025-09
Recent reset intervals
Day 8 reset; archive account observation precedes Tibo’s completion reply.
Day 6 reset: Tibo reported propagation complete.
40M active-user milestone: saved reset grant for paid accounts.
Community-voted reset in the 28-day challenge.
Reset following the GPT-6.1 Sol rollout difficulties.
Saved reset detected by archive accounts; no Tibo announcement recorded.
Reset following a brief service disruption.
Saved reset with the GPT-6 Sol and Luna launch.
Reset alongside an Astra quality update.
Account observation recorded before Tibo’s reset confirmation.
Saved reset accompanying early Astra availability.
Saved reset compensation for delayed Astra access.
Reset celebrating 25M active users.
Reset alongside fixes affecting Codex usage consumption.
Usage reset announced for Codex and ChatGPT Work.
Quiet reset recorded in account meters; later acknowledged in replies.
Sunday reset after usage-related fixes.
20M active-user milestone: saved reset grant.
Reset celebrating 15M active users.
Completion post for the previously promised Monday reset.
Reset celebrating GPT-5.6 Sol availability.
Reset alongside efficiency work and GPT-5.6 Luna improvements.
Reset amid reports of faster usage consumption with GPT-5.6 Sol.
Paid-account usage reset announced by Tibo.
Reset after the previous night’s widespread outage.
10M-user milestone reset announcement.
Another paid-account reset for Codex and ChatGPT Work.
Reset celebrating 9M active users.
8M-user milestone reset during the GPT-5.6 Sol rollout.
7M active-user milestone: saved reset grant.
Saved resets for 500,000 accounts with expanded redemption access.
Weekend reset announced with a short rollout window.
Reset announced, with another reset mentioned for later that day.
Full usage reset with a roughly one-hour propagation window.
Automatic reset and an additional saved reset after rapid usage drain.
Automatic reset and an additional saved reset after rapid usage drain.
Direct usage reset while an investigation continued.
Reset during mitigation of a Codex usage issue.
Automatic reset plus a saved reset deposited for later.
Automatic reset plus a saved reset deposited for later.
Reset following multiple reliability incidents.
Paid-account weekly and short-window limits refreshed.
Reset after a cache-related optimization caused faster usage drain.
Paid-plan reset ahead of the weekend.
Reset accompanying GPT-5.5 availability.
Reset following mitigation of a brief Codex incident.
Codex first-anniversary reset.
Reset accompanying a new subscription-plan launch.
Reset celebrating 3M weekly Codex users.
Precautionary reset after increased rate-limit reports.
Reset alongside the Codex plugins launch.
Reset after Codex service stabilization.
Reset following resolution of a Codex service issue.
Plus and Pro reset after reports of unusual usage drain.
Compensation after a promotional-limit bug affected some accounts.
Reset after fixing incorrectly blocked requests.
Holiday reset alongside a temporary usage promotion.
Reset during a rewrite of Codex usage accounting.
Reset compensating for a service disruption.
Reset used to mitigate an ongoing Codex issue.
Reset after unusually high latency near the US.
Reset after a service outage.
GPT-5-Codex reset after capacity-related slowdowns.
Base history: codex-reset.com · Cross-check: AI IDE List · CC BY 4.0
One announcement can include a public reset and a saved reset grant; these are counted separately. This timeline does not replace your personal reset schedule.
Source comparison and corrections
Latest event: Tibo’s completion post was published at 2026-10-15 06:28:13 UTC; the third-party account observation was 06:13:01 UTC; the earlier announcement was 04:56:07 UTC. These are distinct timestamps and do not establish when every account received the reset.
Base records are compared individually. Verified original evidence takes priority; otherwise the primary archive is retained. The latest event uses the saved Tibo completion post, with the third-party observation kept separately.15 records differ in timestamp precision or meaning.
2109812360596865224Selected: 2026-10-13 05:03 UTC+0Comparison: 2026-10-13 05:06 UTC+02107913674593644711Selected: 2026-10-07 19:19 UTC+0Comparison: 2026-10-08 03:44 UTC+02105008012525769969Selected: 2026-09-29 18:53 UTC+0Comparison: 2026-09-29 19:00 UTC+02097043464538264003Selected: 2026-09-08 01:34 UTC+0Comparison: 2026-09-08 01:56 UTC+02094252447271366730Selected: 2026-08-31 02:34 UTC+0Comparison: 2026-08-31 02:29 UTC+02092311059197808936Selected: 2026-08-25 14:15 UTC+0Comparison: 2026-08-25 14:30 UTC+0How should you read this timeline?
Announcements, completion confirmations and third-party account observations can have different timestamps. The latest event uses a saved Tibo completion post. It establishes his confirmation time, not when every account received the reset. Older records retain their archive provenance where original evidence is unavailable.
An announcement can include both an automatic reset and a saved reset grant, counted once in each category. Reposts do not create extra resets. Historical median intervals describe recorded events, not a promised next date.
Explore our probability model → · Check my weekly Codex usage →