90 days uptime
100.000%
90 of 90 days clean · 0m total downtime
All windows
Last resolved incident
103 days ago · lasted 1h 58m · Minor
Predicted resolution
low data · n=1~118m (p25 118m – p75 118m)
Based on 1 historical Major incidents · currently 2174m elapsed.
6/9/2026, 6:22:00 PM · in progress · Identified
2/27/2026, 12:37:00 PM · resolved 2/27/2026, 2:35:00 PM · Resolved
7/18/2025, 2:42:00 PM · resolved 7/18/2025, 4:47:00 PM · Resolved
Official status page: https://status.cloud.google.com (opens in new tab)
Live status pill for GCP Firestore. Updates automatically — no maintenance, no API key.
PREVIEW
Drop into any HTML page — README, docs, vendor homepage. No iframe, no dependencies.
<script src="https://checkupstream.com/embed/badge.js?service=gcp-firestore"></script>Self-contained, CSP-friendly. Theme + size are query params; revalidates every 60s.
<iframe src="https://checkupstream.com/embed/gcp-firestore" style="border:0;width:260px;height:44px" loading="lazy" title="GCP Firestore status badge"></iframe>GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
[](https://checkupstream.com/reliability/gcp-firestore)Useful for status-page composers (Notion, Slab, custom dashboards) that accept image URLs.
https://checkupstream.com/embed/gcp-firestore/badge.svgGCP Firestore is currently Partial Outage. 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.
Looking for the live "is GCP Firestore down" view? See the GCP Firestore Status page.
6/12/2025, 5:51:00 PM · resolved 6/13/2025, 1:18:00 AM · Resolved
GCP Firestore's last resolved incident started 103 days ago and lasted 1h 58m (degraded performance).
GCP Firestore's 30-day customer-perceived uptime is 100.000%. The figure is weighted (full-outage = 1.0, degraded = 0.3) so component blips don't collapse the score the way a raw incident-count would.
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).
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.