UpTrajectory Review
OpenAI is currently addressing a significant issue with its Codex service, where users are unexpectedly hitting usage limits much faster than anticipated. This problem appears to stem from the company's fraud-prevention systems mistakenly imposing stricter limits on certain accounts. OpenAI has established a dedicated team to investigate and resolve the situation, indicating the seriousness of the matter.
For small business operators relying on Codex for coding tasks, this situation could disrupt workflows and project timelines. If your team is experiencing these limits, it may be wise to monitor your usage closely and consider reaching out to OpenAI for clarification. While the company is taking steps to rectify the issue, the uncertainty around usage caps could impact productivity, especially for those on tighter budgets or deadlines.
“Codex's usage limits are displayed on a user's dashboard as a percentage.” — Business Insider
Takeaway: Monitor your Codex usage closely and stay informed about OpenAI's updates to avoid disruptions.
From the original item — Business Insider:
Samuel Boivin/NurPhoto via Getty Images
- OpenAI is investigating Codex users quickly hitting usage limits.
- The company said the issue stemmed from its fraud-prevention systems erroneously limiting some accounts.
- OpenAI’s Thibault Sottiaux said the company set up a ‘warroom’ on Sunday to address the issue.
OpenAI set up a “warroom” to investigate a flurry of user reports that its coding agent is hitting usage limits faster than usual.
An update on OpenAI’s status page said that some users’ Codex limits are “depleting faster than expected” and that it was related to its “abuse and fraud prevention systems incorrectly rate limiting certain accounts.”
Thibault Sottiaux, the engineering lead for OpenAI’s Codex, said on Sunday that the company implemented an across-the-board reset of user caps while it looked into the issue.
“Codex team is in a warroom on a Sunday combing through logs and checking whether there is anything that could lead to increased usage drains for some users,” Sottiaux said in a separate Sunday X post.
“Taking it very seriously and won’t rest until we get to the bottom of it.”
Usage limits track how much compute an AI coding task has used. Codex’s usage limits are displayed on a user’s dashboard as a percentage. More intense tasks burn through credits faster, and the limit varies by subscription tier.
what has happened to codex limits?
they went from practically infinite tokens to weekly quota gone in 2-3 days on the pro 20x plan.
— Alexander Hoff ❍ (@axhoff) June 28, 2026
However, a wide mix of Codex users took to X over the weekend to report that they were reaching the limit faster compared to just a week ago for similar tasks.
“It really seems something is off. I have the $200 plan, and I had to work hard the entire week to burn through the 7 days’ usage,” wrote a software engineer called Adam. “The last two days burned the entire week’s usage in one day each, and I had to use reset for the 1st time.”
OpenAI’s status page added that the impact appears limited and it is continuing to monitor the situation.
As we are still investigating, I have reset everyone’s Codex usage limits. This is a hard reset given some users had stacked up to three banked resets already that they can apply on their own schedule.
Funnily enough, this week at OpenAI is called the RESET week, which is meant… https://t.co/UdCSbW03QU
— Tibo (@thsottiaux) June 28, 2026
AI companies have gradually been reducing usage limits as the soaring popularity of their tools has strained compute resources. In March, Anthropic adjusted Claude usage caps during peak hours. Some software engineers have been restructuring their days while they wait for usage limits to reset.
More broadly, AI providers have been moving away from all-you-can-eat use of their tools, while companies have started limiting employee AI use to keep costs down.
OpenAI’s Codex limit issue follows an outage earlier this month. Anthropic has had similar problems, and a Claude outage in March underscored how much software engineers now rely on the technology, as some bemoaned having to write code by hand again.