Is Firebase Down? How to Check Firebase Status Right Now

Firebase is the backend for millions of apps — Firestore, Auth, Realtime Database, Hosting, Cloud Functions, and more. When Firebase goes down, your app goes silent: authentication breaks, data stops syncing, and users hit errors they can't explain. Here's how to diagnose quickly.

Is Firebase Down Right Now?

Check these sources in order:

1. Statusfield — Firebase status — real-time monitoring, updated continuously.
2. Twitter/X — search Firebase down sorted by Latest. Developer outage reports are fast and informative.
3. Downdetector — aggregates user-reported outage spikes.

What Actually Breaks During a Firebase Outage

Firebase is a suite of services that can fail independently:

Common Firebase Error Symptoms

Why Firebase Goes Down

Google Cloud regional issues. Firebase runs on Google Cloud. A failure in a GCP region (us-central1, europe-west1, etc.) can affect Firebase services in that region. Firestore is multi-region by default for some configurations but single-region for others.

Shared infrastructure at scale. Firebase serves an enormous number of apps. Infrastructure issues that affect even a small percentage of capacity can translate to millions of affected users.

Cloud Functions cold start storms. Viral app traffic spikes can trigger mass concurrent cold starts in Cloud Functions, sometimes contributing to throttling that looks like an outage.

Dependency on Firebase Auth + Google Identity. Firebase Auth depends on Google's identity platform. If Google Identity has an issue, auth across all Firebase apps in affected regions fails simultaneously.

What to Do When Firebase Is Down

Immediate steps:

1. Identify the specific service — is it Firestore, Auth, Functions, or something else? Check Statusfield for which service component is affected.
2. Check your region — if you're using a single-region Firestore, only that region's users are affected. Multi-region databases have more resilience but also more complex status to check.
3. Use Firestore's offline persistence — if you enabled offline persistence in your Firestore client, reads continue to work from local cache. Writes are queued and sync automatically once service restores.
4. For Auth outages — if Firebase Auth is down, users already logged in (with valid tokens) can often continue using the app if you gracefully handle token refresh failures. New logins and signups will fail.

For engineering teams:

Watch your Cloud Functions execution logs closely during a Firebase outage. Functions often generate high error rates that can push you toward Cloud Function quota limits — combine the outage impact with a potential quota issue on recovery.

Building Firebase-Resilient Applications

Enable Firestore offline persistence

The most impactful single change for Firebase resilience:

import { initializeFirestore, persistentLocalCache } from 'firebase/firestore';
 
const db = initializeFirestore(app, {
  localCache: persistentLocalCache()
});

With offline persistence, your app continues to function for read operations during Firestore outages and queues writes automatically.

Handle Auth token refresh failures

Firebase Auth tokens expire every hour and refresh automatically. If Auth is degraded, token refresh fails silently. Handle this explicitly:

auth.onAuthStateChanged((user) => {
  if (!user) {
    // Could be signed out OR token refresh failed during an outage
    // Check Firebase status before forcing re-login
    checkFirebaseStatus().then(isDown => {
      if (!isDown) redirectToLogin();
      // If Firebase is down, show a "service temporarily unavailable" message
    });
  }
});

Monitor Firebase service health as part of your app health

Your app's health is only as good as Firebase's health. Statusfield's Firebase monitoring tracks Firebase's service status independently of your own application metrics.

How to Get Instant Firebase Outage Alerts

Monitor Firebase on Statusfield and get alerted the moment any Firebase service changes status. Route alerts to email or webhook so you know before your users start filing support tickets.

Start monitoring Firebase →

Frequently Asked Questions

Is Firebase down for everyone or just me?

Check Statusfield. Firebase issues are often regional — your region's Firestore may be down while other regions are fine. If status pages show all clear, check your Firebase project's quota usage and your Firestore security rules, as those can look identical to an outage.

Firestore writes are failing with "unavailable" — is Firebase down?

The unavailable error typically means Firestore's backend is experiencing issues. Check Statusfield for Firestore status in your region. If status shows operational, check your Firestore quota — you may have hit your daily write limits, which produces the same error.

Firebase Auth works but Firestore is down — how do I handle this?

Serve cached data where possible and queue writes locally. If you enabled offline persistence, Firestore handles this automatically. For real-time-critical features, show users a "Service temporarily degraded" banner rather than failing silently.

My Cloud Functions stopped triggering — is this a Firebase outage?

Check Statusfield for the Cloud Functions component status. Also check your Cloud Functions logs in the Firebase console — sometimes functions fail due to code errors or dependency issues that look like an outage. If the status shows Cloud Functions degraded, wait and retry.

How do I get notified when Firebase goes down?

Set up Firebase monitoring on Statusfield. You'll get alerts via email or webhooks the moment Firebase reports a service incident — so you can post a status update to your users before they report the bug.

Does Firebase have maintenance windows?

Firebase rarely has scheduled maintenance windows that cause user-facing downtime. Most maintenance is transparent.