Account Deactivated Unexpectedly - Need Urgent Help/Guidance on Appeal Process

Hi everyone,

I am pro user and my OpenAI account was suddenly deactivated, and I believe this might be an error or a false positive flag. I am a developer and rely heavily on this account for my daily workflow and active projects, so losing access without a clear reason is causing a major blocker for me.

I have already submitted an official appeal via the help center, but due to urgent project deadlines, I cannot afford a long waiting period.

Here are a few details if any moderator or community member can guide me:

Error Message/Behavior: You do not have an account because it has been deleted or deactivated. If you believe this was an error, please contact us through our help center at help.openai.com and include the request ID [Redacted] in your email.

"Hello,

We’re writing with an important update about your OpenAI account associated with (my account) .

Your account has been deactivated because recent activity violated our Terms and Usage Policies.

This means your account can no longer be used.

If you believe this decision was made in error, use the button below to start an appeal." (but i didn’t violate any policies though)

API usage: Yes but didn’t used at all

Has anyone else experienced this recently and managed to get a quick resolution? Are there any specific steps I can take to expedite the review process?

Any advice or help from the staff/moderators would be highly appreciated.

Thank you!

same issue

I am experiencing the exact same sudden deactivation today (June 25). My Pro subscription was successfully billed, but the account was disabled without any warning.

It seems like an automated false-positive triggered by today’s billing system glitch.

Here is my support ticket details:

  • Case Number: 10493425 or C-Zyb3H0nME3ns

Could any of the community moderators or OpenAI staff help escalate this case? Really appreciate it!

(Staff members: I can provide my registered email and Google Play Order ID via Private Message if needed to verify ownership. Please help escalate this. Thanks!)

Also, here is my case ID for today’s widespread glitch: C-cqTCLspRuang

Hoping the OpenAI team resolves this for everyone soon.

same issue for me

my account got deactivated without any reason or warning.

Access Deactivated [C-jhaQAXtMPVA1]

Same issue.

No response from support, no money refund

Same issue. No response yet

Appeal: C-9ezQNZeTkWJb

Request ID: cdflc91c-1cb9-4850-940b- 7cf1584845ac

Support case number: 10572088

Same issue.

C-8pCE0ClqQQbD

My account is a new ChatGPT Business account, less than 24 hours of setting up, with no usage. I was only setting up the admin console, ready for the team to use. It was then deactivated citing violation of terms of use.

Submitted my appeal and 10 days had passed, nothing. Support said they cannot do anything until the account is reinstated. No refund because I was “banned”.

So this “guilty until proven innocent” is how they treat their paying customers.

@OpenAI_Support - I really think this massive deactivation is not an one-off problem, me included, looks like there are lots of innocent people get their services cut off because of your internal security measure. Are you able to get us some resolutions other than “waiting”?

Hello @OpenAI_Support

I am writing this to demand transparency regarding my deactivated account (Case Number: 10740307 / Case ID: C-cqTCLspRuang).

My account was flagged and deactivated exactly during the billing and Codex background-usage glitch week (which Tibo recently posted about). The system was hitting endpoints retrying background suggestions rapidly on its own, which was clearly an internal OpenAI bug, not user abuse.

Despite this, my appeal was just automatically denied by an “AI-assisted support” message with zero human explanation, stating the decision is upheld.

As a developer relying on Codex for production workflows, this is completely unacceptable. How can any developer trust OpenAI services with their business when accounts can be permanently terminated with zero warnings and zero specific reasons, even when the termination aligns perfectly with a known internal system malfunction?

I need a real human developer or Trust & Safety engineer to audit this case, rather than leaving it to a broken automated sweep script.

Has anyone else successfully escalated an unfair ‘upheld’ ban to a human engineer during this week?

I have not received any reply to my appeal(C-5L5l4UlyPzi7) so far, and I was banned during the same period.

I sincerely hope that your appeal will be approved.

They claim I violated the terms of service. But the real criminals are the ones who deactivated my account and took my money via automatic payment. That’s theft.

@OpenAI_Support are you guys able to help at all? It has been more than 3 weeks and I heard nothing, asking support for an update went no where. Please?

Deeply Disappointed: 3+ Years Plus Subscriber Banned Without Warning Right After Auto-Renewal. OpenAI Seriously Lacks Respect for Its Loyal Users.

Update: My account has finally been restored after 21 days.

During that time, two of my appeals were denied, and I did not receive a meaningful response despite contacting OpenAI Support multiple times. I continued following up, and my account was eventually reinstated.

I’m relieved to have access again, although the process was extremely stressful and took much longer than expected. For now, I will remain on my current subscription and will not be upgrading to Pro again anytime soon.

I’m marking this topic as solved because the account has now been restored. Thank you to everyone who offered advice and support.

I believe my Pro account was deactivated in error during the automated security/telemetry sweep over the July 11–13 weekend.

I received two simultaneous deactivation notices on Monday, July 13, at 10:09 AM affecting both my primary user account and my API organization. My usage footprint is completely inconsistent with standard “abuse” or “scraping” signatures:

  • Account Tier: Pro Subscriber ($100/mo tier)

  • Usage Signature: Low-volume, standard intermittent human development use.

  • Potential Trigger: I utilize a local-first development setup and suspect that standard background workspace file-reading from Codex (scanning directory logs and workspace cache files to maintain code context) was miscategorized by automated server-side anti-scraping heuristics.

I submitted a detailed appeal through the official intake form on Tuesday, July 14, and have purposefully avoided duplicate ticketing to protect queue integrity. Because my ticket bypassed the automated instant-rejection loop, it should be sitting cleanly in the manual review queue.

  • Main Account Case ID: C-CS9tbHb0bd7D

  • API / Org Case ID: C-0BvvWAubgoBe

As this account holds critical, time-sensitive system-architecture contexts for an active research project, this lockout is a major blocker. I would be incredibly grateful if a community moderator could route these reference IDs to the Trust & Safety team for a quick manual override.

Thank you for your time and assistance.

Hey everyone, sorry for the inconvenience here.

Account suspensions and appeals require account-specific details that we can’t safely collect or investigate on a public forum. Please contact support@openai.com so our Support team can review your case privately.

To keep these requests in the right place, please don’t open additional forum topics about account suspensions or appeals. We’ll be closing this thread now. Thanks for understanding.