Gemini API Location Error from U.S.-Hosted Server IP

Gemini API
, , ,
1

Hello Google Gemini API Team,

I am experiencing what appears to be an incorrect location classification when accessing the Gemini API from a U.S.-hosted server.

Source IPv4 address: 15.204.50.1..
Hosting provider/network: OVH US / JetHost
Server location: United States (Hillsboro, Oregon)
Model tested: Gemini 3.5 Flash-Lite
Gemini API tier: Free tier
Google project ID: gen-lang-client-0487847700

Requests from this server reach generativelanguage.googleapis.com successfully, but Gemini API requests return:

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

I have completed the following troubleshooting:

  • The same Gemini API key and model work successfully from my local U.S. connection.
  • The hosting server can reach generativelanguage.googleapis.com over HTTPS.
  • The request was explicitly forced over IPv4 using curl -4 and returned the same location error.
  • The server’s outbound IPv4 address is 15.204.50.138.
  • Public IP geolocation identifies this address as Hillsboro, Oregon, United States.
  • My hosting provider has independently confirmed that the server is hosted on U.S. infrastructure and that the IP belongs to an OVH U.S. network.

Because the United States is a supported location and the same API credentials work from another U.S. connection, this appears to be related specifically to Google’s location or network classification of the server IP.

Could the Gemini API team please review the location classification of 15.204.50.138 and confirm whether the IP or its network range is being incorrectly identified as originating from an unsupported region?

I am happy to provide additional diagnostic information if needed. I have intentionally not included my API key.

Thank you.

2

Hello @roy.arellano ,

This could be specific to your IP address. Please report it on our Report IP problems page. Suggested workarounds which may help for now:

  • Try temporarily switching to a different network (e.g. try with the hotspot from your phone if available).

  • Try asking your host for a new IP.

  • Trying switching between IPv6 / IPv4.

3

Thanks! I reported it. Switching to another server may not solve it if its on the same network segment. I’m checking with the hosting provider what the IP address is to an alternate server. However, that would cause a service interruption for not just my site but other sites as well.

4

Hello @Pooja_Kapse,

Thank you for your earlier response and recommendations. I wanted to provide an update because the issue initially appeared to be resolved but has since returned.

Following your recommendation, I submitted the IP address through Google’s Report IP Problems page. Shortly afterward, the Gemini API began functioning correctly. Our WordPress AI chatbot successfully connected to Gemini, completed its initial website indexing, and generated conversational responses.

Unfortunately, as of October 15, 2026, the same issue has returned.

I performed additional testing directly from the hosting server, bypassing WordPress and the chatbot plugin entirely. The API continues to return:

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

Additional findings:

  • Server IP: 15.204.50.138
  • Hosting provider: JetHost / OVH
  • Physical location: Hillsboro, Oregon, United States
  • Model tested: gemini-3.5-flash-lite
  • Connection: IPv4 explicitly forced using curl -4
  • API usage: Within the displayed request and token limits
  • IP address: Unchanged since the original report

I have also submitted a second IP correction report through Google’s reporting page today. The submission was acknowledged, but Google indicates that corrections may take more than a month and that individual follow-up is not provided.

Because this is a hosted application, switching to a mobile hotspot or another local network does not address the underlying problem. My hosting provider has independently confirmed that the server operates on U.S. infrastructure.

Could this issue be escalated to the Gemini API engineering team for further investigation?

Specifically, I would appreciate confirmation of whether Google’s Gemini API infrastructure is incorrectly or intermittently classifying this U.S.-based IP address as originating from an unsupported region.

The intermittent nature of this problem is particularly concerning because the application is now deployed on a live business website. Even when connectivity is restored, we cannot reliably operate the service without knowing whether the issue will recur.

I appreciate your assistance and any guidance toward a permanent resolution.

Thank you.

5

Hello @roy.arellano ,

Please try the below steps:

  • Make sure you’re in one of the supported regions.

  • Turn off any VPN, proxy or iCloud Private Relay, and connect directly.

  • Make sure you’re 18 or older and have verified your age.

  • Try a different network, for example your phone’s hotspot.

If none of these help, please share the details using this form so we can investigate further: Gemini API & Google AI Studio Location Issue Report

6

Thanks, @Pooja_Kapse,

I’ve confirmed that the hosting server is located in Hillsboro, Oregon, USA, which is a supported region. There is no VPN, proxy, or iCloud Private Relay involved, and my Google account’s age verification is complete.

As previously noted, this is a server-side API connection originating from my U.S.-based web hosting provider, not a personal device or local network. Therefore, switching to a mobile hotspot would not address the issue.

The problem also remains intermittent. The API previously worked successfully from this same server and IP address (15.204.50.138) before returning the same location restriction error.

I’ll complete the Gemini API & Google AI Studio Location Issue Report as recommended. I appreciate your assistance and hope this can be escalated for investigation, as the recurring issue is affecting a live business application.