Is Google Gemini down?

Understanding Google Gemini availability

Google Gemini has separate access paths: the web app at gemini.google.com and API requests sent through generativelanguage.googleapis.com. These paths can fail independently. A working web app does not prove that an API key, endpoint, model, quota, or request is valid, and an API error does not necessarily mean the Gemini web app is unavailable.

For a possible provider-side disruption, compare your symptoms with the official Google Cloud status page. A listed incident can support the conclusion that the problem is broader than one browser or account. An empty incident list does not rule out a regional issue, account restriction, browser problem, or connectivity failure.

To establish the scope of the problem, check:

• Whether Gemini fails for other users, devices, or networks.
• Whether the failure occurs during sign-in, page loading, prompt submission, or response generation.
• Whether the web app fails while API requests continue, or whether both access paths fail.
• Whether a private window or second browser changes the result.

A failure across multiple environments is more consistent with a service-side issue. A failure limited to one browser, account, device, or network points first to an access-specific or local cause.

Troubleshooting Google Gemini problems

1. Check for a wider Gemini or Google Cloud incident

Review the official Google Cloud status page for a reported incident affecting the relevant Google service. If Gemini fails consistently across browsers, devices, and networks and an incident is listed, the cause is more likely provider-side. Repeated retries usually will not resolve an active outage; monitor the incident and try again after it is updated or resolved.

If no incident is listed, continue with the isolation steps below. Status pages may not show every regional, account-specific, or newly developing problem.

2. If the Gemini web app will not load

For problems at gemini.google.com:

• Reload once, then test the site in a private or incognito window.
• Try a second current browser.
• Temporarily disable extensions that alter scripts, page content, privacy controls, or network requests.
• If the page is stuck loading or repeatedly returns to sign-in, clear stored site data for the Gemini web app.

If Gemini works in a private window or another browser, the original browser's cookies, cached site data, extensions, or stored session are the most likely areas to investigate.

3. If sign-in or account access fails

A sign-in loop, permission message, or missing access can affect one Google account or session without indicating a general Gemini outage. Confirm that the intended Google account is selected, then sign out and sign back in. A private-window test can help separate account access from stored session data.

If the same account fails across browsers and networks while another account works, preserve the exact message and treat the issue as account- or access-specific rather than assuming Gemini is down.

4. If Gemini loads but prompts or responses fail

Loading the interface does not guarantee that prompt submission or response generation is working. Try one short request in a new conversation and note whether the problem affects every conversation or only one request.

A single failed response may be transient or request-specific. Failures that reproduce across browsers and networks are stronger evidence of a service-side or account-level problem. Compare the timing with the official status page before making extensive local changes.

5. If the API fails while the web app works

Assess API access separately through generativelanguage.googleapis.com. Check the request endpoint, authentication or API-key configuration, selected model or operation, returned HTTP status, and any quota or request error from the client. A successful browser session does not validate an individual API request.

If the API fails in only one runtime or environment, compare it with a second network or runtime and inspect DNS, proxy, firewall, and TLS settings. If the same error occurs across environments, preserve the complete response and timestamp for service-status checks or support investigation. Do not include API keys or other credentials when sharing diagnostic details.

6. If the error indicates a network or TLS problem

DNS failures, connection refusals, timeouts, and TLS errors can prevent a request from reaching Gemini. Test another network where practical and check whether other sites work from the affected device. If the service works on another connection, investigate the original network's DNS, VPN, proxy, firewall, or security filtering.

A connection restart may help with a temporary local network failure, but perform it separately from diagnostics and only when you are authorized to interrupt the connection. If only one device or network is affected, a local configuration problem is more likely than a broad Gemini outage.