Skip to the board
DIDRESET
UTC

"Some Codex users may be experiencing unexpected usage limit resets."

by vortwangUpdated

"Some Codex users may be experiencing unexpected usage limit resets." is the first line of OpenAI's status-page incident of 2026-09-09 (17:29–17:54 UTC), when some banked resets were consumed in ChatGPT Work and Codex without fully refreshing the windows. Tibo Sottiaux wrote the same day that everyone who used one in the affected window "is getting another one and an email to apologize." It was an incident, not a global reset. The last official Codex reset on record was Sep 12, 2026, 08:09 UTC.

Last reset
12 SEP 08:09Z

@thsottiaux

Status
OVERDUE

The gap since the last reset is past 1.5x the recent median.

Next est.
ANY TIME

Days since
6.9

days

What does "Some Codex users may be experiencing unexpected usage limit resets." mean?

The sentence comes from status.openai.com, not from the app. The incident opened at 17:29:55 UTC as "Investigating unexpected usage limit resets" with that line, moved to "We've identified the issue and are working on a fix." at 17:40:47, "We have applied the mitigation and are monitoring the recovery." at 17:45:25, and "All impacted services have now fully recovered." at 17:54:12 UTC.

What users saw was a banked reset that was marked used while the usage bars did not refresh, or refreshed and then snapped back. At 18:23 UTC Tibo Sottiaux described it: "There was a bit of a kerfuffle this morning with some banked resets not fully applying when used in ChatGPT Work and Codex. Everyone who used one in the affected time window is getting another one and an email to apologize."

The help center's rule is the yardstick: a banked reset "is consumed only when it successfully refreshes at least one eligible usage window." A reset that was consumed with no refresh is therefore a defect, and the article's "If your reset is missing or did not work" section is the path to Support. Issue #44221 (user report, 2026-09-09) describes a consumed reset followed by the weekly window being recalculated and the reset date moving from September 16 to September 12; #45236 reports a reset date moving later with no reset used.

Which window is full?

Which window is full?
WindowResetsWhere to check
5-hour windowRefreshed the moment you redeem a full banked reset: "Using a full banked reset refreshes your 5-hour and weekly Codex usage windows".Settings → Usage after redeeming; /status in the CLI
Weekly limitRefreshed by the same redemption, and the reset "changes your weekly reset date"; the new date is shown in Settings → Usage.Settings → Usage; /status (the "Weekly limit" line)

What to do when you see it

  1. Confirm what actually happened

    Refresh Settings → Usage, "confirm you are using the correct account or workspace", and in the CLI type /status to read the "5h limit" and "Weekly limit" bars. The dashboard "may take a short time to update"; compare the reset count and the bars before concluding the reset was lost.

  2. If you redeemed on 2026-09-09, check your inbox

    OpenAI said everyone who used a reset in the affected window "is getting another one and an email to apologize." Look for the replacement under Settings → Usage as "1 reset available" or "Full reset" before contacting anyone.

  3. Otherwise, report it to Support with the details the help center asks for

    Include "The offer or announcement you expected the reset from", "The date, time, and time zone when you used it", "A screenshot of your current Usage page" and "The Codex client and model you were using". Support "can review eligibility and investigate suspected missing or incorrectly applied resets", but "Reporting an issue alone does not qualify you for an additional reset or compensation."

  4. Stop an agent from spending your reset

    Issue #41801 (user report, 2026-08-31) describes Codex invoking "Consume usage reset" during a conversation without a separate confirmation. Redeem resets yourself from Settings → Usage or the /usage menu, and do not ask the agent to "compensate" you with a reset; treat a banked reset as an account resource the agent should never touch.

  5. Do not expect a courtesy reset

    "Support does not provide manual or courtesy resets." Corrections are made only when a review finds an error: "Any correction is based on verified eligibility and the error identified."

When does it reset?

Your own windows: a correctly applied full banked reset refreshes both the 5-hour and weekly windows at once and "changes your weekly reset date"; the new date is in Settings → Usage and on the /status "Weekly limit" line. After the incident, OpenAI issued replacement resets rather than re-running the failed ones, so the replacement follows the normal rules and expiry shown in your account.

Account-wide resets: the 2026-09-09 event was an incident, not a global reset, and it does not appear on this board as a reset. The board row above shows the last official Codex reset on record; the Codex history page lists every announcement, including banked-reset drops, with the original posts. Whether a global reset moves your weekly date is not published; see the linked guide.

FAQ

Was 2026-09-09 a global reset?

No. It was a status-page incident about banked resets "not fully applying" when redeemed, resolved in 25 minutes, followed by replacement resets for affected users. The last documented global reset before it was the automatic reset of 2026-09-07 that "did not add a saved reset."

My reset was consumed and my bars did not move. Will OpenAI give it back?

If you redeemed inside the affected window on 2026-09-09, OpenAI said you get another one plus an email. Otherwise contact Support with the date, time and time zone, a screenshot and your client and model; a banked reset "is consumed only when it successfully refreshes at least one eligible usage window", so a consumed reset with no refresh is an error Support can investigate. Courtesy resets are not issued.

Can Codex redeem my banked reset on its own?

One user report (issue #41801) says it did, via a "Consume usage reset" action, after the user asked about compensation for wasted usage. OpenAI has not documented an agent-side redemption path; the help center describes redemption as something you do from Settings → Usage or /usage. Redeem it yourself and keep the agent out of it.

Did the incident move my weekly reset date?

Not documented. User reports after the incident describe weekly reset dates being recalculated (#44221: September 16 → September 12 after a consumed reset; #45236: September 15 → September 19 with no reset used). The only official statement about the weekly date concerns banked and purchased resets, not incidents; read Settings → Usage for your own account.

Sources

  1. OpenAI status page incident "Investigating unexpected usage limit resets", 2026-09-09 17:29:55–17:54:12 UTCverified 2026-09-18
  2. Tibo Sottiaux on X, 2026-09-09 18:23 UTC: some banked resets "not fully applying"; everyone affected "is getting another one and an email to apologize"verified 2026-09-18
  3. OpenAI Help Center: How banked Codex resets work (article 20001498)verified 2026-09-17
  4. OpenAI Help Center: Managing usage with GPT-6 Astra in Work and Codex (article 20001516)verified 2026-09-17
  5. ChatGPT Learn: Codex CLI slash commands (/status, /usage, /logout)verified 2026-09-18
  6. openai/codex issue #44221 (2026-09-09): user report: banked reset consumed, 94% weekly quota dropped to 0%, weekly reset date moved Sep 16 → Sep 12verified 2026-09-18
  7. openai/codex issue #41801 (2026-08-31): user report: Codex consumed a banked reset ("Consume usage reset") without explicit confirmationverified 2026-09-18
  8. openai/codex issue #45236 (2026-09-13): user report: weekly reset date moved Sep 15 → Sep 19 with no reset used, after the Sep 9 incidentverified 2026-09-18

Want the next Codex reset on your phone?

Sponsors