A second reset in a row, with the team confirming the 5-hour cap removal would stay. The reset cadence that week turned "waiting for the reset" into a community meme.
Quick factsTHE SNAPSHOT
| Item | Data |
|---|---|
| Announced | 2026-07-16 04:14 UTC (Beijing 2026-07-16 12:14, Thursday) |
| Type | Milestone Celebration Reset (reset_type: regular) |
| Sequence | #34 of 70 tracked resets |
| Gap before | 1 days |
| Gap after | 2 days (next reset: 2026-07-18) |
| Running average at that time | 9.2 days (mean of the prior 32 gaps) |
| Where this gap sits in history | longer than 3% of historical gaps (ranked #27 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-07-16 04:14 UTCThe Codex team posted a reset-related announcement; scope follows the source.
-
Original announcement
“Another reset for our Codex and ChatGPT Work users. Actually hit 9M active users way earlier today, but then got distracted by the approximately millions of things the team is doing to keep the systems up and reliable. Should have that sweet 100% weekly usage limit back in a few”— @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 #7 of 12 in the "July reset spree"; 2 days later, the next reset landed on schedule on 2026-07-18. Announced on a Thursday, 1 day after its predecessor — those numbers together are this event's coordinates on the timeline.
What it means for youTAKEAWAY
Milestone resets are pure perks with no trigger conditions. Historically nearly every user-count milestone (3M → 25M) came with one.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 16, 2026 (Thursday)?
On July 16, 2026 (Thursday), the Codex team posted a milestone celebration reset announcement — event #34 of 70 in the archive, 1 days after the previous one, part of the "July reset spree". detected source scope: work; eligibility and required action follow the linked source and Usage Dashboard.
Only 1 day 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-18, 2 days later. That is hindsight, not a forecast that was available at the time.