Databases & Storagefirebase.google.com

Is Google Firebase (Firestore / RTDB) Down Right Now?

Live global uptime status, multi-region edge latency, official incident reports, and automated monitoring for Google Firebase (Firestore / RTDB).

G

Google Firebase (Firestore / RTDB)

firebase.google.com

Google app development platform featuring Cloud Firestore, Realtime Database, and Cloud Functions.

Operational
Edge Latency
412 ms

Primary edge roundtrip

24h Global Uptime
99.98%

Edge consensus

Vantage Points
7 Regions

NA, EU, APAC Edge DOs

Last Checked
6:32:50 PM

Edge consensus mesh

Telemetry verified by SteadyStack Autonomous Edge Network
Official Status
Automated Developer Alerting

Stop checking manually.

When Google Firebase (Firestore / RTDB) goes down or suffers silent latency degradation, you shouldn't be refreshing status pages, searching social feeds, or waiting for angry user reports. Get alerted the exact second Google Firebase (Firestore / RTDB) fails.

Monitor Google Firebase (Firestore / RTDB) in 1 Click

Free 50 monitors • 3m standard (1m for first 10) • 2-of-3 Edge Quorum • No credit card required

10-Second Edge Intervals

Continuous HTTP, WebSocket & DNS checks from 15+ global edge nodes.

4-of-7 Quorum Verification

Multi-region consensus verification prevents 3 AM wakeups from transient routing blips.

Multi-Channel Escalation

Instant alerts to Slack, Discord, Telegram, SMS, PagerDuty & Webhooks.

steadystack.config.ts
Auto-provisioned Monitor
import { defineMonitor } from "@steadystack/core";

export default defineMonitor({
  name: "Google Firebase (Firestore / RTDB) API & Health",
  target: "https://firebase.google.com",
  interval: "10s",
  consensus: { requiredRegions: 3 },
  alerts: ["slack-dev-ops", "pagerduty-p1", "discord-incidents"],
});

Global Edge Reachability & Regional Latency

Synthetic probe response times tested from SteadyStack worldwide vantage points.

🇺🇸
US-East (N. Virginia)
us-east
186 ms
UP
🇺🇸
US-West (Oregon)
us-west
208 ms
UP
🇩🇪
EU-Central (Frankfurt)
eu-central
247 ms
UP
🇯🇵
AP-Tokyo (Tokyo)
ap-northeast
315 ms
UP
🇧🇷
SA-East (São Paulo)
sa-east
322 ms
UP
🇿🇦
AF-South (Cape Town)
af-south
380 ms
UP

Downtime Impact Analysis

What happens when Google Firebase (Firestore / RTDB) degrades

Firestore real-time listeners stop firing, push notifications fail to deliver, mobile logins break.

Common HTTP Error Codes Observed

UNAVAILABLE: The service is currently unavailableDEADLINE_EXCEEDEDRESOURCE_EXHAUSTED

Critical Monitored Subsystems

Components tracked on firebase.google.com

Cloud Firestore
Synthetic Active
Firebase Realtime Database
Synthetic Active
Firebase Cloud Messaging (FCM)
Synthetic Active
Firebase Auth
Synthetic Active
Cloud Functions for Firebase
Synthetic Active

Engineering Resilience Guide: Surviving Google Firebase (Firestore / RTDB) Outages

Defensive software architecture patterns to prevent third-party cascade failures.

Immediate Tactical Steps

  • 1Check status.firebase.google.com.
  • 2Verify Firestore security rules and index definitions.

Recommended Resiliency Patterns

Circuit Breaker Pattern: Automatically trip and fallback to cache when Google Firebase (Firestore / RTDB) error rates exceed 15% in a 30s rolling window.

Idempotent Background Retries: Push failed API events into an asynchronous dead-letter queue with exponential backoff and jitter.

Multi-Region Edge Synthetic Consensus: Rely on SteadyStack to alert your team before end-users notice degradation.

Frequently Asked Questions: Google Firebase (Firestore / RTDB) Availability & Monitoring

Everything you need to know about tracking Google Firebase (Firestore / RTDB) outages and SLA reliability.

Our real-time global edge probes continuously test Google Firebase (Firestore / RTDB) (firebase.google.com) across multiple worldwide locations. You can check the live status badge and latency meter at the top of this page. If you are seeing errors while the global status is operational, it may be due to localized ISP routing, local DNS caching, or account-specific rate limiting.