Missing means unknown.
Unavailable or malformed feeds do not become an all-clear. Failed refreshes mark retained reports stale immediately. Look at retrieval timestamps, source errors and scope.
OFFICIAL REPORTS · EXPLICIT COVERAGE
A homepage is up.
What about the API?
Read official provider incidents and product component reports. Separate an API, login or developer-tool issue from a working homepage.
Reports, not assumptions.
Product scope matters.
Google Cloud, Workspace and Search are separate feeds. Their reports do not establish Gemini developer API health. Consult AI Studio status for that product.
Component reports are separate.
Official component summaries are available for Claude, OpenAI, Cloudflare, GitHub and Wikimedia. Google component summaries are not ingested. A name filter with no match is unknown, not operational.
Freshness and limitations
Reports refresh on demand at most once per minute per source, with a 30-second edge cache. They become stale after 120 seconds. OpenAI uses recent published history, which may omit older incidents. Scheduled maintenance and customer-specific impact are not comprehensively assessed. Provider reports are not independent measurements or proof of causation.
Need measured homepage evidence? See scheduled observations. Agents can use get_provider_components, get_provider_incidents and investigate_incident with no API key. Use the source timestamps to judge how current each report is.