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: “We have reset usage limits for all Codex and ChatGPT Work users. Last night arou…”
Reading the announcement: the 39-word notice follows the classic incident structure — status, fix, compensation — a template that hardened after the March 2026 cluster.
Quick factsTHE SNAPSHOT
| Item | Data |
|---|---|
| Announced | 2026-07-25 19:17 UTC (27:17 Beijing, Saturday) |
| Type | Outage Compensation Reset (reset_type: regular) |
| Sequence | #37 of 53 tracked resets |
| Gap before | 4 days |
| Gap after | 2 days (next reset: 2026-07-28) |
| Running average at that time | 8.7 days (mean of the prior 35 gaps) |
| Where this gap sits in history | longer than 44% of historical gaps (ranked #18 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-07-25 19:17 UTCThe official global-reset announcement went out.
-
Original announcement
“We have reset usage limits for all Codex and ChatGPT Work users. Last night around 2am to 4am we suffered an almost global outage. All well and recovered, but you know what comes next. We learn. We reset. Enjoy. https://t.co/rAPzefTyaa”— @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 #10 of 12 in the "July reset spree"; 2 days later, the next reset landed on schedule on 2026-07-28. Announced on a Saturday, 4 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.At 4 days, the gap was close to the historical norm — a routine move inside the rhythm.
FAQCOMMON QUESTIONS
What was the Codex global reset on July 25, 2026 (Saturday)?
On July 25, 2026 (Saturday), the OpenAI Codex team announced a outage compensation reset — reset #37 of 53 in the archive, 4 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-28, 2 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.