This was classified as a routine reset event. The original announcement determines which plans were covered and whether it applied automatically.
The announcement: “The Codex usage limits have been reset for all paid ChatGPT subscriptions. You s…”
Reading the announcement: gratitude and celebration set the tone of these 33 words, posted in the evening — wrapping a reset as community goodwill is the team's consistent register.
Quick factsTHE SNAPSHOT
| Item | Data |
|---|---|
| Announced | 2026-05-31 15:25 UTC (Beijing 2026-05-31 23:25, Sunday) |
| Type | Global Usage Reset (reset_type: regular) |
| Sequence | #22 of 70 tracked resets |
| Gap before | 8 days |
| Gap after | 3 days (next reset: 2026-06-04) |
| Running average at that time | 12.2 days (mean of the prior 20 gaps) |
| Where this gap sits in history | longer than 62% of historical gaps (ranked #8 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-05-31 15:25 UTCThe Codex team posted a reset-related announcement; scope follows the source.
-
Original announcement
“The Codex usage limits have been reset for all paid ChatGPT subscriptions. You should be back to 100% weekly and 100% hourly limits. Let the tokens do incredible things today and have fun. https://t.co/e7iJcJ1iHy”— @thsottiaux on X ↗
-
EffectThe event applied to the scope named by the announcement; verify it in your Usage Dashboard.
The era: Spring tuning eraCONTEXT
This segment records an accounting bug that drained limits, several small incidents and announcements describing double resets. Cause and scope still need to be read event by event.
In the full sequence, this is event #3 of 8 in the "Spring tuning era"; 3 days later, the next reset landed on schedule on 2026-06-04. Announced on a Sunday, 8 days after its predecessor — those numbers together are this event's coordinates on the timeline.
What it means for youTAKEAWAY
Routine resets historically average about 6.9 days apart, but the spread is wide — back-to-back days to two-week gaps. Watching the radar beats counting days.At 8 days, the gap was close to the historical norm — a routine move inside the rhythm.
FAQCOMMON QUESTIONS
What was the Codex global reset on May 31, 2026 (Sunday)?
On May 31, 2026 (Sunday), the Codex team posted a global usage reset announcement — event #22 of 70 in the archive, 8 days after the previous one, part of the "Spring tuning era". detected source scope: all_paid; eligibility and required action follow the linked source and Usage Dashboard.
Do I need to do anything for this event?
Read the linked announcement and your Usage Dashboard. Automatic resets and redeemable banked resets are different; this event's source determines the required action.
When was the next global reset after this one?
The archive has the historical answer: the next record landed on 2026-06-04, 3 days later. That is hindsight, not a forecast that was available at the time.