Unexpected Error 400: "User location is not supported for the API use" from Poland (EU)

Gemini API
1

Hi,

I am suddenly encountering the following error when making API calls:

Error 400: User location is not supported for the API use

This issue started occurring abruptly without any changes to my codebase or setup. Up until now, everything was working seamlessly.

Details:

Location: Poland (European Union) – which is an officially supported region.

Affected Service: Google AI Studio / Gemini API

It appears that my current IP range might have been incorrectly flagged or geoblocked by mistake. Since I am accessing the service from an authorized EU location, could you please verify if there is an issue with recent IP subnet routing for this region?

Ip: 57.128.247.1..

Thank you for your help.

Best regards

2

Hello @Muny ,

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

@Muny I’m in Canada and started experiencing the same thing yesterday from a couple of our servers.

After some analysis I found that Google was blocking all requests from the OVH Canada datacenter over IPv6. So I forced my applications to use IPv4 and it was fine after. Not sure if this is your problem but Google silently changed something clearly since many users have been reporting this in the last couple of days. Not sure if this will help but worth a try.

@Pooja_Kapse FYI the “Report IP Problems” page does not support IPv6 ranges so it doesn’t help if someone is accessing Google services via IPv6.

4

Same for me from OVH in France.

5

Same for me, but Linode Chicago.

6

Same for me using an OVH server hosted in Virginia (US-EAST-VA), was working fine till today and all of a sudden broke my app.

7 
Since 2026-08-19 04:56 UTC, Gemini API requests from our OVHcloud server
in Frankfurt, Germany return:

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

Source IPv6: 2001:41d0:701:1100::3fcb
Provider: OVHcloud / AS16276
Endpoint: GET https://generativelanguage.googleapis.com/v1beta/models
Last successful request: 2026-08-14 14:57 UTC

I am personally located in Thailand. The API requests themselves originate
from our server in Frankfurt, Germany. Both Thailand and Germany are officially
supported regions for the Gemini API.

Controlled test using the same API key and endpoint:
- forced IPv4 (57.129.113.230): HTTP 200
- forced IPv6 (2001:41d0:701:1100::3fcb): HTTP 400 location unsupported

Multiple API keys and projects are affected, including a billed project.
No VPN or proxy is used.

This strongly indicates that the server’s IPv6 address or prefix is being
incorrectly geolocated or blocked. Please correct the geolocation/allow-list
for this IPv6 address or prefix.
8

same issue here to a linode server in Sydney Australia

I switched to ipv4 in /etc/gai.conf and it’s working again now

9

Thank you, switching to IPV4 fixed it for me as well!

1. Update Netplan (/etc/netplan/): Remove IPv6 blocks and force IPv4-only structures inside your configuration file.

2. Block Cloud-Init (/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg): Disable network auto-configuration to stop system overwrites.

3. Disable Kernel IPv6 (/etc/default/grub): Append the disable parameter, update the bootloader, and reboot the VPS.

4. Prioritize IPv4 Precedence (/etc/gai.conf): Uncommend the precedence rule to prefer IPv4 routing for outbound traffic.
10

I am facing same issue my whole server is now unable to access the GCS Bucket showing error “We’re sorry, but this service is not available in your location” after it was working super fine …

11

Please try switching to IPv4 and see if that resolves the issue

12

Thanks for reporting this issue and apologies for the inconvenience.

Can I request you all to please take a moment and fill this form. We are trying to debug the issue. Thanks again!