Users noticed limits draining faster than expected; the team root-caused it to an accounting bug, fixed it, and refunded the difference with a global reset.
Quick factsTHE SNAPSHOT
| Item | Data |
|---|---|
| Announced | 2026-05-23 20:14 UTC (28:14 Beijing, Saturday) |
| Type | Outage Compensation Reset (reset_type: regular) |
| Sequence | #21 of 53 tracked resets |
| Gap before | 7 days |
| Gap after | 8 days (next reset: 2026-05-31) |
| Running average at that time | 12.4 days (mean of the prior 19 gaps) |
| Where this gap sits in history | longer than 45% of historical gaps (ranked #8 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-05-23 20:14 UTCThe official global-reset announcement went out.
-
Original announcement
“Some of you noticed limits drained faster in Codex, we root caused it to an optimization that we rolled back that had an impact on cache hit rates when compacting across long running sessions. We fixed this and have now reset usage limits for all accounts. Enjoy the weekend. https://t.co/t1O8jCd4PB”— @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 #2 of 8 in the "Spring tuning era"; 8 days later, the next reset landed on schedule on 2026-05-31. Announced on a Saturday, 7 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 7 days, the gap was close to the historical norm — a routine move inside the rhythm.
FAQCOMMON QUESTIONS
What was the Codex global reset on May 23, 2026 (Saturday)?
On May 23, 2026 (Saturday), the OpenAI Codex team announced a outage compensation reset — reset #21 of 53 in the archive, 7 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-05-31, 8 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.