Codex desk · reset confirmed · Codex · Policy

Some Pro 500 accounts missed the global reset

Tibo admits the 10am rollout did not propagate perfectly. Some Pro 500 accounts missed it; investigation and make-up remain unresolved.

RECEIPT · @thsottiaux · posted 26 Sep 2026 · 21:41 UTC · captured 26 Sep 2026

@giadotai Sorry Gia. More resets coming next week

Open on X ↗

Also on file: 6 more posts

• @giadotai · 26 Sep 2026 The reset came right after my own reset, couldn’t be worse timing.
• @thsottiaux · 1 Oct 2026 Because usage on your primary dot is virtually unlimited at the moment, I can’t really give a reset. I need to come up with something new fast.
• @thsottiaux · 2 Oct 2026 Global reset landing tomorrow 10am PST for all paid ChatGPT accounts. Apologies for the slow start with GPT-6.1 Sol, it's now back to running at expected speeds after the massive load spike in the first two days.
• @thsottiaux · 2 Oct 2026 Reset all propagated. Enjoy.
• @thsottiaux · 3 Oct 2026 Seeing some reports that the Pro 500 didn’t get the reset as expected earlier. Investigating and will make up for it
• @thsottiaux · 3 Oct 2026 @_architected Yeah no, that was my bad for not propagating it at 10am quite perfectly. This is something that will be better planned next time, apologies.

“That was my bad for not propagating it at 10am quite perfectly.”

Tibo admits the 10am global reset did not propagate perfectly. Some Pro 500 accounts missed it; investigation and promised make-up remain unresolved.

Update, October 3 at 05:04 UTC: X syndication verifies Tibo’s complete 04:28:21 UTC reply admitting that he did not propagate the reset perfectly at 10am. He apologizes and says it will be better planned next time. This confirms a rollout miss but does not resolve the reported Pro 500 exception or identify affected count, cause, mechanics or make-up remedy.

Update, October 3 at 04:04 UTC: X syndication verifies Tibo’s complete 04:01:28 UTC post reporting that some Pro 500 accounts did not get the reset as expected. He says he is investigating and will make up for it. This qualifies the earlier all-propagated statement but does not establish affected count, cause, reset mechanics or remedy. Keep the global reset confirmed while marking Pro 500 delivery incomplete.

Update, October 2 at 21:56 UTC: X syndication verifies Tibo’s complete 21:18:48 UTC post, ‘Reset all propagated. Enjoy.’ It quotes the October 2 announcement for all paid ChatGPT accounts, tying completion to that scope. This advances the signal from announced to confirmed. The post still does not identify full versus banked mechanics or affected usage windows.

Update, October 2 at 18:52 UTC: the stated 10am PST time has passed without a provider completion statement. Tibo’s recent feed contains no newer reset delivery post. Loic reports no reset at 2pm and calls it banked; those are community observations, not provider confirmation of delivery or mechanics. The signal remains announced, not confirmed.

Update, October 2 at 02:41 UTC: X syndication verifies Tibo’s complete original statement, author and 02:14:51 UTC posting time. The post was made October 1 at 7:14pm PST, making “tomorrow” October 2. It explicitly names 10am PST and all paid ChatGPT accounts. We advance the signal from watch to announced.

Tibo also says GPT-6.1 Sol is back to expected speeds after a massive load spike during its first two days. That speed recovery is separate from reset delivery and does not prove any account has reset.

The announcement does not identify full versus banked mechanics, affected usage windows, whether every ChatGPT product allowance changes, or completion. Confirmed reset history, calendar and subscriber feed remain unchanged until delivery is verified.

Update, October 1 at 15:36 UTC: X syndication verifies Tibo’s complete original statement, author and 14:51:54 UTC posting time. The post does not name a replacement benefit or renew the earlier reset commitment. We therefore downgrade the forward-looking signal from Strong to watch.

Loic replied asking for a banked reset and claiming usage was cut in half. That is community input, not provider confirmation of a reset, usage reduction or replacement plan.

Reviewed September 26 at 22:38 UTC: X syndication verifies the complete original reply, author, posting time and parent relationship. The parent is Gia’s comment about receiving the reset just after her own reset, quoting Tibo’s earlier completion statement. That community context is not evidence of future eligibility or mechanics.

This is a separate Strong signal from the September 26 reset whose propagation Tibo already confirmed. The new reply does not say whether future resets will be automatic or banked, which usage windows will change, how many resets there will be, or who will receive them.

“Next week” is retained as the provider’s wording. We do not convert it into an exact date, timezone, countdown or probability. This developing story stays outside confirmed reset history, calendars and subscriber feeds.

The updated layered spotlight has an October 4 editorial review window. That visibility setting is not a provider delivery deadline.

Public timeline access remains limited and recent discovery feeds cannot guarantee complete reply coverage. The earlier September 23–26 editorial gap remains recorded.