Antigravity account keeps getting banned: what helps

You connect an Antigravity account, code for a day, and then it happens: every request comes back with a 403 and the message "Verify your account to continue." You verify with Google, it works for a few hours, and the ban returns.

An earlier version of this post called a smarter cooldown "the real fix". It is not. Google's Antigravity terms say that using third-party software, tools or services to access the service is a breach, and that it may be grounds for suspension or termination of your Antigravity and/or Gemini CLI accounts. A router, kRouter included, is third-party software. So a ban that keeps coming back is a policy question before it is a technical one.

What a router can control is narrower: whether it keeps throwing real requests at an account Google has already flagged. That part kRouter changed in v0.5.93, and it is what the rest of this post covers.

Why a flat 24-hour cooldown makes it worse

When Antigravity returns 403 Verify your account, the sensible-looking response is to mark the account unavailable for 24 hours and then put it back in rotation.

In the reports that led to v0.5.93, flagged accounts stayed flagged for days, not hours. So a fixed 24-hour lock produced this loop:

1. The account hits a 403. The router locks it for 24 hours.
2. The lock expires and the account rejoins the pool.
3. The next request goes to that account. Google's flag is still active, so it gets another 403.
4. The router locks it for another 24 hours, and the cycle repeats.

The account never recovers, and every cycle spends a real request on an account that was always going to refuse it.

What kRouter does instead: longer locks for repeat bans

kRouter treats a repeat ban as a sign that the account needs more time, not the same amount. The base lock for this error is 24 hours, and each consecutive lock multiplies it:

1st lock  →  24 hours  (1x)
2nd lock  →  48 hours  (2x)
3rd lock  →   4 days   (4x)
4th lock  →   7 days   (7x)
5th+      →  14 days   (14x)

The count is kept per connection. A single successful reply from the account resets it to zero, so one bad day does not keep a healthy account out for weeks. After you complete Google's check, Test Connection on that account clears the current lock straight away.

The lock covers the whole account, not one model, and it is stored in kRouter's database, so a restart does not cut it short.

The chronic-ban badge

After three consecutive locks, kRouter marks the connection as chronically banned and shows a red chronic ban ×N badge on its card. The tooltip says what it means: this account has failed verification several times in a row and needs to be checked by hand.

That badge is the signal to stop and look, not to wait it out. Sign in to the official Antigravity app with that account. If it asks you to verify, do it there. If the app refuses you too, the account has been restricted rather than gated, and the badge is telling you to remove it from the pool.

What kRouter cannot fix

The backoff only stops kRouter from making a ban worse. It does not make one less likely, and nothing in kRouter makes third-party access to Antigravity permitted.

kRouter did fix one bug of its own that flagged accounts on their very first request: until v0.5.46 its bootstrap call described the client differently from the OAuth flow. That story, and how to tell a verification check from an outright restriction, is in Antigravity "verify your account" 403: what it means.

In February 2026 Google restricted accounts tied to third-party use of the Antigravity backend. kRouter's dashboard marks the Antigravity provider with a risk notice and asks you to confirm before connecting it, because the account may be restricted or banned.

Spreading traffic across accounts

The same release fixed a related complaint: with round-robin turned on, one Google account was doing all the work while the others sat at 0% used. Conversation stickiness, which keeps the upstream prompt cache warm by sending a conversation back to the same account, was silently overriding the round-robin choice. Since v0.5.93, choosing round-robin for a provider switches that stickiness off for it.

Since v0.5.119, Antigravity uses round-robin by default unless you pick another strategy for it. Antigravity enforces a per-minute limit on top of the daily quota, and pinning traffic to one account tripped that limit quickly. Round-robin in kRouter is sticky by default: an account handles 3 requests before the next one takes over.

Rotating between accounts does not change Google's terms. If a provider forbids third-party access, spreading the same traffic over more accounts does not make it allowed.

What to do when an account is banned

1. Check the official app first. If it asks you to verify, complete the check in a browser signed in as that account, then click Test Connection in kRouter.
2. If the app refuses you, stop sending traffic to the account. Remove it from kRouter and follow the appeal path Google shows you.
3. Give Gemini traffic a sanctioned path. A Gemini API key from AI Studio, or Vertex AI, is billed by Google for exactly this kind of programmatic use, and kRouter connects both as API-key providers. Put one after Antigravity in a combo so a locked account does not stop your work.

Common questions

Why does my Antigravity account keep getting banned?

Google's Antigravity terms treat access through third-party software, tools or services as a breach. A ban that returns after you verify usually means Google is still flagging the use itself. A router's backoff can stop it making things worse; it cannot make that use acceptable to Google.

How long does kRouter keep a banned account out of rotation?

Twenty-four hours for the first lock, then 48 hours, 4 days, 7 days and 14 days for each further consecutive lock. A successful reply resets the count, and Test Connection clears the current lock once you have verified the account.

What does the "chronic ban" badge mean?

The account has been locked three or more times in a row. kRouter shows the badge so you check the account by hand instead of waiting for another cooldown to expire. It clears on the next successful reply.

Will round-robin across several Google accounts avoid bans?

No. Round-robin spreads load so no single account trips Antigravity's per-minute limit, but it does nothing about Google's terms. Each account is subject to the same rules.

Related

• Antigravity "verify your account" 403: what it means
• "Verify your account to continue" error reference
• The Zenith Routing Engine