September 2026
October 2026
Reset records
Events: 67Swipe sideways for the full table →
| Date | Type | Applies to | Reason | Source |
|---|---|---|---|---|
| 10-2606:14 | Usage reset | All users | Tibo's 28-day challenge | |
| ||||
| 10-2506:06 | Usage reset | All users | Tibo's 28-day challenge | |
| ||||
| 10-2317:00 | Usage reset | All users | Tibo's 28-day challenge | |
| ||||
| 10-2217:00 | Usage reset | All users | Tibo's 28-day challenge | |
| 10-2006:33 | Usage reset | All users | Tibo's 28-day challenge | |
| ||||
| 10-1721:12 | Usage reset | All users | Tibo's 28-day challenge | |
| ||||
| 10-1506:28 | Usage reset | All users | Tibo's 28-day challenge | |
| ||||
| 10-1305:06 | Usage reset | All users | Tibo's 28-day challenge | |
| ||||
| 10-1104:01 | Usage reset | All users | Tibo's 28-day challenge | |
| ||||
| 10-0800:36 | Banked reset | All users | MilestoneActive users of Codex and ChatGPT Work hit a record 40 million | |
| 10-0703:35 | Usage reset | All users | Tibo's 28-day challenge | |
| ||||
| 10-0221:15 | Usage reset | Paid users | FixApology for GPT-6.1 Sol's slow start after a massive load spike | |
| 09-2919:00 | Banked reset | Not specified | New modelDevDay: Dots and GPT-6.1 Sol launch | |
| ||||
| 09-2618:17 | Usage reset | Paid users | FixApology for the brief disruption | |
| ||||
| 09-2218:23 | Banked reset | Paid users | New modelGPT-6 Sol and Luna launch | |
| ||||
| 09-1208:09 | Usage reset | All users | FixQuality issues after the Astra launch | |
| ||||
| 09-0801:56 | Usage reset | All users | New modelAstra launch | |
| ||||
| 09-0500:39 | Banked reset | Paid users | New modelAstra rolled out early | |
| ||||
| 09-0323:12 | Banked reset | Some usersPaid users without Astra access | CompensationNo Astra access yet | |
| ||||
| 08-3102:29 | Usage reset | Paid users | Milestone25M active users | |
| ||||
| 08-2920:43 | Usage reset | Paid users | FixUsage-limit issues | |
| ||||
| 08-2716:35 | Usage reset | All users | Unstated | |
| ||||
| 08-2400:46 | Usage reset | Not specified | FixUsage issues | |
| 08-2111:43 | Banked reset | Paid users | Milestone20M active users | |
| ||||
| 08-1301:01 | Usage reset | All users | Milestone15M users | |
| ||||
| 08-1100:27 | Usage reset | Not specified | Unstated | |
| ||||
| 08-0820:29 | Usage reset | Paid users | New modelGPT-5.6 Sol available everywhere | |
| ||||
| 08-0103:32 | Usage reset | All users | WeekendCelebrating an efficient week | |
| ||||
| 07-2904:09 | Usage reset | All users | FixSol usage draining too fast | |
| ||||
| 07-2803:09 | Usage reset | Paid users | Unstated | |
| ||||
| 07-2519:17 | Usage reset | All users | FixNear-global outage overnight | |
| ||||
| 07-2116:47 | Usage reset | Paid users | Milestone10M users | |
| ||||
| 07-1803:28 | Usage reset | Paid users | Weekend | |
| ||||
| 07-1604:14 | Usage reset | All users | Milestone9M active users | |
| ||||
| 07-1419:34 | Usage reset | All users | Milestone8M active users | |
| ||||
| 07-1318:29 | Usage reset | All users | Milestone7M active users | |
| ||||
| 07-1221:28 | Usage reset | Some usersUsers whose reset card failed | FixReset cards did not apply | |
| ||||
| 07-1105:54 | Usage reset | All users | New modelGPT-5.6 Sol launch (second of two) | |
| ||||
| 07-1017:59 | Usage reset | All users | New modelGPT-5.6 Sol launch (first of two) | |
| ||||
| 07-0921:24 | Usage reset | All users | Unstated | |
| ||||
| 06-2923:39 | Usage reset | All users | FixUsage draining too fast | |
| ||||
| 06-2823:54 | Usage reset | All users | FixUsage issue investigation | |
| ||||
| 06-2623:39 | Usage reset | All users | FixUsage draining too fast | |
| ||||
| 06-1800:10 | Usage reset | All users | FixUsage issues | |
| ||||
| 06-0400:25 | Usage reset | Paid users | FixThree small incidents in 24 hours | |
| ||||
| 05-3115:25 | Usage reset | Paid users | Milestone5M users | |
| ||||
| 05-2320:14 | Usage reset | All users | FixCompaction cache regression rolled back | |
| ||||
| 05-1617:51 | Usage reset | Paid users | Weekend | |
| ||||
| 04-2805:28 | Usage reset | Paid users | MilestoneCelebrating a good week | |
| ||||
| 04-2023:15 | Usage reset | All users | Fix10-minute service outage | |
| ||||
| 04-1700:58 | Usage reset | All users | MilestoneCodex first anniversary | |
| ||||
| 04-0917:51 | Usage reset | All users | MilestoneSecond 3M celebration, $100 plan launch | |
| ||||
| 04-0723:13 | Usage reset | All users | Milestone3M weekly users | |
| ||||
| 04-0107:48 | Usage reset | All users | FixMore users hitting usage limits | |
| ||||
| 03-2701:52 | Usage reset | All users | New productPlugins launch | |
| ||||
| 03-1105:38 | Usage reset | All users | FixCodex stable again | |
| ||||
| 03-1003:51 | Usage reset | All users | FixIncident fully resolved | |
| ||||
| 03-0802:42 | Usage reset | Paid users | FixUsage draining too fast | |
| ||||
| 03-0421:30 | Usage reset | Paid users | FixDouble limits missing for some users | |
| ||||
| 03-0301:50 | Usage reset | All users | FixRequests wrongly blocked as high risk | |
| ||||
| 2025-12-2508:01 | Usage reset | All users | MilestoneHoliday gift, limits doubled until Jan 1 | |
| ||||
| 2025-12-1922:01 | Usage reset | All users | FixUsage tracking system rewritten | |
| ||||
| 2025-12-1702:18 | Usage reset | All users | FixService disruption | |
| ||||
| 2025-12-0222:49 | Usage reset | All users | FixUsage issues | |
| ||||
| 2025-11-2223:13 | Usage reset | All users | FixHigh latency near the US | |
| ||||
| 2025-11-0520:19 | Usage reset | All users | Fix45-minute outage resolved | |
| ||||
| 2025-09-1704:02 | Usage reset | All users | New modelGPT-5-Codex launch, also making up for slowdowns | |
| ||||
Codex resets are announced by Tibo, who leads Codex at OpenAI, on his own X account. Historically they follow outages and usage bugs, model launches and user milestones; since mid-2026 some arrive as banked resets you use yourself. This site records each announcement as one event, tags its type, scope and reason, and links the original posts.
FAQ
Did Codex reset today?
Look for a row dated today: if there is one, a reset happened. Then check its type. A usage reset clears your usage right away; a banked reset is credited to your account and only takes effect when you use it on the usage page. The headline counts time since the latest record of either type. Each record links Tibo’s original post. For your own reset times, check chatgpt.com/codex/settings/usage or /status in the CLI.
Codex announced a reset, so why didn’t my limit reset?
Open the original post on the record and check which kind it was: a usage reset applies directly, while a banked reset only clears your usage once you use it on the usage page. Then refresh the usage page, which can lag. Also make sure you are signed in to the account and workspace that received it. If it still has not changed, contact OpenAI support: they do not reset limits by hand, but they do check whether a reset was applied.
Is a “reset” here the same as the countdown in my account?
No. Your account's 5-hour and weekly limits reset on their own schedule. This site only records the extra, officially announced one-off usage resets and the banked resets handed out. An announcement time is not your account's reset time.
What is the difference between a usage reset and a banked reset?
A usage reset applies directly: the limits of the users covered by the announcement clear at once. A banked reset (once called a reset card) is credited to an eligible account and takes effect only when you use it.
How do I use a Codex banked reset?
Open chatgpt.com/codex/settings/usage and use it from the row that shows an available reset; /usage in the CLI works too. One use refreshes both the 5-hour limit and the weekly limit, and the next weekly reset is 7 days after the first message you send afterwards, so send one right away. Banked resets expire: the date is shown in your account, and an expired one is not replaced.
When does my Codex weekly limit reset?
Normally it resets once a week. After a reset (a banked, automatic or purchased one), the new week starts with your first message after the reset, and the next weekly reset is 7 days after that message—not after payment or the reset itself. So send a message soon after a reset, or the next weekly reset comes later. Settings → Usage and /status show your times.
Does Codex still have a 5-hour limit?
It depends on the plan. On July 12, 2026 Codex temporarily removed the 5-hour limit for Plus, Business and Pro; it came back for Plus around August 25. Pro currently has none and is bound only by the weekly limit. Where the limit applies, it resets 5 hours after your first message. Both changes were announced by Tibo on X.
Do Codex and ChatGPT share usage limits?
Not with regular ChatGPT conversations; those are counted separately. What is shared is Codex across its own surfaces: signed in with the same ChatGPT account, the CLI, the IDE extension, the web and ChatGPT Work task execution all draw from one Codex allowance. Usage with an API key is billed separately at API rates.
Codex usage limit reached: what can I do?
First check whether your account holds a banked reset; if it does, use it on the usage page. Otherwise wait for the limit to reset, or buy extra usage on the usage page if your plan offers it. OpenAI support does not reset limits by hand.
Who is Tibo, and what is a Tibo reset?
Tibo is Thibault Sottiaux (@thsottiaux), who leads Codex at OpenAI. Codex usage resets and banked resets are announced from his X account, so the community calls them Tibo resets. This site records his public posts, one event per announcement; to see whether Codex reset today, check the first row of the table on this page.
Where does Codex data come from?
Codex records cover public announcements from Tibo. Each record links to the original post and lists its time, type and scope.
How often do resets happen, and when is the next one?
There is no fixed schedule. The next estimate is based on recent records and time already waited; with limited history it is only a rough estimate. The date may change; it is not an official schedule or your personal usage reset time. Follow announcements from OpenAI.
How do I report a missing reset?
If you find a missing Codex reset announcement, share its original post link in the Telegram group in the reminder panel.
