This was an outage-compensation event. The source announcement is the authority for who was covered and whether the reset was automatic.
The announcement: “As we are still investigating, I have reset everyone's Codex usage limits. This …”
Reading the announcement: gratitude and celebration set the tone of these 50 words, posted in the morning — wrapping a reset as community goodwill is the team's consistent register.
Quick factsTHE SNAPSHOT
| Item | Data |
|---|---|
| Announced | 2026-06-28 23:54 UTC (Beijing 2026-06-29 07:54, Monday) |
| Type | Outage Compensation Reset (reset_type: regular) |
| Sequence | #26 of 70 tracked resets |
| Gap before | 2 days |
| Gap after | 1 days (next reset: 2026-06-29) |
| Running average at that time | 11.4 days (mean of the prior 24 gaps) |
| Where this gap sits in history | longer than 4% of historical gaps (ranked #21 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-06-28 23:54 UTCThe Codex team posted a reset-related announcement; scope follows the source.
-
Original announcement
“As we are still investigating, I have reset everyone's Codex usage limits. This is a hard reset given some users had stacked up to three banked resets already that they can apply on their own schedule. Funnily enough, this week at OpenAI is called the RESET week, which is meant https://t.co/UdCSbW03QU”— @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 #7 of 8 in the "Spring tuning era"; 1 day later, the next reset landed on schedule on 2026-06-29. Announced on a Sunday, 2 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.With a very short gap, this sits squarely in a streak — burning quota in such periods had the highest odds of being refilled in the whole archive.
FAQCOMMON QUESTIONS
What was the Codex global reset on June 28, 2026 (Sunday)?
On June 28, 2026 (Sunday), the Codex team posted a outage compensation reset announcement — event #26 of 70 in the archive, 2 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-29, 1 day later. That is hindsight, not a forecast that was available at the time.