This was an outage-compensation event. The source announcement is the authority for who was covered and whether the reset was automatic.
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 (Beijing 2026-03-08 10:42, Sunday) |
| Type | Outage Compensation Reset (reset_type: regular) |
| Sequence | #10 of 70 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 Codex team posted a reset-related announcement; scope follows the source.
-
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 event applied to the scope named by the announcement; verify it in your Usage Dashboard.
The era: March incident clusterCONTEXT
Early March 2026 is an incident-dense segment of the archive: several events within nine days cited failed requests, usage-accounting anomalies and fix verification. That describes the period; it is not a promise that every incident produces a reset.
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 events respond to an incident or usage-accounting problem. Eligibility and action must be read from that event's announcement.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 Codex team posted a outage compensation reset announcement — event #10 of 70 in the archive, 3 days after the previous one, part of the "March incident cluster". detected source scope: plus / pro; 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-03-10, 2 days later. That is hindsight, not a forecast that was available at the time.