This was an outage-compensation event. The source announcement is the authority for who was covered and whether the reset was automatic.
The announcement: “Codex incident is mitigated, seeing recovery. Lasted about 10 mins, Codex itself…”
Reading the announcement: the 35-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-04-20 23:15 UTC (Beijing 2026-04-21 07:15, Tuesday) |
| Type | Outage Compensation Reset (reset_type: regular) |
| Sequence | #18 of 70 tracked resets |
| Gap before | 4 days |
| Gap after | 7 days (next reset: 2026-04-28) |
| Running average at that time | 12.7 days (mean of the prior 16 gaps) |
| Where this gap sits in history | longer than 35% of historical gaps (ranked #11 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-04-20 23:15 UTCThe Codex team posted a reset-related announcement; scope follows the source.
-
Original announcement
“Codex incident is mitigated, seeing recovery. Lasted about 10 mins, Codex itself helped with the remediation, but ultimately the insight came from a human this time. Apologies for the disruption and rate limit reset incoming. https://t.co/RiuRnNsH2u https://t.co/efVDAsHrBa”— @thsottiaux on X ↗
-
EffectThe event applied to the scope named by the announcement; verify it in your Usage Dashboard.
The era: Growth eraCONTEXT
Announcements in this period paired reset events with 3M weekly users, the $100 plan launch and Codex's first anniversary. These are documented historical contexts, not evidence that a future milestone will trigger a reset.
In the full sequence, this is event #6 of 7 in the "Growth era"; 7 days later, the next reset landed on schedule on 2026-04-28. Announced on a Monday, 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 April 20, 2026 (Monday)?
On April 20, 2026 (Monday), the Codex team posted a outage compensation reset announcement — event #18 of 70 in the archive, 4 days after the previous one, part of the "Growth era". 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-04-28, 7 days later. That is hindsight, not a forecast that was available at the time.