Gemini API location restriction affecting multiple Thailand IP ranges — AS135161

Gemini API
1

Hello Google Gemini API Team,

We operate Zcom Cloud BKK4, a public cloud infrastructure platform located in Bangkok, Thailand, under AS135161 (GMO-Z com NetDesign Holdings Co., Ltd.).

We are reporting a recurring Gemini Developer API location restriction affecting multiple customer-facing public IPv4 ranges in Thailand.

Thailand is listed as an officially supported region:

1. Error observed

Our affected servers consistently return:

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

2. Latest investigation — 28 October 2026

We conducted tests across multiple BKK4 public IP allocations.

Affected Customer Standard IP ranges:

IP address Network Result
118.27.146.42 118.27.146.0/23 HTTP 400
118.27.147.191 118.27.146.0/23 HTTP 400
118.27.148.3 118.27.148.0/23 HTTP 400
118.27.150.190 118.27.150.0/23 HTTP 400
118.27.151.6 118.27.150.0/23 HTTP 400
118.27.146.80 118.27.146.0/23 HTTP 400

All failed addresses returned the same FAILED_PRECONDITION location error.

Working control addresses:

IP address Network Result
118.27.144.2 Production infrastructure HTTP 200
118.27.145.4 Development infrastructure HTTP 200
118.27.156.23 PaaS Additional HTTP 200
118.27.157.22 PaaS Additional HTTP 200
118.27.158.90 PaaS Additional HTTP 200

These HTTP 200 results are from API connectivity checks; successful inference has not been independently confirmed for every control address.

3. Controlled inference test

On 28 October 2026, we tested the same Gemini API key, model and request payload from two different BKK4 source addresses.

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

  • 118.27.146.80 — 05:15:47 UTC — HTTP 400 / FAILED_PRECONDITION (location restriction).

  • 118.27.144.2 — 05:15:44 UTC — HTTP 503 / UNAVAILABLE (temporary model demand, not location restriction).

Both requests successfully established HTTPS connections with Google, with valid TLS verification.

The internal server did not encounter the location restriction, while the customer server did.

4. IP geolocation verification

We independently checked the IP geolocation of the affected and working addresses.

  • APNIC WHOIS: country TH, netname ZCOM-THAI

  • IPinfo: Bangkok, Thailand

  • Cloudflare: loc=TH

  • ASN: AS135161

Both successful and affected addresses belong to our Thailand-operated cloud network.

5. Previous incident

We observed the same issue on 7–8 September 2026, affecting several customer IPs. Some subsequently recovered without changes to our network infrastructure.

The issue has now recurred in October.

6. Google report already submitted

We submitted the official Gemini API & Google AI Studio Location Issue Report on 28 October 2026.

Google Forms displayed: “Your response has been recorded.”

However, no case number or confirmation email was provided.

7. Request for assistance

Could a Google representative please help us:

  1. Investigate why different IP ranges from the same ASN and supported country receive inconsistent Gemini API location eligibility decisions.

  2. Review and correct any inaccurate regional eligibility or IP geolocation classification applied to these customer IP addresses.

  3. Advise whether network operators can submit affected IPv4/IPv6 prefixes for review in bulk.

  4. Confirm whether an authoritative geofeed or Google ISP Portal registration would assist.

  5. Advise how to track or escalate our submitted location issue report.

We can provide sanitized technical logs, precise timestamps, and additional network allocation information if needed.

Thank you.