This was an outage-compensation reset: Codex had an incident or usage-accounting anomaly, and the team refilled everyone while fixing it. Nothing to claim — quotas refill automatically once the announcement lands.
The announcement: “We are giving all Codex users a usage reset on the house. Should be showing in y…”
Reading the announcement: 45 words, posted in the evening, plainly worded — set beside its neighbors, the continuity of the "Spring tuning era" voice comes through.
Quick factsTHE SNAPSHOT
| Item | Data |
|---|---|
| Announced | 2026-06-26 23:39 UTC (31:39 Beijing, Friday) |
| Type | Outage Compensation Reset (reset_type: regular) |
| Sequence | #25 of 53 tracked resets |
| Gap before | 9 days |
| Gap after | 2 days (next reset: 2026-06-28) |
| Running average at that time | 11.8 days (mean of the prior 23 gaps) |
| Where this gap sits in history | longer than 63% of historical gaps (ranked #9 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-06-26 23:39 UTCThe official global-reset announcement went out.
-
Original announcement
“We are giving all Codex users a usage reset on the house. Should be showing in your accounts in the next few hours. We have applied some mitigations, but our investigation hasn't shown users being impacted at large. We are continuing to monitor the situation. https://t.co/rLJrQdI1ks”— @thsottiaux on X ↗
-
EffectThe reset propagated across all paid accounts and quotas were refilled.
The era: Spring tuning eraCONTEXT
The cadence slowed while the causes got finer: an accounting bug draining limits, three stacked incidents, two "sneaky" double resets. The team was calibrating when to compensate and how much.
In the full sequence, this is event #6 of 8 in the "Spring tuning era"; 2 days later, the next reset landed on schedule on 2026-06-28. Announced on a Friday, 9 days after its predecessor — those numbers together are this event's coordinates on the timeline.
What it means for youTAKEAWAY
Compensation resets treat all paid users equally — even unaffected accounts get the refill. The announcement usually explains what broke.At 9 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 26, 2026 (Friday)?
On June 26, 2026 (Friday), the OpenAI Codex team announced a outage compensation reset — reset #25 of 53 in the archive, 9 days after the previous one, part of the "Spring tuning era". Usage across all paid plans (Plus / Pro / Business) was wiped and refilled automatically.
What was being compensated?
Judging by the announcement, this was a post-incident compensation: the team refilled every paid account while fixing the problem, even for users who were never affected. Historically, outage compensation is second only to milestone celebrations as a reset trigger.
When was the next global reset after this one?
The archive has the exact answer: the next reset landed on 2026-06-28, 2 days later. That's the unique value of these event pages — the "what happened next" that people at the time couldn't know. For the future, use the homepage radar's projection instead.