OpenAI resets ChatGPT and Codex usage limits after outage

On July 12, 2026, OpenAI began resetting ChatGPT Work and Codex usage counters and temporarily lifted the 5-hour usage cap across Plus, Business, and Pro plans ^[1], after OpenAI product lead Tibo said the prior 48 hours of Codex and ChatGPT Work usage had been "intense" ^[1]. That reset followed the GPT-5.6 Sol and ChatGPT Work launch, whose high-compute mode was too easy to trigger and burned through usage limits far faster than expected ^[2]. OpenAI's Thibault Sottiaux later acknowledged the rollout "didn't get everything quite right," citing usage limits depleted too quickly, a confusing desktop redesign, and regressed multi-agent workflows ^[3]. That is a separate story from the global infrastructure outage on July 25, which knocked ChatGPT, the API, and Codex offline simultaneously and triggered its own emergency reset. The two events share a fix - reset the counters - but not a cause: one is a product-design and pricing problem, the other is a backend failure. Compounding the confusion, OpenAI separately had to fix a bug that was preventing some of its own announced resets from applying correctly to affected accounts, as users reported on OpenAI's community forum ^[4]. For a subscriber watching their usage bar, the distinction barely registers - it just looks like OpenAI resetting limits, again.

The July 25 outage did not degrade one product - it took ChatGPT, the OpenAI API, and Codex offline together, across the US, Europe, India, Japan, and Australia. Industry analysis from Unite.AI points to what that pattern usually means: "When a fault surfaces at once across the web app, the mobile client and the API, the cause usually sits in a shared layer" ^[5]. The specifics bear that out - users hit 503 errors carrying the internal label "biscuit_baker_service_me_circuit_open," a circuit breaker that blocked requests before they ever reached OpenAI's servers ^[6]. OpenAI's own status page listed 12 affected API components, 15 affected ChatGPT components, and 4 affected Codex components during the window ^[6]- a footprint too broad to be a single model or endpoint failing, and consistent with a shared authentication, routing, or gateway layer buckling under load. OpenAI moved from "investigating" to "monitoring" about an hour after applying a mitigation ^[6], but the status history for the surrounding days shows this wasn't an isolated blip: elevated errors were logged on July 22, 23, and 24 as well ^[7], suggesting the same underlying layer had already been under strain before it broke outright on July 25.

OpenAI has turned "we reset your limits" into its default apology, and that is starting to cut both ways. Reset events - some tied to the July 12 GPT-5.6 Sol overload, others issued whenever a status incident hits - have applied to roughly 500,000 ChatGPT Work and Codex accounts combined ^[8]. CloudYeti's tracking of OpenAI's compensation resets has counted 36 events so far, describing the pattern bluntly: "Every time something breaks on OpenAI's end - usage tracking messed up, model degraded, outage - they seem to drop a free reset into everyone's account to compensate." On the surface, that reads as generous - a company eating the cost of its own instability.

But on r/codex, the same pattern reads differently. One user described ramping up usage specifically to burn through a fresh reset before the next one landed, then hanging at zero waiting for it, and said it "might be better overall, if they would just give us steady resources without this dopamine carousel with resets every unknown amount of days." A separate complaint-flaired post, "Fix the limits or that line is gonna go down as fast it went up," drew replies comparing OpenAI's weekly limits unfavorably to Anthropic's Claude plans, with some users saying they were canceling their subscriptions over it. The reset has shifted from an emergency gesture into an expected, almost routine feature of using ChatGPT Work and Codex - which means the next time OpenAI doesn't reset promptly, or the reset bug recurs ^[4], there is less goodwill left to absorb it.

The July 25 outage was OpenAI's fourth service disruption in four consecutive days, following incidents logged on July 22, 23, and 24 ^[9]. Zoomed out further, OpenAI's status page has recorded roughly 166 incidents over about nine months since autumn 2025 - close to 18 per month ^[10]. That frequency matters more than any single outage, because it compounds against exactly the customers OpenAI is trying to win: businesses running Codex and the API inside their own products and engineering workflows. When those endpoints go down, the failure doesn't stay contained to OpenAI - it becomes an outage for every company built on top of it ^[11]. Unite.AI's analysis frames the stakes bluntly: "A model a customer cannot reach is, for that window, worth nothing" ^[5], and TheNextWeb's coverage warns that "every outage chips away at the reliability narrative enterprise buyers need" ^[6]. Usage-limit resets can placate individual subscribers cheaply, but they don't address the pattern underneath them - a shared backend that has now failed openly four days running - and that pattern, not any single day's downtime, is the harder problem for OpenAI to sell past.