Firebase statusManual checkVerified May 24, 2026Source: status.firebase.google.com
Is Firebase down?
Live status check · No widespread incident reported.
Most recent manual verification mirrored from status.firebase.google.com. Below: the components that can break, what to do during an incident, and how to keep your scheduled jobs running independently.
About Firebase status
Firebase sits on top of Google Cloud. Most incidents map to a specific service — Auth, Firestore, Cloud Functions, Hosting, Realtime Database — and to a specific region. The status page is one of the better in the industry, with clear per-component history.
Components and surfaces that can break
- Surface 01
Authentication (sign-in, custom claims, token refresh).
- Surface 02
Firestore, Realtime Database, Storage.
- Surface 03
Cloud Functions (HTTP, callable, scheduled), Hosting, App Check.
Recent Firebase incidents
Firebase maintains a public incident history. Read the latest entries to see whether you're hitting a known issue, and look at the post-mortems for context on how long similar incidents typically take to clear.
What to do if Firebase is actually down
Check both Firebase and Google Cloud status
Firebase Cloud Functions actually run on Google Cloud Functions. If status.firebase.google.com looks green but functions are timing out, check status.cloud.google.com as well — the root cause may be a Cloud Run or networking incident.
Cache Auth tokens client-side for short outages
If Firebase Auth degrades, valid ID tokens already in client memory remain useful until they expire (1 hour by default). Avoid forcing a sign-out on every API failure or you'll lock out users unnecessarily.
Confirm Scheduled Functions on Blaze are still firing
Cloud Scheduler triggers Scheduled Functions under the hood. If Cloud Scheduler is degraded in your region, scheduled runs are quietly skipped and not retried. You need an external watcher to detect this.
Keep firing through the incident
Schedule your own Firebase health check with Crontap
Firebase Scheduled Functions require the Blaze (pay-as-you-go) plan and live on Cloud Scheduler. Crontap calls your function URL on the same cadence without requiring a billing upgrade, and works on Spark plan projects too.
External HTTP cron hits your endpoint on the cadence you pick, stores every response, and emails you the moment a run fails. Pro schedules down to 1 minute; $3.25/mo annual flat for unlimited jobs.
Go deeper
Firebase status: FAQ
- How do I check Firebase status by service and region?
- status.firebase.google.com has a per-product matrix. Each cell is clickable and opens the incident history for that specific service and region. The JSON feed at /incidents.json is good for scripting your own status mirror.
- Why doesn't Firebase Scheduled Functions retry missed runs?
- Scheduled Functions run on Cloud Scheduler with at-most-once semantics by default. If the platform skips a fire, Firebase does not catch up later. Configure max retry attempts in the Cloud Scheduler console — or run the same handler URL from an external cron with retries built in.
- Can I trigger Firebase Functions from outside without going to Blaze?
- Yes — HTTP-triggered functions can be called from any HTTP client. Crontap calls the function URL on your schedule, and you stay on the Spark plan. See our Firebase scheduled functions without Blaze post for the full setup.