Loading status…
Loading status…
Firebase status · Data & Backend · checked (4m ago)
Also searched as Google Firebase, Firestore, Firebase Auth.
No — Firebase is not down. All Firebase systems are reported operational.
According to Firebase's official status page, Firebase was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, Firebase's feed reported no outage in 100.00% of our checks.
Everything above is read from Firebase's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported Firebase in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
Firebase is Google's app development platform: Firestore and the Realtime Database, Authentication, Cloud Functions, Hosting, Cloud Messaging, Crashlytics and Remote Config. It is used heavily in mobile apps, so a Firebase incident often surfaces as an app that will not sign users in.
Firebase publishes a JSON list of incidents rather than a current-status indicator, so its state has to be derived: isuptime reads the incident list and treats anything without an end time as ongoing. Google grades those incidents as service disruption or service interruption, which map to degraded and outage here. One consequence is that Firebase reads as operational whenever no incident is open — there is no amber aggregate to fall back on.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
One bar per day. Each shows the share of that day's checks where Firebase's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days Firebase was down.
9 other services isuptime tracks were also reporting a problem as of the same check, 4m ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of Firebase's status endpoint.
Firebase has published 25 incidents in the last 12 months, the 20 most recent shown here. Only what Firebase posted itself — not every problem users hit.
AVAILABLE · Sep 22, 04:51 PM (1d ago)
AVAILABLE · Sep 22, 04:25 PM (1d ago)
AVAILABLE · Sep 22, 04:06 AM (1d ago)
AVAILABLE · Sep 21, 07:40 PM (1d ago)
AVAILABLE · Sep 16, 07:25 PM (7d ago)
AVAILABLE · Sep 10, 07:16 AM (13d ago)
AVAILABLE · Sep 1, 10:29 AM (22d ago)
AVAILABLE · Aug 20, 03:08 PM (34d ago)
AVAILABLE · Aug 17, 10:58 PM (36d ago)
AVAILABLE · Aug 13, 05:56 PM (41d ago)
AVAILABLE · Aug 11, 01:17 PM (43d ago)
AVAILABLE · Jul 31, 03:38 AM (54d ago)
AVAILABLE · Jul 21, 06:11 PM (64d ago)
AVAILABLE · Jul 20, 03:39 PM (65d ago)
AVAILABLE · Jul 14, 08:38 PM (70d ago)
AVAILABLE · Jul 13, 03:42 PM (72d ago)
AVAILABLE · Jul 4, 02:45 PM (81d ago)
AVAILABLE · Jun 15, 06:03 PM (100d ago)
AVAILABLE · Jun 11, 05:20 AM (104d ago)
AVAILABLE · Jun 1, 09:36 PM (113d ago)
Firestore security rules rejecting reads look exactly like a backend outage from inside an app. So does an expired service account key, and so does exceeding the free-tier quota on the Spark plan. Check the Firebase console's usage tab before assuming the platform is at fault. Firebase also depends on wider Google Cloud infrastructure, so a Google Cloud regional incident can affect you before Firebase's own feed says anything.
Firebase is reporting no problems right now. If it stops, these cover the same job — each shows its own live status.
Status shown for each is read from that provider's own feed, on the same schedule as this page.