Codex + ChatGPT Pro account banned with no warning, no explanation - 18-month subscriber

Posting here because the standard appeal channel has produced no human response after three attempts, and I have run out of escalation paths. I am writing as a longtime supporter of OpenAI, not someone who is here to attack the company.

I have been a paying ChatGPT Pro subscriber since December 10, 2024. The subscription is billed monthly through Google Play and remains active. I am a heavy user of ChatGPT and Codex for my daily development.

The account was banned with an absolute block and zero prior warning. The termination email cited a generic violation of Terms and Usage Policies, with no specific clause, prompt, or behavior identified. The ban instantly revoked access to ChatGPT, Codex, API keys, and my Pro plan. Crucially, whatever I was building inside Codex is now completely inaccessible, including conversation context I cannot easily reconstruct.

For context: I am a physician and a developer. I mention this not to demand special treatment, but to clarify that I rely heavily on OpenAI’s ecosystem for legitimate work and have absolutely no incentive to abuse it.

To address the standard questions head-on:

  • Account Sharing: None. Used exclusively by me.

  • Network Masking: I do not use a VPN, proxy, or any tool to mask my IP.

  • Automation: I do not run scripts, bots, or automated scrapers against the ChatGPT UI or Codex.

  • Payments: No chargebacks or disputed payments.

  • Content: I have never attempted to jailbreak or bypass safety systems.

  • Duplicate Accounts: I have no other OpenAI accounts.

The only explanation I have for triggering this automated, zero-warning ban is my network environment. I frequently connect from the Hospital Santa Catarina Paulista network in SĂŁo Paulo during my clinical shifts.

It turns out the hospital’s enterprise network routes all its internet traffic through a Google Cloud link. I checked the IP today. The public egress IP from this clinical network resolves directly to a Google LLC Data Center/Transit IP (177.69.36.49 / IPv6 2001:4860:7:f03::de).

OpenAI’s security system must have seen my traffic coming from a Data Center IP block and automatically assumed I was a headless proxy, a bot farm, or someone masking their network. I’m not. I was literally just a regular user sitting at a hospital computer, using the corporate network. Hundreds of hospital devices share this same public IP, which clearly looks like a proxy or datacenter node to your automated fraud/abuse detection systems. I do not control this clinical network architecture and cannot change how its outbound traffic is classified.

This automated ban destroyed my development workflow and locked me out of critical code context I can’t easily reconstruct. I have zero reasons to break the rules.

I can share my User ID and Organization ID privately with any OpenAI staff member who responds here.

If anyone from the OpenAI staff is reading this, I would deeply appreciate a human review of the logs to reverse this data center IP false positive. If anyone in the community has experienced a similar absolute block due to shared corporate/hospital networks and found a resolution path, I would value your advice.

Honestly the hospital/shared enterprise network explanation doesn’t sound impossible to me, especially if everything exits through a cloud/datacenter IP range that abuse systems already watch closely​:face_with_monocle:

But from the outside nobody here can really confirm what actually triggered it unfortunately. Could’ve been IP reputation, traffic heuristics, or something else entirely​:thinking:

The rough part is losing access to active Codex/dev workflow context instantly with no actionable explanation. Hopefully staff can get a human review on it​:pleading_face:

Thanks a lot for jumping in, S_z — genuinely appreciate it. Just having someone acknowledge that the hospital/shared-egress theory isn’t crazy helps, because from my end it’s the only variable I can actually point to.

Quick status update: still no human response. Three appeal attempts through the standard channel, all answered by what looks like an automated pipeline, and the account is still under an absolute block — ChatGPT, Codex, API keys, and the Pro plan all revoked. The Google Play subscription is still being billed in the meantime, which makes the silence sting a bit more.

You’re 100% right that nobody outside can confirm what actually triggered it — could be IP reputation, traffic heuristics, or something else entirely. That’s exactly the problem: without any actionable explanation, I can’t even fix whatever I supposedly did. The only signal I have is that the hospital’s entire network egresses through a Google LLC datacenter/transit IP (177.69.36.49), which to an abuse classifier probably looks identical to a proxy or bot farm. Hundreds of clinical devices share that NAT and I have zero control over how it’s classified upstream.

And yeah — losing live Codex context instantly, with no way to export or recover it, is the part that really hurts. It’s not just “a subscription,” it’s active work.

If any Regular or OpenAI staff member reading this can help route it for a human review, I’d be enormously grateful. Happy to share my User ID and Org ID privately. Not looking for special treatment — just five minutes of human eyes on the logs.

Thanks again, S_z. Means something when you’re otherwise shouting into the void.

Welcome to the Dev Community! @npribeiro

Have you already created a support ticket with OpenAI Support? If so, please share the ticket number here and I can take a look at the account.

~Smith

@OpenAI_Support thank you for reaching out, Smith. Means a lot!

Appeal Submission Confirmation: C-SOG00jZD9A3F

User ID: user-w7vk8pU7Kuwj9DUcSQMYSzzn Organization ID: org-VQaXy9KnTJ4hgSsi3ZHj6nGa // Case Number 09313155

I also sent an email to support@openai.com with the full case description. Happy to share any additional information you need.

Thanks for sharing everything. I’ll work on the support case you created and help get this resolved.

To help streamline the process, I'll close this community thread. All further communication and updates will take place through the support ticket moving forward. Appreciate your patience in the meantime.

~Smith