Early March 2026 started a rough patch: failed requests and usage accounting anomalies kept surfacing, and the team compensated affected users with resets while fixing. This kicked off a cluster of resets in the first ten days of March.
Quick factsTHE SNAPSHOT
| Item | Data |
|---|---|
| Announced | 2026-03-03 01:50 UTC (Beijing 2026-03-03 09:50, Tuesday) |
| Type | Outage Compensation Reset (reset_type: regular) |
| Sequence | #8 of 70 tracked resets |
| Gap before | 68 days |
| Gap after | 2 days (next reset: 2026-03-04) |
| Running average at that time | 23.9 days (mean of the prior 6 gaps) |
| Where this gap sits in history | longer than 86% of historical gaps (ranked #1 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2026-03-03 01:50 UTCThe Codex team posted a reset-related announcement; scope follows the source.
-
Original announcement
“Codex is back up. We introduced an issue that caused requests to be blocked and rejected as high cyber risk. This was fixed in ~8 mins and we are now back online and fully operational. Team will reset rate limits, that’s been a while. Enjoy one on us.”— @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 #1 of 5 in the "March incident cluster"; 2 days later, the next reset landed on schedule on 2026-03-04. Announced on a Tuesday, 68 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.The 68-day gap ran above the then-average, a reminder that long silences can end in either a big compensation or more silence — watching the pressure gauge beats guessing motives.
FAQCOMMON QUESTIONS
What was the Codex global reset on March 3, 2026 (Tuesday)?
On March 3, 2026 (Tuesday), the Codex team posted a outage compensation reset announcement — event #8 of 70 in the archive, 68 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-04, 2 days later. That is hindsight, not a forecast that was available at the time.