This was an outage-compensation event. The source announcement is the authority for who was covered and whether the reset was automatic.
The announcement: “Oops... I did it again. Enjoy reset usage limits for all paid users for Codex an…”
Reading the announcement: the team's signature playfulness is on full display in these 43 words — a meme-flavored notice that is, underneath, still a formal global refill.
Quick factsTHE SNAPSHOT
| Item | Data |
|---|---|
| Announced | 2026-07-18 03:28 UTC (Beijing 2026-07-18 11:28, Saturday) |
| Type | Outage Compensation Reset (reset_type: regular) |
| Sequence | #35 of 70 tracked resets |
| Gap before | 2 days |
| Gap after | 4 days (next reset: 2026-07-21) |
| Running average at that time | 8.9 days (mean of the prior 33 gaps) |
| Where this gap sits in history | longer than 21% of historical gaps (ranked #22 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-07-18 03:28 UTCThe Codex team posted a reset-related announcement; scope follows the source.
-
Original announcement
“Oops... I did it again. Enjoy reset usage limits for all paid users for Codex and ChatGPT Work. Super grateful for an incredible team who is iterating at lightspeed and keeping the infra up as we scale faster than ever. Enjoy the weekend! https://t.co/WIuS07doKA https://t.co/3NwNqHG7TV”— @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 #8 of 12 in the "July reset spree"; 4 days later, the next reset landed on schedule on 2026-07-21. Announced on a Saturday, 2 days after its predecessor — those numbers together are this event's coordinates on the timeline.
What it means for youTAKEAWAY
Compensation events respond to an incident or usage-accounting problem. Eligibility and action must be read from that event's announcement.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 18, 2026 (Saturday)?
On July 18, 2026 (Saturday), the Codex team posted a outage compensation reset announcement — event #35 of 70 in the archive, 2 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.
What was being compensated?
Judging by the announcement, this was a post-incident compensation. The linked source determines who was covered; this page does not infer unaffected or unnamed accounts.
When was the next global reset after this one?
The archive has the historical answer: the next record landed on 2026-07-21, 4 days later. That is hindsight, not a forecast that was available at the time.