Something feels slow, broken or unavailable in Gemini? Check the source and freshness before drawing a conclusion.
What the evidence says
Monitoring not activated. No current independent evidence.
- Official Gemini app
- Official status unknown
- Official Gemini API
- Official status unknown
- Independent Gemini API
- Insufficient evidence
API checks do not measure the consumer app.
Monitoring not activated. No verified current independent snapshot is available.
Official Gemini app status
Official status unknown
No verified current component evidence.
Source checked: Unavailable · unavailableOfficial Gemini API status
Official status unknown
No verified current component evidence.
Source checked: Unavailable · unavailableIndependent Gemini API checks
Insufficient evidence
Latency comparison: insufficient evidence
Latest check slot: Unavailable
0 / 3 fresh regions · current regional evidence unavailableAPI checks do not measure the consumer app. Official reports and independent observations may disagree. Missing evidence does not mean an outage.
Independent checks: every 5 minutes when activated; unavailable after a missed expected check plus 60 seconds. Official evidence expires after 90 seconds. Each source ages separately.
Gemini official status is UNKNOWN here: no approved machine-readable source. Official AI Studio status reference (check its stated scope).
What these sources cover
No approved stable machine-readable Gemini official status feed has been verified. The AI Studio status page is an official reference, not proof of Gemini consumer-app status. We do not scrape it or substitute Google Cloud status.
Official consumer components, official API components and independent API checks are three separate sources. An overall provider indicator is not a substitute for a matching component. No incident reported is limited to the supported official components and fresh supplied incident coverage; it is not proof that every user can connect.
Why can the service feel slow without an incident?
A long conversation, a different model, account limits, a local network path or app routing may affect your experience. These are possible explanations, not diagnoses. We only label elevated API latency after repeated comparable checks exceed a distributed baseline. Without enough baseline evidence, speed remains inconclusive.
One successful request does not rule out intermittent failures. One failed request does not establish a consumer-app outage. Missing regions and expired observations remain visible.
Performance history
Reports describe completed API measurement periods, not current consumer-app status.
- Daily: no complete verified report yet
- Weekly: no complete verified report yet
- Monthly: no complete verified report yet
Archive: verified historical evidence
Earlier bounded observation (not a complete Daily, Weekly or Monthly report): AI Performance Observation Report: 2026-10-02–2026-10-03
Calendar reports use America/New_York local dates, including daylight-saving changes. Publication requires a closed period, complete expected slots, immutable source verification, reconciled accounting and explicit publication permission. Partial periods are not completed reports.