OpenAI fixes mistaken ChatGPT suspensions and restores subscriptions and credits

• OpenAI said OpenAI’s incident post came from an internal issue that incorrectly suspended a subset of user accounts, not a policy crackdown, and the company said it was restoring access plus related subscription and credit problems.
• The public timeline ran from reach_vb’s first acknowledgment in the morning, to OpenAI’s formal statement in the afternoon, to reach_vb’s late update saying most affected accounts and subscriptions were back.
• User reports in a Reddit thread about a deactivated account after heavy Codex usage and ai_for_success’s roundup of X and Reddit complaints suggest the lockouts hit some heavy agent users before OpenAI confirmed the suspensions were mistaken.
• The suspension incident landed a day after thsottiaux’s Codex reliability note disclosed three separate Codex incidents in 24 hours, and after thsottiaux’s follow-up on a token undercount bug said OpenAI had fixed quota accounting for fewer than 15 percent of Pro and Plus accounts.

You can read OpenAI’s status page, skim the main OpenAI community thread, and compare it with a Reddit report tied to a 28-hour Codex run. The odd detail is the blast radius beyond login itself: OpenAI’s statement explicitly mentioned subscription and credit issues, while users in the community thread said some restored accounts appeared to come back on the free tier.

The first public acknowledgment was brief. In the morning, reach_vb said OpenAI was investigating reports that users “may be getting banned.”

About six hours later, OpenAI’s official statement framed it more clearly: an issue had incorrectly suspended some accounts, and the recovery work now included subscriptions and credits. That wording matched the status incident page, which describes account access problems for a subset of users but does not disclose a root cause.

By early afternoon, reach_vb’s repost of a restored user said at least one affected account was back and the issue was still under investigation. Late in the day, reach_vb’s final update said most affected accounts, including subscriptions, should now be restored.

The notable part of OpenAI’s statement was not just access restoration. It also said the company was “working through related subscription and credit issues,” which means the suspension bug touched billing state as well as login state.

That showed up in user discussion. In the main community thread, several posters said restored accounts appeared to return without the right paid status, a complaint Exa surfaced alongside the incident updates. reach_vb’s late-night post then singled out subscriptions as part of the recovery milestone, which suggests the restoration happened in phases rather than as a single rollback.

OpenAI also appears to have added some make-good after the fix. reach_vb’s “sweet little surprise” note said affected users should check email, but did not say publicly what the surprise was.

Before OpenAI confirmed the suspensions were mistaken, users were already trying to reverse-engineer what had triggered them. the Reddit report described a Pro account deactivation after a /goal task that reportedly ran for roughly 28 hours with a large repo, repeated retries, compaction errors, and many agent requests.

That thread matters because it gives a concrete failure pattern, even if it does not prove causality. The original poster guessed the long-running session may have tripped an abuse or security flag, while one commenter in the same thread said they had seen a Codex prompt loop run for about 12 hours days earlier. Separately, ai_for_success’s roundup said X and Reddit had filled with similar suspension complaints over the prior 12 hours.

OpenAI has not publicly tied the mistaken suspensions to heavy Codex usage. The company’s official language stayed at “incorrectly suspended,” and OpenAI’s status page offers no mechanism or root cause.

The suspension incident did not land in isolation. On June 4, thsottiaux said OpenAI had seen three separate small Codex reliability incidents in 24 hours and reset usage limits across all paid plans.

The next evening, thsottiaux’s follow-up disclosed another Codex issue, a bug that had been undercounting served tokens for a small share of Pro and Plus users, which he said affected fewer than 15 percent of accounts. Users noticed the earlier reset immediately, with bridgemindai’s post describing “full tanks across the board,” and the same reset showed up in an OpenAI community quota thread.

That sequence leaves a pretty messy 48-hour log for OpenAI’s coding surfaces: reliability incidents, a quota reset, a token accounting fix, then an account suspension bug serious enough to spill into subscriptions and credits.