October 22, 2026 • Reliability Desk • 3 min read

"50% of My Weekly Quota." Gone Overnight.

A $500 a month Pro subscriber says a few simple agent tasks ate half a week of Codex, while other paying users report refused resets, capacity errors and accounts locked for days.

An hourglass with sand running through it

An hourglass, shown for illustration. Photo: John Morgan, CC BY 2.0, via Wikimedia Commons.

Thursday, October 22 brought a fresh run of complaints from people who pay OpenAI the most: a Pro subscriber who says half a week of Codex vanished overnight, users whose usage resets will not apply, and two accounts that have been locked for days.

Half a week of Codex in one night

On r/codex, a subscriber on what they describe as the "$500/month ChatGPT Pro plan" wrote that their weekly allowance had been "draining significantly faster than usual" for several days, and that "Between October 21 and October 22, I lost approximately 50% of my entire weekly Codex allowance overnight." They say they "only ran a few agents working on relatively simple development tasks."

The user says OpenAI support confirmed the weekly quota was "100% exhausted," that two rate limit reset credits were available, and that support "cannot provide detailed per-request or per-session usage logs for personal Pro accounts." The case was escalated to a specialist. "At $500/month, I would expect much better transparency about what is consuming my allowance," they wrote.

Resets that will not apply, models "at capacity"

Another r/codex user tried to spend a banked reset before it expired and says Codex "refused to apply it" with a message that their current usage "does not need the reset." A third wrote that for "the past few days" running several Codex sessions at once keeps returning "Selected model is at capacity. Please try a different model." A fourth complained that "The 5h limit disappeared for weeks, then came back" and that resets "land on random days with little warning, and they shift the weekly reset date."

On the OpenAI Community forum, a Pro user wrote that inside Projects, selecting GPT 5.6 Pro and pressing Send switches the model to GPT 6 Pro "the moment I click Send," which they say spends their weekly GPT 6 Pro quota.

Locked out for days

A company that bought a ChatGPT Business workspace on October 9 says "nobody has been able to use it since." Its only admin says every SAML sign in through Microsoft Entra ID fails with oaisaml_authenticate_failed, so they cannot change SSO settings, add an admin or manage the subscription, and several support cases have been opened.

A separate user says they have been locked out since October 19 because sign in "now requires an authenticator code I never set up," with no recovery code, and no update from support since confirming there was no unauthorized activity.

What the status page shows

OpenAI's status page logged "Elevated ChatGPT conversation and Responses API errors" for users in India, Japan and Korea starting 7:18 PM Pacific on October 21, resolved at 1:50 AM on October 22. On October 22 it logged "Degraded Performance of Dots on Enterprise" from 11:51 AM, resolved at 1:55 PM, and "New Ad Accounts failing to provision admins," still open when we read it. OpenAI also posted that on October 20, from 9:35 to 10:35 AM PDT, "some users near Illinois experienced authentication errors" with the API, ChatGPT and Codex, fixed by rolling back a configuration change.

None of the status entries mention Codex usage accounting. We found no OpenAI statement about the quota reports, and none of the posts quoted here had a staff reply when we read them. These are individual user reports; we have not tested the affected accounts.

Sources

Keep Digging

Homepage Chat Memory Full After 9 Messages, Oct 21 ChatGPT Status Tracker Real User Accounts Every Article On This Site

← Back to ChatGPT Disaster Homepage