Tibo's Day 23 | Usage reset has landed
Tibo confirmed the Day 23 reset was done on October 28 at 06:29:38 UTC. The article preserves the earlier midnight PST estimate and explains how to check your own allowance.
On this pageCollapse
The Day 23 usage reset has landed. Tibo quoted his earlier timing reply and confirmed completion on October 28 at 06:29:38 UTC. That is the public confirmation time; he did not give the exact backend execution time.
Earlier, Tibo’s Day 23 post called it a reset day, and his follow-up said it would land by midnight PST.
The earlier midnight PST estimate
The announcement was posted on October 28 at 02:42:53 UTC and the reply at 02:43:38 UTC. It was still the evening of October 27 in Pacific time, so the series calendar files Day 23 under October 27 and interprets midnight as the end of that day.
| Interpretation | Estimated deadline in UTC | Beijing / Taipei (UTC+8) |
|---|---|---|
| Literal PST (UTC−8), used by the earlier countdown | October 28, 08:00 | October 28, 16:00 |
| If local PDT (UTC−7) was intended | October 28, 07:00 | October 28, 15:00 |
“By midnight” was a deadline, not an exact execution time. Tibo has since confirmed completion, so the countdown has ended; the table preserves the earlier estimate.
What is known about the reset?
The announcement and confirmation do not specify eligible plans, usage windows or a banked-reset option. One reply says the reset had not appeared for that user; this is an individual report that CRW has not independently verified. Check your own usage dashboard; the usage guide explains how to compare the displayed windows. The earlier Day 21 account observation remains a separate event in history.
Tibo’s opening jokes about iCloud Mail and Calendar before identifying the day as a reset. The quoted ChatGPT announcement separately says those plugins are available on all ChatGPT plans on web, desktop and iOS. CRW classifies Day 23 as a reset day rather than counting the quoted announcement as another Day 23 feature.
Tibo also mentioned good news tomorrow without specifying what it would be.
Sources & corrections
Published UTC
