# How to Monitor Firebase Uptime

> Firebase is Google's app development platform providing authentication, Firestore database, hosting, cloud functions, storage, and analytics.

*Source: https://monitoristic.com/monitor/firebase*

---

## Why Monitor Firebase?

Firebase services are independent — Firestore can be down while Auth works fine, or Cloud Functions can timeout while Hosting serves pages normally. Since Firebase apps typically depend on multiple services simultaneously, a partial outage breaks your app in ways that are hard to diagnose without monitoring each piece.

## What to Monitor

- `your-app.web.app` — Your Firebase Hosting URL
- `your-app.firebaseapp.com` — Default Firebase app domain
- `us-central1-your-project.cloudfunctions.net/health` — Cloud Functions health endpoint

## What You Should Actually Do

1. Monitor your Firebase Hosting URL to catch deployment failures and CDN issues
2. Create a Cloud Function health endpoint that tests Firestore reads — this catches backend outages that don't affect the static shell
3. Track response times on Cloud Functions — cold start spikes are common and can make your app feel broken during low-traffic periods
4. Set up alerts for weekends and off-hours — Firebase outages don't respect your work schedule
5. Monitor your custom domain separately from your .web.app domain — DNS and SSL issues on custom domains won't affect the default Firebase domain

## Firebase's Official Status Page

Firebase publishes real-time status at https://status.firebase.google.com. Your own monitor complements it by catching connection-level issues, often before the status page updates.

## Takeaway

Firebase apps have a unique failure mode: the static shell loads perfectly while the backend is broken. Users see your app, interact with your UI, and think it's buggy — not that the infrastructure is down. External monitoring that tests actual functionality, not just page loading, is the only way to catch these partial failures.

## Frequently Asked Questions

### Can I monitor Firebase Cloud Functions?

Yes. Create a simple HTTP Cloud Function that performs a health check (reads from Firestore, checks auth) and returns 200. Monitor that function's public URL. When the function fails, you know which backend service is down.

### Why does my Firebase app look fine but not work?

Firebase Hosting serves static files from a CDN — it's almost always up. But Firestore, Auth, and Cloud Functions are separate services that can fail independently. Your app's shell loads, but data and functionality break. External monitoring catches this.

### Should I monitor firebase.google.com?

No — that's the Firebase marketing site. Monitor your own app's URLs: your-app.web.app, your custom domain, and your Cloud Function endpoints. These are what your users actually access.

### How is this different from status.firebase.google.com?

Firebase's status page reports platform-wide incidents by service and region. Your monitor checks YOUR specific app. Quota exhaustion, cold start spikes, deployment mismatches, and project-level issues don't appear on the platform status page.