Sign in to the provider's console as that account and read the notice there — it names the specific reason, which the API error does not. If it is a disabled API rather than a suspended account, re-enable the API for that project and the account works again. Appeal through the provider if you believe it is a mistake. There is nothing kRouter can do client-side to restore access. In the meantime, connect another account: kRouter keeps the suspended one out of rotation so it stops wasting requests, and routes to the next healthy one.

Creating a new key on the same account. — The account is what is suspended, so every credential under it fails the same way. Routing the same account through a different tool. — The block is server-side; the client making the call is irrelevant.

Google Antigravity, Gemini, and other Google-backed providers

AI provider "account has been suspended" or "service has been disabled" — recovery steps

Matches these upstream messages

your account has been suspended
this service has been disabled in this account
this account is deactivated

What you actually see

{"error":{"code":403,"message":"This service has been disabled in this account.","status":"PERMISSION_DENIED"}}

What does "your account has been suspended" mean?

The provider has taken the account out of service. Unlike a rate limit this is a policy decision, so retrying — from any tool, not just kRouter — will keep failing until the account itself is restored.

Why does it happen?

Terms-of-service enforcement, billing problems, or an API that was disabled for the project. Accounts created in bulk, or used from many IPs at once, are the common triggers.

How do I fix it?

Sign in to the provider's console as that account and read the notice there — it names the specific reason, which the API error does not.
If it is a disabled API rather than a suspended account, re-enable the API for that project and the account works again.
Appeal through the provider if you believe it is a mistake. There is nothing kRouter can do client-side to restore access.
In the meantime, connect another account: kRouter keeps the suspended one out of rotation so it stops wasting requests, and routes to the next healthy one.

Is it really this error?

These get mistaken for each other, and chasing the wrong one is where the time goes.

Looks like: The "verify your account" gate.

Actually: Verification is reversible by you in a few minutes. Suspension needs the provider to act, and no client-side change reaches it.

Looks like: A billing failure.

Actually: Sometimes it IS billing — check the console. A disabled API on the project reads identically in the API response but is a one-click fix.

What will not fix it

Reasonable-sounding fixes that do not apply here — worth ruling out before you spend an afternoon on them.

Creating a new key on the same account.
The account is what is suspended, so every credential under it fails the same way.
Routing the same account through a different tool.
The block is server-side; the client making the call is irrelevant.

What kRouter does automatically

kRouter locks the ENTIRE account for 24 hours — every model on it, not just the one you asked for. It immediately fails over to your next connected account or provider, so the request still completes. The account is flagged as needing human action and stays out of rotation until you fix it upstream.

Stop hitting this error

kRouter routes your AI coding tools across every provider and account you own, so a limit on one does not stop your work. It is free, MIT-licensed and runs on your machine.

Install kRouter