Gemini API suspension: Cloud Support redirects to appeals, but Cloud Console is blocked

Hello Google AI Developers team,

I am looking for the correct review or escalation route for a Gemini API / Google Cloud restriction.

I use the official Gemini API for text tasks in my private comic-drama application. Public registration is disabled, I am the only user, and my normal country of use is the United States. I am a paying customer.

My project was suspended on November 4, followed by a Cloud-wide service restriction on November 5. The notice referred to activity consistent with hijacked resources, but did not identify a specific request or resource. I submitted the project appeal and supplied sanitized gateway records and configuration checks. The key was restricted to the Gemini API and an allowed server IP; tests from other IPs were rejected. The project appeal was denied on November 8 without identifying the behavior that needs remediation.

A subsequent direct API test returned HTTP 401, ACCOUNT_STATE_INVALID, stating that the service account bound to the API key was deleted or disabled. The Cloud Console and Support Center redirect to the account restriction page, which says the entire Cloud service is unavailable.

I then submitted the GCP Account Suspension Inquiry. On November 10, Cloud Support said the issue was outside its scope and linked the Gemini API troubleshooting documentation. Its policy-suspension guidance points back to Cloud appeals: Google AI Studio

I have also submitted an updated account-level appeal explaining this routing problem.

Could a Google team member help identify the team responsible for reviewing this restriction, or an escalation route that works while Cloud access is blocked? I would appreciate specific remediation guidance and a review of the evidence. I can provide existing case references, project identifiers, correspondence, and sanitized records privately to verified staff.

Thank you.