Knowledge base · TOPIC-10

Gemini connectivity: local path or service incident?

Short answer: compare local protocol evidence with Google’s official status and the API’s returned error class. Anonymous reachability cannot prove API-key validity, quota, billing, model access, or regional eligibility.

Google’s Gemini troubleshooting guide distinguishes transient conditions such as timeouts, 429, and 5xx from client-side request errors. That is provider-reported interpretation. A local DNS, TCP, or TLS result is observed evidence. Neither alone proves the root cause of an authenticated request.

Record the timestamp, HTTP status or network error, and the exact product surface—without recording keys or prompts. Check the relevant official status component and retry only according to documented policy. One trusted alternate network can help separate path-specific behavior from a wider incident, but a passing connection still does not validate account state.

Gemini is UNSUPPORTED / NOT_EXECUTED in Tivor Open Probe V0.1. The tool does not send Gemini API requests or inspect credentials. Use the browser Scanner for limited reachability evidence and Open Probe for local network context. Related: HTTP 401/403 is not the same as unavailability.