A large share of Codex's global resets are compensations: outage recoveries, usage-accounting bugs, abnormal drains. By the archive's classification, outage compensation is the second-most-common trigger after milestone celebrations.
Compensation events share a stable structure: incident first, fix second, compensation third — the reset always lands after the repair. In practice, when Codex misbehaves, "wait for the official fix" almost always comes with a global refill, which is why incident periods need no anxiety.
This hub collects every event the archive classifies as outage compensation: the November 2025 recovery, the nine-day March 2026 incident cluster, the April and May accounting bugs, and June's stacked incidents with its investigation-period double reset. Each page carries the original announcement so you can reconstruct the full causal chain.
FAQFAQ
Are compensation resets announced in advance?
Rarely on their own — they arrive as part of the fix announcement ("fixed, and we've reset everyone"). The radar's official-watch state sometimes reflects these moves early.
Do unaffected users get compensation too?
Yes. Compensation resets treat all paid accounts equally — that's what distinguishes them from targeted make-goods.
How do I tell whether a reset was compensation?
Read the announcement's wording (outage / issue / drained / compensation) against its timing — the era + type labels on our event pages do this classification automatically; browse the list below.