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: “This codex issue is now fully resolved and stable for the last couple of hours. …”
Reading the announcement: the 35-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-10 03:51 UTC (11:51 Beijing, Tuesday) |
| Type | Outage Compensation Reset (reset_type: regular) |
| Sequence | #11 of 53 tracked resets |
| Gap before | 2 days |
| Gap after | 1 days (next reset: 2026-03-11) |
| Running average at that time | 17.4 days (mean of the prior 9 gaps) |
| Where this gap sits in history | longer than 0% 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-03-10 03:51 UTCThe official global-reset announcement went out.
-
Original announcement
“This codex issue is now fully resolved and stable for the last couple of hours. You have come to expect it, but yes, that means we will be reseting rate limits in a bit. Enjoy. https://t.co/QSCRLGK4kJ”— @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 #4 of 5 in the "March incident cluster"; 1 day later, the next reset landed on schedule on 2026-03-11. Announced on a Tuesday, 2 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.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 March 10, 2026 (Tuesday)?
On March 10, 2026 (Tuesday), the OpenAI Codex team announced a outage compensation reset — reset #11 of 53 in the archive, 2 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-11, 1 day 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.