Nefish
June 25, 2026, 7:09pm
1
I am a ChatGPT Pro / Codex Pro 5x subscriber.
On June 25, 2026 (Asia/Shanghai), my previous Pro 5x subscription appeared to end unexpectedly even though I believe it should still have had about one week remaining. Because I rely on Codex for work, I paid again for the $100 Pro 5x plan.
After renewing, my Codex usage started draining abnormally while I was barely using Codex. In one afternoon, my weekly usage dropped by nearly 30%, and my 5-hour usage was also almost exhausted.
I checked ChatGPT/Codex sessions, devices, login activity, and running tasks, but I did not find abnormal logins, unknown devices, active Codex tasks, or background work that could explain this usage.
I also opened a GitHub issue with more details:
opened 04:27PM - 25 Jun 26 UTC
bug
codex-web
rate-limits
### What issue are you seeing?
I am reporting a serious Pro 5x subscription and… quota accounting issue.
I have been a ChatGPT Pro $100 / Codex Pro 5x subscriber. My previous Pro 5x subscription should still have had roughly one week remaining, with the next renewal expected around late June or early July.
However, on June 25, 2026 (Asia/Shanghai), I unexpectedly found that my Pro membership had dropped. Because I rely on Codex for work, I paid again for the $100 Pro 5x plan.
After renewing, I started seeing another serious problem: my Codex usage quota kept decreasing even though I was barely using Codex.
Over the course of the day, especially during the afternoon, my weekly usage dropped by almost 30%. Earlier in the afternoon, my 5-hour usage was also almost fully drained.
This does not match my actual usage at all. I did not run heavy coding tasks, long refactors, large repository analysis, background automations, or continuous Codex sessions. In fact, I barely assigned any tasks to Codex that day.
I also checked ChatGPT and Codex account/session areas and did not find:
- abnormal logins from other regions
- unknown devices
- active conversations consuming tokens
- extra Codex tasks running in the background
- obvious evidence of another machine consuming my quota
From my perspective, quota is being consumed while idle or with almost no real activity.
This looks very similar to recent quota accounting reports, including:
- #29955
- #30002
- #26512
- #21966
- #28525
- #20153
There are two separate problems here:
1. My previous Pro 5x subscription appears to have ended early, costing me roughly one week of paid Pro 5x access.
2. After renewing, my 5-hour and weekly Codex quota started draining abnormally while I was effectively idle.
This is unacceptable for a paid Pro 5x account. A $100 Pro 5x subscription should not lose a large portion of its quota in a single afternoon when there is no meaningful Codex usage, and a paid subscription should not end early without explanation.
### What version of the Codex App are you using?
Latest version available to me.
### What subscription do you have?
ChatGPT Pro $100 / Codex Pro 5x.
### What platform is your computer?
macOS.
### What steps can reproduce the bug?
I cannot intentionally reproduce the internal accounting issue, but this is what happened:
1. I had an existing Pro 5x subscription that should still have had about one week remaining.
2. On June 25, 2026 (Asia/Shanghai), I unexpectedly found that my Pro membership had dropped.
3. I renewed and paid again for the $100 Pro 5x plan.
4. After renewal, I barely used Codex during the day.
5. During the afternoon, my 5-hour usage dropped heavily and was almost drained.
6. By the end of the day, my weekly usage had dropped by nearly 30%.
7. I checked ChatGPT and Codex for abnormal logins, unknown devices, active tasks, or other sessions, but found no explanation.
### What is the expected behavior?
Codex quota should only decrease in proportion to actual usage.
If I am not running Codex tasks, not using background automations, and not sending meaningful prompts, my 5-hour and weekly quota should not continuously drain.
A Pro 5x account should not lose around 30% of weekly quota in one afternoon with almost no activity.
Also, a paid Pro 5x subscription should not end around one week early without explanation.
### What is the actual behavior?
My previous Pro 5x subscription appears to have ended early, forcing me to renew again before the expected renewal date.
After renewing, my quota dropped significantly while I was effectively idle.
The observed consumption appears far higher than any real Codex usage I performed. This strongly suggests a quota metering / server-side accounting problem rather than actual token consumption.
### Requested resolution
Please investigate the account-side metering and subscription state for my account.
Specifically, I am asking OpenAI to:
1. Restore or reset the incorrectly consumed 5-hour quota, weekly quota, and/or credits.
2. Review why my previous Pro 5x subscription appears to have ended early.
3. Compensate the lost Pro 5x subscription time, either by extending the subscription period, refunding the duplicate renewal, or providing equivalent credits.
4. Provide attribution or visibility into what source, task, device, or backend process consumed the quota, if the system believes the usage was legitimate.
If this is related to the known quota accounting / reset bug reported by other users, please restore the incorrectly consumed quota and compensate the lost paid subscription time.
This is a serious paid-plan reliability issue. I paid for Pro 5x because I rely on Codex for work, and I need both the subscription status and quota meter to reflect actual usage accurately.
I am happy to provide screenshots, timestamps, or account details privately if needed.
I have already contacted OpenAI Help Center, but so far I only received automated replies. I need a human review from OpenAI staff.
Please investigate:
why my previous Pro 5x subscription appears to have ended early;
why my Codex quota drained while idle after renewal;
whether my incorrectly consumed quota can be restored;
whether the lost Pro 5x subscription time or duplicate renewal can be compensated.
This is a serious paid-plan reliability and billing issue, not just a normal rate-limit complaint.
Drained while idle?
@OpenAI_Support I guess that is for you.
@Nefish