[BUG] Google AI Pro — All 5 Accounts Simultaneously Locked for 167 Hours (IP-Level Rate Limit / Session Bleed)

Google Antigravity
, ,
1

Subscription: Google AI Pro × 5 accounts
Platform: Antigravity IDE (Windows 11)
App version: Latest as of March 2026
Region: Italy

Issue Summary

I am a professional developer running 5 separate Google AI Pro accounts to sustain a continuous development workflow. All 5 accounts hit a simultaneous 167-hour lockout on Claude Sonnet 4.6, Claude Opus 4.6, GPT-OSS 120B, Gemini 3.1 Pro High, and Gemini 3.1 Pro Low.

This is not a standard quota exhaustion. The lockout hit all 5 accounts at the exact same time, despite each account having independent quota allocations.

Observed Behavior

  • All 5 Pro accounts show ~167h refresh timer for Claude, GPT-OSS and Gemini 3.1 Pro (High and Low) simultaneously
  • Gemini 3 Flash on the same accounts shows the correct ~5h refresh (Pro tier working as expected)
  • The lockout is server-side: logging out, clearing %USERPROFILE%\.antigravity and re-authenticating does NOT resolve it
  • I spun up a virtual machine on a completely separate network/IP: the problem persists identically, confirming the lockout is tied to the Google accounts themselves — not to the local machine or IP address
  • The Antigravity UI quota screen shows available quota for all accounts — but generation still returns RESOURCE_EXHAUSTED 429
  • This confirms the discrepancy between the quota display system (fetchAvailableModels) and the generation backend (generateContent) reported in other threads

Root Cause Hypothesis

