This was classified as a routine reset event. The original announcement determines which plans were covered and whether it applied automatically.
The announcement: “Introducing... another usage limit reset for all our ChatGPT Work and Codex user…”
Reading the announcement: gratitude and celebration set the tone of these 46 words, posted in the afternoon — wrapping a reset as community goodwill is the team's consistent register.
Quick factsTHE SNAPSHOT
| Item | Data |
|---|---|
| Announced | 2026-07-11 05:54 UTC (Beijing 2026-07-11 13:54, Saturday) |
| Type | Global Usage Reset (reset_type: regular) |
| Sequence | #30 of 70 tracked resets |
| Gap before | 0 days |
| Gap after | 2 days (next reset: 2026-07-12) |
| Running average at that time | 10.2 days (mean of the prior 28 gaps) |
| Where this gap sits in history | longer than 0% of historical gaps (ranked #29 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-07-11 05:54 UTCThe Codex team posted a reset-related announcement; scope follows the source.
-
Original announcement
“Introducing... another usage limit reset for all our ChatGPT Work and Codex users. Should land over next 30 minutes. Hope you have an awesome weekend. Thank you for pushing our systems to the absolute limit, we have never seen traffic increase so quickly. Keep the feedback https://t.co/WOd7fr2viS”— @thsottiaux on X ↗
-
EffectThe event applied to the scope named by the announcement; verify it in your Usage Dashboard.
The era: July reset spreeCONTEXT
This is the archive's densest three-week segment: more than ten public records, a temporary removal of the five-hour limit, announced user growth from 7M to 10M, and a banked-reset grant to 500k users. That density should not be extrapolated into a future cadence.
In the full sequence, this is event #3 of 12 in the "July reset spree"; 2 days later, the next reset landed on schedule on 2026-07-12. Announced on a Saturday, 0 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.With a very short gap, this sits squarely in a streak — burning quota in such periods had the highest odds of being refilled in the whole archive.
FAQCOMMON QUESTIONS
What was the Codex global reset on July 11, 2026 (Saturday)?
On July 11, 2026 (Saturday), the Codex team posted a global usage reset announcement — event #30 of 70 in the archive, 0 days after the previous one, part of the "July reset spree". detected source scope: all_paid / work; eligibility and required action follow the linked source and Usage Dashboard.
Only 0 days after the previous one — are back-to-back resets normal?
Yes. The archive shows several such streaks (this event's era, the "July reset spree", alone holds 12 events), typically tied to milestones, launch weeks or incident wrap-ups. Streak periods are also when the radar's SEND-IT advice appears most often.
When was the next global reset after this one?
The archive has the historical answer: the next record landed on 2026-07-12, 2 days later. That is hindsight, not a forecast that was available at the time.