This was an outage-compensation event. The source announcement is the authority for who was covered and whether the reset was automatic.
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 (Beijing 2026-03-10 11:51, Tuesday) |
| Type | Outage Compensation Reset (reset_type: regular) |
| Sequence | #11 of 70 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 Codex team posted a reset-related announcement; scope follows the source.
-
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 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 #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 events respond to an incident or usage-accounting problem. Eligibility and action must be read from that event's announcement.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 Codex team posted a outage compensation reset announcement — event #11 of 70 in the archive, 2 days after the previous one, part of the "March incident cluster". the source does not state account scope; 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-11, 1 day later. That is hindsight, not a forecast that was available at the time.