Based on my investigation and cross-referencing reports from this forum (Bug AG-859, thread #126125, #123195), I believe this is a combination of:

  1. IP-level rate limiting: Multiple authenticated sessions originating from the same IP address trigger Google’s anomaly detection. The system applies a shared weekly lockout at the IP level — not per-account — causing all 5 accounts to be locked simultaneously even though no single account exhausted its individual quota.

  2. Background quota drain: As reported in thread #125399, Antigravity IDE silently consumes Claude quota even when completely idle and no prompts are being sent. With 5 IDE instances open, this passive drain is multiplied ×5, accelerating quota exhaustion dramatically.

  3. Metadata Entitlement Sync Failure: Once the weekly cap triggers, the backend erroneously applies the Free-tier fixed epoch reset instead of the Pro rolling 5-hour window.

Impact

This is a complete business continuity failure. I rely on Antigravity as my primary development environment. With all 5 accounts locked simultaneously for 7 days, and the issue confirmed even on a VM with a different IP, I have no fallback within the Google AI ecosystem. I am being forced to migrate my entire active project to alternative IDEs mid-development, causing significant productivity loss.

Requested Actions

  1. Immediate manual quota reset for all 5 affected accounts
  2. Clarification on whether IP-level rate limiting is intentional policy or a bug
  3. Fix for background idle quota consumption — the IDE should not drain quota when no prompts are active
  4. Separation of the quota display system from the generation backend so they reflect the same state
  5. Official communication on the status of Bug AG-859 / Metadata Entitlement Sync Failure

Related Reports

  • [BUG] Antigravity IDE - Critical Quota Error (7-day lockout): thread #114724
  • :police_car_light: MAJOR ALARM - Pro Paid Users Locked for 167 Hours: thread #123195
  • Antigravity IDE consuming Claude quota automatically while idle: thread #125399
  • The “Pro” Tier Lockout - Post-Mortem: thread #126323
1 Like
2

Hi @Marco_D_Elia,

Welcome to the Forum,

Thank you for bringing these concerns to our attention. Please be assured that we have shared your feedback with our internal team for further review.

We appreciate your continued patience as we work to enhance the Antigravity experience.

1 Like
3

Update — 7 days later. Nothing changed. It happened again.

A week has passed since my original report and the response from @chunduriv assuring me that feedback had been “shared with the internal team.”

Here is what happened in the meantime:

  • None of my accounts were ever manually reset. I had to wait the full 167 hours.
  • I did not use any of the accounts during the cooldown period. Zero prompts. Zero activity. IDE closed.
  • The weekly baseline countdown has started again on all accounts simultaneously — currently showing ~5 days remaining before I can use Claude, GPT-OSS and Gemini 3.1 Pro again.
  • This means the quota is being consumed passively, without any usage on my part. This is not a usage limit. This is a billing issue.

The only “solution” suggested to me — directly or indirectly — has been:

“Upgrade to Google AI Ultra” or “purchase additional credits.”

I want to be direct: this is not a solution. This is a monetization strategy disguised as technical support.

I subscribed to Google AI Pro specifically to have continuous, reliable access. The product was advertised with a 5-hour rolling refresh. What I am actually receiving is a weekly lockout that resets itself even without usage, with the only escape being a more expensive plan.

What makes this even harder to accept is that competing tools — Cline, TRAE, Cursor, Windsurf, Copilot — do not have this problem. They provide stable, predictable access without silent weekly lockouts or passive background quota drain. At this point, these alternatives are simply more reliable for professional development workflows.

If the Pro plan cannot deliver what was advertised, that should be communicated transparently — not discovered after two weeks of debugging, forum posts, and waiting.

I am not asking for a workaround. I am asking for:

  1. An honest explanation of why quota is consumed without any usage
  2. A commitment to fix the passive background drain documented in thread #125399
  3. Clarity on whether the 5-hour rolling reset still applies to Pro subscribers for Claude and Gemini 3.1 Pro — or whether it has been silently removed

At this point I have lost two full weeks of productive development time. The silence from the team is, frankly, more frustrating than the bug itself.

2 Likes
4

I am deeply disappointed and outraged. After suffering an unjustified lockout across all 5 of my Pro accounts, I patiently waited for 5 days without even touching the program, hoping the situation would resolve itself. Today I log in, only to be told by the system that I have to wait another 7 days.

What exactly am I paying my subscriptions for?

This is absolutely unacceptable and frustrating. I am paying for a professional development environment, yet my entire workflow is completely paralyzed due to your glaring technical issues (incorrect IP-level rate limiting, phantom background quota drain, and synchronization failures). You are aware of these bugs, yet the end-users relying on your tools for their livelihood are the ones paying the price.

I demand an immediate manual unlock of my accounts. This represents a severe lack of respect and reliability towards the professionals who invest in your ecosystem.

Senza titolo
Senza titolo931×779 47.7 KB

3 Likes
5

I am having the same issue. I am a Google Premier partner and have extensively pushed Google’s solutions, but now they do not seem to give a damn about paying members who model there entire workflow around their tech that worked so well until it did not. They are great when things work (brilliant actually) but just pure evil when something does not work. How do legitimate companies that make millions for Google get treated like this, it is frankly just poor taste on Google’s side.

6

Well the problem is it doesn’t auth correct when theres multiple accounts.

If your workflow is a 5 AI Pro fleet - you can adapt my advice.

the error we have faced over the past 3 weeks (since the release of 1.19.5 actually), is that when there is more than one google account present in the default browser like chrome for example, antigravity has an account identity mismatch - this triggers NOT the 7 day bucket as we have been led to believe - it instead (in my relatively educated and experienced opinion) is in fact doing a security lockout based on account identity mismatch.

how to get around this? install google chrome canary, set it as default system browser (assuming you are on windows) whatever account you are using for your antigravity login, have ONLY THAT account logged in to that default system browser. when you want to change account sign out of browser, sign out of antigravity, close antigravity, log in to canary with your next account, then log in to antigravity.

is it going to solve your current 7 day security lockouts - no. you’ll still be waiting but after the wait you will be account properly authorized and be able to continue your grind. i would suggest to sign out of them all except one, and make sure it is matching the one in antigravity. while you are locked out - may as well do the extra cleaning and clear cache and ditch any quota extensions too because i really don’t think they are helping us track jack and might be causing harm and probably aim manually the antigravity external browser as well just to be safe. (also if you’d like, submit that feedback form inside the antigravity app so devs can get some state information).

i’ve been trying to help people understand and address this from the user facing side all week actually, i’m just a user not official anyone, just been on this since i hit the first 9 day and chasing the solution. its difficult because we have been led to believe that 7 days means bucket when in fact it is my belief that 7 days has in fact TWO possible causes.

Best of luck, i’ve been here and on reddit trying to help as much as i can - feel free to reach out and i’ll do everything i can to help.

1 Like
7

@DuctTapedGoat you are an absolute angel from heaven! Thank you so much, your method unlocked everything and I’m finally out of the ban!

I was supposed to wait another two full days, but after setting things up exactly as you suggested, the timer unlocked and restarted to 4 hours and 59 minutes. I haven’t run any tests yet, so I don’t know for sure if everything will be fully restored in about 5 hours, but as they say… that’s one small step for man, one giant leap for mankind!

Thanks again!

1 Like
8

wow they must be finally working on something in the back end because thats even more progressive than before if it actually got your timer back to 5h so quickly! :open_mouth:

yay!!! thats such great news omg!!! :partying_face:

i just went and checked mine, most of my models are back but i was still waiting on gemini pro which would have had 24hours or so remaining but everything is back to 4h59m blank slate! they really must have finally fixed it :open_mouth:

also, so actually - this 4h59m isn’t a moving timer persay - thats everything ready to go, as soon as you send a prompt, then the timer would begin the next countdown!

i just did a couple gemini flash prompts so you can see, the timer doesn’t move from 4h59 until you start using it :wink:

image
image815×724 31 KB

9

Unfortunately, I don’t bring good news: the bug (or ban, whatever we want to call it) is back.

It’s incredibly frustrating that despite all the reports, Google still hasn’t stepped in to help us out. I am paying for 5 Pro accounts to sustain my workflow, and I keep finding myself locked out for hours. This level of service disruption makes it impossible to maintain a professional development cycle.

@Bryan_Casson @chunduriv @chunduriv
Out of sheer necessity, I’ve decided to put Antigravity on hold and look into alternatives. Right now, I’m testing out Trae and it’s getting the job done. I know there are ongoing debates regarding its telemetry and privacy, but I kindly ask that we skip that discussion in this thread: right now, my absolute priority is writing code, and I desperately need a tool that works without locking me out.

If you know of any other solid alternatives that are free (or at least cost-effective, without needing to pay for multiple expensive subscriptions), please suggest them below. Thanks to everyone for the support so far.

image
image2386×1552 217 KB

10

Trae is cool, they have Kimi and she’s a beast at coding. Without a doubt my fav model - Trae actually was my preferred IDE when they were on a Request based structure. They recently changed it when Gemini3.1 dropped (which ironically is around the timeframe of the lockout errors). Now Trae uses a token/credit billing structure.

My power workflow - Gemini via the website or sidebar is first. I do my planning, mockups, notes, everything starting out with the scaffolding is there. Then, i send it in to Google Jules (I had errors there uploading but it works with Drive links and GitHub). I let Jules be my main compiler. Then, I send it over to Trae to handle the fast stuff, the minor edits. Antigravity is my last stop shop, where i do the final checks, the error resolutions. When I hit testing - thats when i get CoPilot and have them check things out, they are a great evaluator.

Since so many aren’t transparent about “usage”, the only way i know of to manage any semblance of transparency - is using multiple different platforms and chaining the workflow like that.

Chickens and baskets. :nest_with_eggs::hatching_chick::chicken::basket::egg::cooking:

Also : since you mentioned you do a multiple account structure using pro - and i don’t want to sound insensitive but, have you tried like, 5 separate computers? If the earlier account isolation worked but jammed up when you tried to change account - idk maybe that could be the solution? Like, set up a few old laptops, plug your project into a drive and put that on your router/modem or just move the drive from one computer to the next? That would likely preserve your account isolation without a cookie crumb jamming up the works :smiley:

[dropping link to thread : i’ve been pushing as much support as i can on this issue but until google actually makes a public statement - or until mods just sticky my dang guide, i’m having to link it everywhere possible]

https://www.reddit.com/r/google_antigravity/comments/1rvkqp5/ag859_solved_5_hour_refresh_workaround_legal_for/

1 Like
11

I am using Windsurf, the settings look almost identical to Antigravity, does not seem to be a cap. It even has the AI Agent, you just need to turn it on in the settings

12

I just picked up the 40$ Kimi package today because…. never enough chickens :smiley:
VS Code Extension, Online Tools, and Terminal. 5 Api keys on the 40$ package.
should be able to run it in Trae IDE, but will probably see how Void handles first.

First test didn’t bill me for every line it’s script did so thats refreshing - burn relief.
Pretty sure theres some perk to using the extension vs api, hopefully its efficient :smiley:

image
image1215×791 71.9 KB