Same for me, please fix this. I’m on the Ultimate subscription.
1 Like
Does Google only block accounts and never unblock them?
Has anyone had their account successfully reinstated?
no body know banned account will be unlocked, but we definitely need to create new accounts
what kind of bullying TOS from google, why I cannot use the tokens I have paid, where is the “openness“ from google
2 Likes
I am on the AI ultra plan, and i’m not even allowed to use the services i paid for.
It’s been 2 days since the service got disabled, and i can’t even access my antigravity.
Cloud Code Assist API error (403): This service has been disabled in this account for violation of Terms of
Service. If you believe this is an error, contact gemini-code-assist-user-feedback@google.com.
What is going on, and how can this even be allowed.
Sent an email, but have not recieved anything back at all, it’s pretty frustrating.
I didn’t even know it was against TOS, i just tried using openclaw because of a youtube channel i watched.
I really don’t get it, what’s even wrong if i stayed within my quotas? I upgraded my plan for the sole purpose of having an increased limit?
1 Like
Just to report that I have sent a bug report from Antigravity, as the support engineer suggested. Maybe we should all do the same.
I did it and I got a “standard” support ticket to logout, reinstall Antigravity, etc. The same things I already did with another guy on the support chat, so it is like a loophole. Now I do not get the message that my account was disabled, but instead I get something more “generic” and ask me to try again later. It is the 3rd day when I check and I get the same message, even if the webpage is telling that the authentication was successful. I just canceled the subscription, since this was the main thing for what I actually subscribed for and also for their “support”.
I’ve been investigating this issue deeply (I’m also affected as a Pro subscriber). It seems we are all caught in an automated “security sweep” triggered by the recent hype around third-party tools like OpenClaw or various Antigravity proxies.
Here is what is actually happening technically:
-
The Trigger: Google’s Risk Engine has started flagging non-official OAuth requests. Specifically, many third-party proxies use a hardcoded header ideType: 6. Google knows this ID does not belong to the official Antigravity IDE or VS Code extension. When the system sees ideType: 6 combined with high token usage (typical for agents like OpenClaw), it triggers an automated ban for “ToS Violation.”
-
The “Smoking Gun” in your Console: If you want to see the proof, go to your Google Cloud Console → Log Explorer. Look for logs around the time you were banned. You will likely find a critical error:
-
Error: Exception calling SetIamPolicy
-
Reason: A required Google-managed service account has been deleted or de-provisioned by the automated ban.
-
This means your project is now in an “inconsistent state” where the backend is trying to manage a service account that no longer exists.
-
-
Why “Standard Support” isn’t working: The first-line chat support will give you generic advice (reinstall, logout) because they don’t have visibility into the Gemini Safety/IAM flags.
My advice for those affected:
-
Don’t just email the feedback address: It’s currently a “black hole” due to the volume of requests.
-
If you are a paid Pro/Ultra subscriber: Go through Google One Support. Explain that your “Cloud AI Companion API” is broken at the infrastructure level and point them to the IAM errors in your logs. Ask them to escalate the case to the “Higher Tier / Technical Engineering team.”
-
Stop trying to log in: Repeated failed attempts might prolong the automated “cooldown” period.
Google needs to realize that 95% of us are enthusiasts and developers testing new tech, not malicious actors. I have already escalated my case with technical logs, and I suggest you mention the “missing service account” issue in your tickets to help their engineers identify the bug in their automated banning script.
Stay patient
14 Likes
is your account have been resolved?
Not resolved yet, but there is progress. Google One support has escalated my case to the higher-tier technical team after I provided the IAM logs. It’s clear now that first-line support can’t fix this, so escalation is the only way forward. I’ll let you know as soon as I hear back from the engineers.
8 Likes
I’m have same problem. In my case I’m using open code(oh-my-opencode).
I’ve just sent its mail.
1 Like
I’m have same problem. I’ve sent mail and waiting.
2 Likes
I just opened a Google One support case (I’m a Pro user). In my case, I explained to them that I have been using my Gemini CLI to test different products and tools in combination with my Gemini account. I’m crossing my fingers that they can unban my account
2 Likes
Check hosts.txt in your win file… You might have wrong configuration. I had solved it by removing local host IP.
Note that I have just contacted Google One support regarding to our problems. And the support specialist has already sent the URL of this discussion post to their speicialist to handle the case. So hopefully they can solve the issue for all of us, once and for all.
3 Likes
if you will make it please write detailed explanation how to solve this problem step by step in the best way!
1 Like
@Dawid_M How did you get access to those logs, its not in my google console….
Go to the Google Cloud Console: console.cloud.google.com
-
Select your project: In the top left corner (next to the Google Cloud logo), make sure you have selected the project you were using with Gemini/Antigravity.
-
Open the Navigation Menu (the three horizontal lines in the top left) and go to Logging → Logs Explorer.
-
In the “Query” box (the big text area in the middle), paste the following line:
severity>=ERROR AND (protoPayload.methodName=“SetIamPolicy” OR “Cloud AI Companion”) -
Click the “Run query” button on the right.
-
What to look for: Look for entries with a red exclamation mark. Click on them to expand the details. You are looking for an error message that says something like:
“Exception calling IAM: Service account [ID-NUMBER] does not exist” or “Permission Denied”.If you can’t find “Logs Explorer” in the sidebar menu:
The sidebar in Google Cloud Console is dynamic and can be confusing. The fastest and most reliable way to find it is:
-
Go to the Search Bar at the very top of the page (where it says “Search resources, services, and docs”).
-
Type “Logs Explorer”.
-
Click the first result under the “Products & Pages” section.
This will take you directly to the logs regardless of your sidebar settings or language.
-
1 Like
I can confirm your analysis. I am seeing the exact same behavior on my end as a Pro subscriber.
My local Antigravity logs completely support the theory that the backend identity (Service Account) has been obliterated, leaving the project in an inconsistent state.
Here is what my Antigravity logs are spitting out:
-
Identity Deletion Confirmation:
[Antigravity] Failed to get OAuth token: key not found
[Antigravity] Cache(userInfo): Singleflight refresh failed: key not found
This matches your point about the Service Account being de-provisioned. The system isn’t rejecting the key; it physically cannot find the key/identity associated with the user anymore. -
Broken Trust Chain:
remote error: tls: unknown certificate
The removal of the managed service account seems to have invalidated the SSL/TLS certificates used for the secure tunnel, causing the handshake to fail before authentication even happens. -
Client-Side Lobotomy:
Because the initial auth fails so catastrophically, the extension enters a zombie state where it throws recursive errors
1 Like
the most terrifying is the silence (days in). think you stablish your revenew stream upon a service supported like that.