CheckUpstream does not yet run an independent probe against GCP Firestore, so no availability figure is published for it — only GCP Firestore's own disclosure record below. 2 incidents were recorded in the past 12 months; the most recent resolved 11 days ago after 27 minutes. Status signals are polled from GCP Firestore's official status feed, alongside independent probes and community reports.
We run no independent probe against GCP Firestore yet, so we publish no availability figure for it. What follows is GCP Firestore's own disclosure record, which is a different thing.
Vendor disclosed: 2 incidents · 364 of 365 days with none posted · 30m of declared impact
Fewer incidents in the last 30 days than 34% of 232 tracked services.
Share of each window with no impact declared by GCP Firestore
7d
100.000%
30d
99.931%
90d
99.977%
180d
99.988%
1y
99.994%
Downtime like this can be refundable
If you're a paying GCP Firestore customer, outages in these windows may count against GCP Firestore's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
A GCP Firestore outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
UPDATE: We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region.
Major
Aug 20, 18:53 UTC · resolved in 26m · Resolved
UPDATE: We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region.
GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Frequently Asked Questions
›Is GCP Firestore currently down?
GCP Firestore is currently Operational. CheckUpstream tracks GCP Firestore in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
GCP Firestore's last resolved incident started 11 days ago and lasted 26 minutes (a partial outage).
›What's GCP Firestore's 30-day uptime?
We don't publish one. CheckUpstream runs no independent probe against GCP Firestore yet, and the only other figure available would be derived from GCP Firestore's own incident posts — which measures how much a vendor discloses rather than how available it was. Vendors that post often score worse than vendors that stay quiet, so the number would be backwards.
›How do I monitor GCP Firestore in production?
Sign up to CheckUpstream and add GCP Firestore to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
›How does CheckUpstream track GCP Firestore?
We poll GCP Firestore's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.