This was an outage-compensation event. The source announcement is the authority for who was covered and whether the reset was automatic.
The announcement: “Good Sunday. Reset has been propagated to accounts and we landed some fixes to u…”
Reading the announcement: the 37-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-08-24 00:46 UTC (Beijing 2026-08-24 08:46, Monday) |
| Type | Outage Compensation Reset (reset_type: regular) |
| Sequence | #45 of 70 tracked resets |
| Gap before | 3 days |
| Gap after | 2 days (next reset: 2026-08-25) |
| Running average at that time | 7.8 days (mean of the prior 43 gaps) |
| Where this gap sits in history | longer than 39% of historical gaps (ranked #23 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-08-24 00:46 UTCThe Codex team posted a reset-related announcement; scope follows the source.
-
Original announcement
“Good Sunday. Reset has been propagated to accounts and we landed some fixes to usage for things mentioned yesterday as issues we found. You should feel a positive difference. More to come tomorrow and will keep communicating. https://t.co/6mgUetJnhg”— @thsottiaux on X ↗
-
EffectThe event applied to the scope named by the announcement; verify it in your Usage Dashboard.
The era: Milestones & banked creditsCONTEXT
This segment records the 20M and 25M user milestones, an August 21 banked-reset grant and several celebration events near month-end. The record alone does not establish a future launch cadence or an unstated official intention.
In the full sequence, this is event #2 of 6 in the "Milestones & banked credits"; 2 days later, the next reset landed on schedule on 2026-08-25. Announced on a Monday, 3 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 3 days, the gap was close to the historical norm — a routine move inside the rhythm.
FAQCOMMON QUESTIONS
What was the Codex global reset on August 24, 2026 (Monday)?
On August 24, 2026 (Monday), the Codex team posted a outage compensation reset announcement — event #45 of 70 in the archive, 3 days after the previous one, part of the "Milestones & banked credits". the source does not state account scope; 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-08-25, 2 days later. That is hindsight, not a forecast that was available at the time.