This was an outage-compensation reset: Codex had an incident or usage-accounting anomaly, and the team refilled everyone while fixing it. Nothing to claim — quotas refill automatically once the announcement lands.
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 (11:28 Beijing, Saturday) |
| Type | Outage Compensation Reset (reset_type: regular) |
| Sequence | #35 of 53 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 official global-reset announcement went out.
-
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 reset propagated across all paid accounts and quotas were refilled.
The era: July reset spreeCONTEXT
The wildest three weeks in the archive: ten-plus resets back to back, the 5-hour cap temporarily removed, users climbing from 7M to 10M, and the first 500k banked-reset grants. This era cemented the "a reset can land anytime" consensus.
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 resets treat all paid users equally — even unaffected accounts get the refill. The announcement usually explains what broke.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 OpenAI Codex team announced a outage compensation reset — reset #35 of 53 in the archive, 2 days after the previous one, part of the "July reset spree". Usage across all paid plans (Plus / Pro / Business) was wiped and refilled automatically.
What was being compensated?
Judging by the announcement, this was a post-incident compensation: the team refilled every paid account while fixing the problem, even for users who were never affected. Historically, outage compensation is second only to milestone celebrations as a reset trigger.
When was the next global reset after this one?
The archive has the exact answer: the next reset landed on 2026-07-21, 4 days later. That's the unique value of these event pages — the "what happened next" that people at the time couldn't know. For the future, use the homepage radar's projection instead.