Gemini App vs Gemini API dual check

Google Gemini & API IP check

Hitting 'Gemini isn’t currently supported in your country' or 'User location is not supported for the API use'? Google enforces two separate region matrices for the Gemini web app and the Gemini API. Check both side by side right here.

App vs API splitWorkspace rule awareCloud API checkIPv4 & IPv6 lookup

Current egress IP & Gemini dual-track check

Reads your active browser egress IP for both Gemini App and Gemini API, or test any remote server IP in step 3.

Waiting for the report…
Current egress IP — — —
Heuristic risk score / 100
— pts
—
Network type—
ASN—
Native IP—
Checked at—

How to read it:—

Reputation:—

Source:—

2Gemini App vs Gemini API readiness scores
Waiting for the report…
3Test any server IP for Gemini & AI Studio

Public IPv4 and IPv6 are supported; private addresses return a not-applicable notice.

Enter an address to see the result
Looked-up address — — —
Heuristic risk score / 100
— pts
—
Network type—
ASN—
Native IP—
Checked at—

How to read it:—

Reputation:—

Source:—

Why Gemini App and Gemini API give different region verdicts

Google publishes distinct availability lists for the consumer Gemini web experience and for Google AI Studio / Gemini API. Certain territories (such as Hong Kong) are excluded from free/standard Gemini API access, while Mainland China is listed as Workspace-only for Gemini App and unsupported on Gemini API.

Checking both tracks simultaneously prevents deploying backend code to a server region where generativelanguage.googleapis.com rejects requests with HTTP 400.

Why Google may still block access when public geo-IP looks supported

Unlike stateless services, Google combines current IP geolocation with internal location signals and account metadata:

  • Proprietary Google geo-feed drift: shared proxy IPs heavily used by mobile devices with GPS/Wi-Fi location enabled can be re-mapped by Google to another country
  • Google Account country association: an account permanently associated with an unsupported region or Supervised/Workspace policy can still be gated
  • Dual-stack IPv6 leaks: Google prefers IPv6 by default — if your IPv4 is in a supported region but IPv6 routes locally or via another country, Gemini will read the IPv6 location

Choosing a server IP for Gemini API

Gemini API tolerates cloud datacenter ASNs well (up to 80/100 in our model) provided the host sits in a supported country such as the US, Japan, Singapore, Taiwan or Western Europe and has no severe abuse history.

Frequently asked questions

How do I fix 'User location is not supported for the API use'?

Verify the server’s egress IP (both IPv4 and IPv6!) in step 3 above. Move the API caller or outbound gateway to a country supported on ai.google.dev/gemini-api/docs/available-regions.

What does 'Workspace only' mean on Gemini App?

Google’s official Gemini App availability page notes that in Mainland China only eligible Google Workspace business/education editions can enable Gemini, not personal Gmail accounts.

Why check IPv6 specifically for Google services?

Google domains publish AAAA records globally, and modern OSes prefer IPv6 within milliseconds. Always verify both IPv4 and IPv6 egress on our homepage if results look unexpected.

Can I check my server from SSH without a browser?

Yes — run curl -sL https://ip-find.com/en/ in your terminal to see both Gemini App and Gemini API scores instantly.

Check dual-stack IPv6 & DNS egress next

Make sure IPv6 and DNS resolvers match your intended region on the full ip-find homepage.