Paid Tier 3 Gemini API User Suspended for “Hijacked Resources” — Need Clarification

Gemini API
1

I’m a paid Tier 3 Gemini API user and my project was recently suspended with the following reason:

“abusive activity consistent with hijacked resources”

Project:
gen-lang-client-0714990559

I’m trying to understand what exactly triggered this suspension because the message is very vague.

My setup mainly involved:

  • personal development/testing

  • self-hosted API gateway

  • Gemini API integration

  • OpenAI-compatible API routing

I was NOT intentionally abusing the service, generating prohibited content, or attempting malicious activity.

The suspension email mentioned:

  • abusive activity

  • hijacked resources

  • possible compromised project behavior

What confuses me is:

  • Billing was enabled

  • This was a paid Tier 3 account

  • I did not receive clear technical details

  • I’m unsure whether the trigger was:

    • API gateway/proxy usage

    • concurrency

    • VPS/datacenter IPs

    • shared routing patterns

    • automatic abuse detection

Has anyone experienced something similar recently?

I would especially appreciate clarification from Google staff regarding:

  1. Whether self-hosted API gateways (NewAPI/OneAPI style) violate policy

  2. What “hijacked resources” usually means in practice

  3. Whether proxy-style routing alone can trigger suspension

  4. How to safely use Gemini API in development environments without being flagged

I’ve already started:

  • rotating keys

  • adding stricter rate limits

  • improving authentication/security

  • reviewing logs and access patterns

Any guidance would be greatly appreciated.

2

Hoping this isn’t the case, but see if you can check every single project for a Gemini API spending frenzy. … have been scraping API keys and racking up bills, but that alert you received looks similar