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 usage limits will be fully reset again in the next hour and we will credit…”
Reading the announcement: the 50-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-29 23:39 UTC (Beijing 2026-06-30 07:39, Tuesday) |
| Type | Outage Compensation Reset (reset_type: regular) |
| Sequence | #27 of 70 tracked resets |
| Gap before | 1 days |
| Gap after | 10 days (next reset: 2026-07-09) |
| Running average at that time | 11.0 days (mean of the prior 25 gaps) |
| Where this gap sits in history | longer than 0% of historical gaps (ranked #25 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-06-29 23:39 UTCThe Codex team posted a reset-related announcement; scope follows the source.
-
Original announcement
“Codex usage limits will be fully reset again in the next hour and we will credit one additional reset into your bank for your own usage over the next 24 hours. We investigated reports that Codex usage was being consumed faster than expected. There wasn't one central issue, but a https://t.co/UdCSbW0BGs”— @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 #8 of 8 in the "Spring tuning era"; 10 days later, the next reset landed on schedule on 2026-07-09. Announced on a Monday, 1 day 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 29, 2026 (Monday)?
On June 29, 2026 (Monday), the Codex team posted a outage compensation reset announcement — event #27 of 70 in the archive, 1 days after the previous one, part of the "Spring tuning 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-07-09, 10 days later. That is hindsight, not a forecast that was available at the time.