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 rate limits for all Codex users to compensate for the unusual high…”
Reading the announcement: 49 words, posted in the morning, 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 (Beijing 2025-11-23 07:13, Sunday) |
| Type | Outage Compensation Reset (reset_type: regular) |
| Sequence | #3 of 70 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 Codex team posted a reset-related announcement; scope follows the source.
-
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 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 #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 events respond to an incident or usage-accounting problem. Eligibility and action must be read from that event's announcement.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 Codex team posted a outage compensation reset announcement — event #3 of 70 in the archive, 17 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-02, 10 days later. That is hindsight, not a forecast that was available at the time.