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 don’t have evidence of a widespread issue with codex usage being drained fast…”
Reading the announcement: the 46-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-03-08 02:42 UTC (10:42 Beijing, Sunday) |
| Type | Outage Compensation Reset (reset_type: regular) |
| Sequence | #10 of 53 tracked resets |
| Gap before | 3 days |
| Gap after | 2 days (next reset: 2026-03-10) |
| Running average at that time | 19.1 days (mean of the prior 8 gaps) |
| Where this gap sits in history | longer than 11% of historical gaps (ranked #7 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-03-08 02:42 UTCThe official global-reset announcement went out.
-
Original announcement
“We don’t have evidence of a widespread issue with codex usage being drained faster than it should but there are enough reports and we have reset rate limits for plus & pro subscriptions while we work towards wrapping up our investigation over the coming 1-3 days. https://t.co/yhr8K8pOjf”— @thsottiaux on X ↗
-
EffectThe reset propagated across all paid accounts and quotas were refilled.
The era: March incident clusterCONTEXT
Early March 2026 was the densest incident window in the archive: multiple resets within nine days, all tied to failed requests, usage-accounting anomalies and fix verification. Resets became the standard incident-response gesture.
In the full sequence, this is event #3 of 5 in the "March incident cluster"; 2 days later, the next reset landed on schedule on 2026-03-10. Announced on a Sunday, 3 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 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 March 8, 2026 (Sunday)?
On March 8, 2026 (Sunday), the OpenAI Codex team announced a outage compensation reset — reset #10 of 53 in the archive, 3 days after the previous one, part of the "March incident cluster". 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-03-10, 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.