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 have reset the usage limits for everyone in Codex, which helps us mitigate th…”
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 | 2025-12-02 22:49 UTC (Beijing 2025-12-03 06:49, Wednesday) |
| Type | Outage Compensation Reset (reset_type: regular) |
| Sequence | #4 of 70 tracked resets |
| Gap before | 10 days |
| Gap after | 14 days (next reset: 2025-12-17) |
| Running average at that time | 25.7 days (mean of the prior 2 gaps) |
| Where this gap sits in history | longer than 0% of historical gaps (ranked #3 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2025-12-02 22:49 UTCThe Codex team posted a reset-related announcement; scope follows the source.
-
Original announcement
“We have reset the usage limits for everyone in Codex, which helps us mitigate the issue the fastest and the team will continue to work on the underlying cause. This should propagate to all users over the next 10 mins, enjoy and apologies for the confusion! https://t.co/UdHowMWBoz”— @thsottiaux on X ↗
-
EffectThe event applied to the scope named by the announcement; verify it in your Usage Dashboard.
The era: Winter compensation eraCONTEXT
Announcements in this period cited a November outage recovery, usage discrepancies after a billing-system rewrite, and a Christmas thank-you. The recorded causes differ and do not establish a fixed schedule.
In the full sequence, this is event #3 of 6 in the "Winter compensation era"; 14 days later, the next reset landed on schedule on 2025-12-17. Announced on a Tuesday, 10 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 10-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 December 2, 2025 (Tuesday)?
On December 2, 2025 (Tuesday), the Codex team posted a outage compensation reset announcement — event #4 of 70 in the archive, 10 days after the previous one, part of the "Winter compensation era". detected source scope: all_paid; 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 2025-12-17, 14 days later. That is hindsight, not a forecast that was available at the time.