Gemini API project-wide quota set to 0 RPM after policy notice — appeal still pending

Gemini API
, ,
1

Hello,

I am requesting guidance and, if possible, assistance escalating a Gemini API restriction affecting my Google Cloud project.

After receiving a policy notice, I submitted an appeal through the Google Cloud Console. I have not yet received a response, and the Gemini API remains completely unavailable.

I performed several clean diagnostic tests:

  • Tested multiple Gemini Flash and Pro models.
  • Tested through Gemini CLI.
  • Tested with direct REST requests.
  • Tested directly from Google Cloud Shell to eliminate my local machine, network, Node.js, CLI configuration, and workspace context as possible causes.
  • Tested the models-listing endpoint, which does not invoke a specific model or generate content.

Every request returns HTTP 429 RESOURCE_EXHAUSTED.

The complete quota metadata returned by the API is:

Quota metric:

generativelanguage.googleapis.com/api_requests

Quota limit:
ApiRequestsPerMinutePerProjectPerRegion

Quota limit value:
0

Quota unit:
1/min/{project}/{region}

Quota location:
us-south1

Reason:
RATE_LIMIT_EXCEEDED

The error message is:

“Quota exceeded for quota metric ‘API requests’ and limit ‘Request limit per minute for a region’ of service ‘generativelanguage.googleapis.com’.”

This means the effective general Gemini API request limit for the project is currently zero. The error occurs even when listing models, before selecting a model or sending a content-generation prompt.

Additional context:

  • The project still has a positive prepaid balance.
  • The AI Studio dashboard shows usage below the visible RPM, TPM, and RPD limits.
  • The same error occurs across all tested models.
  • Creating a new API key in the same project does not change the result.
  • I have not created another project to bypass the restriction.
  • I already submitted an appeal and am waiting for a response.

My usage is legitimate software development through local command-line tools. I sometimes worked with two local workspaces simultaneously. If credentials from different projects were accidentally configured, this was not intended to aggregate or circumvent quotas.

After receiving the notice, I took the following actions:

  • Consolidated API usage under one Google Cloud project.
  • Removed unused and old credentials.
  • Reviewed local environment files and CLI authentication.

Could a Google team member or forum moderator please help with the following?

  1. Confirm whether a quota value of 0 is consistent with an active Trust & Safety restriction.
  2. Confirm whether there is any additional remediation I should perform.
  3. Help route or escalate the pending appeal to the appropriate team.
  4. Confirm whether the project-level Gemini API quota can only be restored by Trust & Safety.
  5. Advise whether there is another official support channel for this case.

I can provide the project ID, project number, appeal date, and complete error response privately to a Google moderator if required.

Thank you.

{
“code”: 429,
“status”: “RESOURCE_EXHAUSTED”,
“reason”: “RATE_LIMIT_EXCEEDED”,
“quota_metric”: “generativelanguage.googleapis.com/api_requests”,
“quota_limit”: “ApiRequestsPerMinutePerProjectPerRegion”,
“quota_limit_value”: “0”,
“quota_unit”: “1/min/{project}/{region}”,
“quota_location”: “us-south1”
}