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: “We have reset rate limits for all Codex users to compensate for the unusual high…”
Reading the announcement: 49 words, posted in the evening, plainly worded — set beside its neighbors, the continuity of the "Winter compensation era" voice comes through.
Quick factsTHE SNAPSHOT
| Item | Data |
|---|---|
| Announced | 2025-11-22 23:13 UTC (31:13 Beijing, Saturday) |
| Type | Outage Compensation Reset (reset_type: regular) |
| Sequence | #3 of 53 tracked resets |
| Gap before | 17 days |
| Gap after | 10 days (next reset: 2025-12-02) |
| Running average at that time | 33.5 days (mean of the prior 1 gaps) |
| Where this gap sits in history | longer than 0% of historical gaps (ranked #2 longest among the gaps recorded up to then) |
| Source | public announcement by @thsottiaux ↗, archived by codex-resets.com |
TimelineWHAT HAPPENED
-
2025-11-22 23:13 UTCThe official global-reset announcement went out.
-
Original announcement
“We have reset rate limits for all Codex users to compensate for the unusual high latencies in or near the US in the previous hours. Grateful for the team working hard behind the scenes to keep Codex running 24/7. I do recommend trying out GPT-5.1-Codex-Max too if you haven’t! https://t.co/xVe5IC4VFs”— @thsottiaux on X ↗
-
EffectThe reset propagated across all paid accounts and quotas were refilled.
The era: Winter compensation eraCONTEXT
Resets in this period were mostly compensation: the November outage recovery, usage discrepancies wiped after the billing-system rewrite, and a Christmas thank-you. Resets followed events, not a schedule, while the team reworked systems underneath.
In the full sequence, this is event #2 of 6 in the "Winter compensation era"; 10 days later, the next reset landed on schedule on 2025-12-02. Announced on a Saturday, 17 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.The 17-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 November 22, 2025 (Saturday)?
On November 22, 2025 (Saturday), the OpenAI Codex team announced a outage compensation reset — reset #3 of 53 in the archive, 17 days after the previous one, part of the "Winter compensation era". 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 2025-12-02, 10 days 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.