Paid Gemini API customer blocked by incorrect IP geolocation — "User location is not supported" from a Tokyo, Japan datacenter IP

Gemini API
1 
Since 2026-09-19 13:02:32 UTC (22:02:32 JST), every Gemini API request from
our production server has been rejected with:

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

Our server is physically in Tokyo, Japan. Japan is a supported region.
Google's geolocation data for our IP is wrong, and as a result a paying
customer has been locked out of a paid service for over a day.

AFFECTED IP
  203.137.179.33
  Registered to IDC Frontier Inc., Tokyo (APNIC/JPNIC, country: JP)
  Correct location: Tokyo, Japan

ACCOUNT
  Project: "Suipa" (gen-lang-client-07354577.., project number 5017064249..)
  Billing: Tier 2, prepaid, auto-recharge ON, positive credit balance
  API key suffix: ...8CpQ

EVIDENCE THAT THIS IS IP GEOLOCATION AND NOTHING ELSE
  1. The same API key, at the same minute, returns 200 from another network
     in Japan and 400 from 203.137.179.33 (10 of 10 requests). Content
     generation succeeds from the other network.
  2. An intentionally invalid key sent from 203.137.179.33 returns
     API_KEY_INVALID. Our real key passes key validation and is rejected
     only afterwards by the location check. The key, project, quota and
     billing are all healthy.
  3. Forcing both hosts onto the same Google frontend IP with
     `curl --resolve` does not change the outcome. The result follows the
     client IP, not the frontend.
  4. youtube.com served to 203.137.179.33 embeds "GL":"US", while the same
     page served to the other Japanese network embeds "GL":"JP". Google
     itself does not recognise this Japanese IP as being in Japan.
  5. Nothing changed on our side. No deploy, no configuration change, no key
     change. Requests succeeded at 13:02:30 UTC and began failing two
     seconds later.

IMPACT
  All Gemini-backed features of our production service (suipa.jp) have been
  down since the time above, including image generation, which has no
  substitute. To keep the service running we have had to move workloads to
  a competitor's API at roughly 18x the per-document cost. Meanwhile our
  prepaid Gemini credits, which expire after one year, cannot be used
  through no fault of ours.

WHAT WE ARE ASKING FOR
  1. Correct the geolocation of 203.137.179.33 (and its surrounding IDC
     Frontier range) to Japan.
  2. Tell us when the correction will take effect.
  3. Explain why a location check fails closed for a verified, paying
     Tier 2 account whose billing address is in Japan, with no warning and
     no way to appeal from the console.

We can provide request timestamps, response bodies and curl transcripts on
request.
2

Hello @S_T1 ,

Please let us know if you are still facing this issue.