Gemini API: User location is not supported from a Moldova server IP

Gemini API
, , ,
1

Subject: Gemini API returns 400 FAILED_PRECONDITION “User location is not supported” from Moldova server

Hello Gemini API / Google AI team,

I am requesting clarification and, if possible, a review of the location eligibility classification for my Gemini API project.

I have a Google Cloud project:

Project ID: cruisestratbot
Project number: 201329394..

The Generative Language API is enabled.

I created an authorization API key bound to a service account and restricted to the Generative Language API.

The key itself is valid. I verified the raw key format and length locally and also tested it directly from my server.

The following minimal REST request is made from my own Linux server:

POST https://generativelanguage.googleapis.com/v1beta/models/gemini-3.8-flash:generateContent

The request uses:

  • a valid authorization API key

  • x-goog-api-key authentication

  • a minimal generateContent request

  • IPv4 explicitly forced with curl -4

  • HTTPS connection directly to generativelanguage.googleapis.com

The server receives:

HTTP 400

{
“error”: {
“code”: 400,
“message”: “User location is not supported for the API use.”,
“status”: “FAILED_PRECONDITION”
}
}

The server’s public IPv4 address is:

213.232.235.167

The server is physically hosted in Chisinau, Moldova.

Moldova is listed as a supported country/region for Gemini API access.

I have also verified that the API key is being accepted far enough for the request to reach the location eligibility check. Previously, an incorrectly formatted key produced API_KEY_INVALID; after correcting the key, the API now consistently returns the location eligibility error above.

The request is also explicitly forced over IPv4, so this test is not dependent on IPv6 routing.

Could you please clarify:

  1. Is the IP address 213.232.235.167, or its hosting/provider network, classified by Google as an unsupported location or network type?

  2. Does Gemini API currently restrict requests originating from datacenter/VPS IP ranges even when the server itself is located in a supported country?

  3. Is there a recommended procedure for requesting a review or correction of the location classification for this IP/network?

  4. Is there any additional project, account, or security eligibility requirement that I should check for this Free Tier project?

  5. If server-side access from this IP/network is not eligible, is there an officially supported alternative for using Gemini API from a backend server located in Moldova without enabling paid billing?

I am not including the API key or any private credentials in this request.

I can provide additional diagnostic information if required.

Thank you. Additional information from the hosting provider:

I contacted my VPS hosting provider regarding the source IP 213.232.235.167.

They officially confirmed that:

  • 213.232.235.167 belongs to their VPS infrastructure;

  • the IP is classified by their infrastructure as Moldova / Chisinau;

  • they have no known regional, security, or other restrictions applied to this IP or subnet;

  • they have no information indicating that this IP/subnet was previously used for a large volume of automated requests to Google;

  • they could not identify any upstream IP geolocation issue from their side.

The provider cannot assign another IPv4 to this existing VPS because IP replacement is only available during the first 24 hours after VPS creation.

Therefore, could Google please check how 213.232.235.167 is classified by the Gemini API location/eligibility system?

The same minimal Gemini API request consistently returns:

HTTP 400
FAILED_PRECONDITION
User location is not supported for the API use.

The request is forced over IPv4.

I would specifically appreciate clarification on whether:

  1. the IP itself is being classified by Google’s Gemini API backend as an unsupported location;

  2. the hosting/datacenter ASN or IP range is subject to a separate eligibility restriction;

  3. the Google account/project has an additional regional eligibility state;

  4. there is an official process for requesting an IP/location classification review.

I am not providing the API key or any credentials.

PS.

2

Hello @Andrew_Gl,

This error occurs because the IPv4 address 213.232.235.167 is being associated with an unsupported region rather than Moldova.

To clarify your specific questions:

  • This restriction applies strictly to the IP address classification. There is no restriction on your Google Cloud project (cruisestrat...), and the Gemini API does not block datacenter or VPS networks located in supported regions.
  • Google determines IP location using aggregated network and traffic signals in addition to regional registry (WHOIS) records. If an IP address or surrounding subnet on a shared VPS host has historically carried traffic from an unsupported region, its location classification can differ from the physical datacenter country shown in your provider’s records.
  • Regional eligibility requirements apply to both the Free Tier and Paid Tiers, so enabling paid billing on your project will not bypass this error from the same IP address.

Next steps:

  • Submit a location review request for 213.232.235.167 through Google’s Report IP problems form. Please note that IP location reviews and updates can take several weeks to propagate across Google services.
  • Ask your hosting provider (or their upstream transit provider) to submit or update an RFC 8805 IP geolocation feed for their prefix via the Google ISP Portal.
  • For immediate access, provision a new server instance that assigns an IP address from a different subnet, or route requests through a host whose IP resolves to Moldova on Google services.