Skip to main content

Is Firebase Down?

No — Firebase is up

Reachable from all 8 checked regions

Average response time: 918ms

Last checked · checks run every 6 hours

Official status page: https://status.firebase.google.com

Firebase uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
780ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 20 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

20-day clean streak
Jul 19: no data
Jul 20: no data
Jul 21: no data
Jul 22: no data
Jul 23: no data
Jul 24: no data
Jul 25: no data
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: 100.00% uptime, 8 checks
Jul 30: 100.00% uptime, 32 checks
Jul 31: 100.00% uptime, 32 checks
Aug 1: 100.00% uptime, 32 checks
Aug 2: 100.00% uptime, 30 checks
Aug 3: 100.00% uptime, 32 checks
Aug 4: 100.00% uptime, 31 checks
Aug 5: 100.00% uptime, 24 checks
Aug 6: 100.00% uptime, 32 checks
Aug 7: 100.00% uptime, 32 checks
Aug 8: 100.00% uptime, 32 checks
Aug 9: 100.00% uptime, 32 checks
Aug 10: 100.00% uptime, 32 checks
Aug 11: 100.00% uptime, 40 checks
Aug 12: 100.00% uptime, 24 checks
Aug 13: 100.00% uptime, 32 checks
Aug 14: 100.00% uptime, 32 checks
Aug 15: 100.00% uptime, 32 checks
Aug 16: 100.00% uptime, 32 checks
Aug 17: 100.00% uptime, 24 checks
Jul 19 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

gru
990ms
DNS 0ms TCP 2ms TLS 58ms TTFB 555ms
iad
402ms
DNS 0ms TCP 2ms TLS 5ms TTFB 322ms
jnb
1544ms
DNS 0ms TCP 2ms TLS 162ms TTFB 698ms
lax
1332ms
DNS 0ms TCP 0ms TLS 12ms TTFB 1250ms
lhr
618ms
DNS 0ms TCP 1ms TLS 7ms TTFB 398ms
nrt
1187ms
DNS 0ms TCP 1ms TLS 7ms TTFB 887ms
ord
456ms
DNS 0ms TCP 1ms TLS 14ms TTFB 396ms
sin
1345ms
DNS 0ms TCP 1ms TLS 8ms TTFB 582ms
sjc
465ms
DNS 0ms TCP 2ms TLS 24ms TTFB 311ms

What Firebase does

Firebase is Google's application development platform, providing the backend pieces mobile and web apps would otherwise build themselves: authentication, a hosted database, file storage, push messaging and crash reporting. Because sign-in and data both run through it, a Firebase incident tends to stop an app working entirely rather than degrading one feature of it.

What an outage looks like

Users cannot sign in, and apps that require authentication at launch hang on a splash screen or loop back to the login form. Reads and writes against Realtime Database or Firestore time out, so lists load empty and saved changes never appear on other devices. Push notifications through Cloud Messaging stop arriving, and Crashlytics reports go quiet, which can hide the problem from you.

What to do about it

Check status.firebase.google.com, which lists roughly 25 products separately, including Authentication, Realtime Database, Hosting, Cloud Messaging, App Check and Crashlytics, so a Crashlytics incident tells you nothing about whether sign-in works. Client SDKs cache data locally and retry, so avoid shipping an emergency release before confirming which product is actually affected.

Is it down for everyone, or just you?

If this page says Firebase is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

AWS
AWS
Supabase
Supabase
MongoDB Atlas
MongoDB Atlas
Vercel
Vercel

Firebase outage FAQ

Is Firebase down or is my app misconfigured?
Firebase's dashboard reports each product on its own line, so match the symptom to the product before touching code. Sign-in failures point at Authentication, missing data at Realtime Database or Firestore, and silent notifications at Cloud Messaging. If every product is green, suspect your API keys, security rules or App Check enforcement, all of which fail in ways that look identical to an outage from inside the app.
Does a Firebase outage affect Google Cloud too?
Often, because Firebase runs on Google Cloud infrastructure and several products are the same service under a different name. Firestore and Cloud Functions in particular appear on both Google Cloud's dashboard and Firebase's. If Firebase reports an incident, check whether your other Google Cloud dependencies sit in the same region before concluding the two problems are unrelated.
Will data written during a Firebase outage be lost?
Usually not. The Firebase client SDKs keep a local cache and queue writes, so changes made while the device cannot reach the backend are generally sent once connectivity returns. The risk is ordering rather than loss: queued writes land later than users expect, and anything depending on a server timestamp or a transaction may resolve differently from what the user saw on screen.
Can users still use my app if Firebase Authentication is down?
Anyone already signed in usually can, for a while. Firebase issues ID tokens that stay valid for about an hour, so an existing session keeps working until the token needs refreshing, while new sign-ins fail immediately. That gap is why an Authentication incident often looks like it only affects some users, and why the impact widens the longer it runs.
How do I know if Firebase is down when Crashlytics is silent?
Treat the silence as a symptom. Crashlytics is itself a Firebase product with its own status line, so an incident there means crash reports stop arriving even though your app may be failing badly. Never read an empty Crashlytics dashboard as evidence of health during a Firebase incident; confirm against the status page and your own server-side logs instead.

How we measure this

  • We request Firebase's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Firebase publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Firebase goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required