This was an outage-compensation event. The source announcement is the authority for who was covered and whether the reset was automatic.
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 (Beijing 2026-07-26 03:17, Sunday) |
| Type | Outage Compensation Reset (reset_type: regular) |
| Sequence | #37 of 70 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 Codex team posted a reset-related announcement; scope follows the source.
-
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 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 #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 events respond to an incident or usage-accounting problem. Eligibility and action must be read from that event's announcement.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 Codex team posted a outage compensation reset announcement — event #37 of 70 in the archive, 4 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-28, 2 days later. That is hindsight, not a forecast that was available at the time.