This was an outage-compensation event. The source announcement is the authority for who was covered and whether the reset was automatic.
The announcement: “Hi. Over the last 24 hours we had three separate small incidents that affected C…”
Reading the announcement: the 48-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-06-04 00:25 UTC (Beijing 2026-06-04 08:25, Thursday) |
| Type | Outage Compensation Reset (reset_type: regular) |
| Sequence | #23 of 70 tracked resets |
| Gap before | 3 days |
| Gap after | 14 days (next reset: 2026-06-18) |
| Running average at that time | 11.8 days (mean of the prior 21 gaps) |
| Where this gap sits in history | longer than 18% of historical gaps (ranked #16 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-06-04 00:25 UTCThe Codex team posted a reset-related announcement; scope follows the source.
-
Original announcement
“Hi. Over the last 24 hours we had three separate small incidents that affected Codex reliability. Those are three too many and we are taking active steps for them to not reproduce. I have reset usage limits for Codex across all paid plans. May the tokens flow again.”— @thsottiaux on X ↗
-
EffectThe event applied to the scope named by the announcement; verify it in your Usage Dashboard.
The era: Spring tuning eraCONTEXT
This segment records an accounting bug that drained limits, several small incidents and announcements describing double resets. Cause and scope still need to be read event by event.
In the full sequence, this is event #4 of 8 in the "Spring tuning era"; 14 days later, the next reset landed on schedule on 2026-06-18. Announced on a Thursday, 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 June 4, 2026 (Thursday)?
On June 4, 2026 (Thursday), the Codex team posted a outage compensation reset announcement — event #23 of 70 in the archive, 3 days after the previous one, part of the "Spring tuning era". detected source scope: all_paid; 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-06-18, 14 days later. That is hindsight, not a forecast that was available at the time.