Last updated: November 9, 2026
Is Firebase down? User reports indicate possible problems with Firebase
Firebase is Google's app development platform with Firestore, Authentication, Hosting, Cloud Functions, and Storage used by millions of apps. This page tracks product outages, console failures, quota problems, and error reports from Firebase developers.
Report a problem !
Select which issue applies
Firebase problems reported in the last 24 hours
Most reported problems
All quiet. No issues reported in the last 24 hours.
Your feedback
How would you rate Firebase over the past 3 months?
Most reported locations
Where Firebase reports are coming from in the last 24 hours.
No problem locations to show yet. Firebase looks fine right now. Locations appear here as soon as users submit reports.
Latest Firebase user reports
No reports yet — be the first to report a problem above.
Firebase outage history
Our latest check and the live report status for Firebase.
✓ Our latest check (8 November 2026, 4:13 AM PKT): firebase.google.com answered normally in 566 ms.
Good news. Firebase has no reported problems right now. If it is not working for you, report it above and your report will appear here.
Firebase uptime and reports
Live report counts and the day by day record for the last 30 days.
User reports received in each period.
Last 30 days, day by day: 10 October 2026 to 8 November 2026
Green: up. Red: outage. Amber: some checks failed. Grey: no record yet.
The daily record builds from today as our checks run. Grey days have no saved record yet. A red day marks a confirmed outage.
Get Firebase down alerts
Leave your email and we will tell you when Firebase is having problems. One email per outage, no spam.
Firebase on social media
An early signal from outside our site, watched in rotation.
Posts on Bluesky saying Firebase is down. Checked 8 November 2026, 1:58 PM PKT.
Quiet right now. Nobody on Bluesky is saying Firebase is down.
Guides that can fix it
Step by step fixes for the problems people report most.
→ An App Is Not Working? Fixes for Android and iPhone
→ Login Problems That Are Not an Outage
→ How to Clear the Cache in Firefox, Safari and Edge
Is Firebase Down Right Now?
No major Firebase outage is active right now. The Firebase status above tracks live reports across all Firebase products. Because Firebase sits on Google Cloud, a Google Cloud incident often breaks Firebase apps too. Past events hit Firestore, Hosting, and Authentication at the same time. Check the report graph first. A steep rise usually means a regional Google Cloud problem.
Firebase is a bundle of services, not one system. Firestore, Realtime Database, Authentication, Hosting, Functions, and Storage can each fail alone. Your app may lose login while its data loads fine. Name the exact product that fails before you search for a fix, because each one has its own status and its own common faults.
Is Firebase Down for Me or Everyone?
A quick check shows if Firebase is down for me or everyone. Open your app on a second network and watch which parts load. If login works but data does not, only one product is affected. The Firebase console gives the same clue. If the console fails too, the incident is wide. If the console works, review your project rules, quotas, and keys.
Firestore Reads and Writes Failing
Firestore errors spike during regional Google Cloud incidents in places like us-east1. Apps show permission or unavailable errors even with correct rules. Before you rewrite security rules, check whether other developers report the same errors today. Quota limits cause a quieter failure. Free plan projects that outgrow daily reads simply stop answering until the next day or a plan upgrade.
Authentication Errors That Lock Users Out
Sign-in failures draw the loudest Firebase down reports. Auth breaks when a Google Cloud identity service degrades, and every app feels it at once. Local causes exist too. A wrong API key, a blocked domain in the authorized list, or a changed app signature stops sign-in for one project only. The error code in the console separates platform faults from project faults.
Hosting Deploys That Fail or Serve Old Sites
A deploy can finish with errors or leave the old version live. Large file counts and slow networks break uploads near the end. Cache layers then keep serving the older release to visitors. The release history in the console shows which version is truly live. A rollback to the last good release is faster than a blind second deploy during an incident.
Common Firebase Problems and Fixes
Firestore returns unavailable errors
Check if other projects in the same region report the same errors today. If yes, wait out the regional incident and avoid rule changes. If only your project fails, review quotas and billing. A project over its daily quota stops until reset or upgrade.
Users cannot sign in
Read the exact auth error code in the browser console. Confirm the domain is on the authorized domains list in the console. Check that the API key in your app matches the project. If codes point to a server fault across projects, treat it as an incident.
Firebase console will not load
Try the console from another network and a private window. A console failure plus app failures signals a wide incident. If the console loads elsewhere, your network or browser cache is at fault. Clear site data for the console domain and retry.
Hosting deploy fails
Read the deploy log for the first error line, not the last. Cut huge folders like backups from the deploy path. Retry the deploy on a stable connection. Use the release history to roll back if the live site broke.
Cloud Functions time out
Check the function logs for cold start delays and slow downstream calls. Raise the timeout and memory for heavy jobs. A function that waits on a sick service will time out with it. Add retries for short platform hiccups.
Having a problem with Firebase?
Comments are public and help others understand the issue.
Frequently Asked Questions
Why does Firestore say unavailable?
A regional incident or a blown quota causes most unavailable errors. Check whether other projects in your region fail too. If only yours fails, review daily quotas, billing, and security rules.
Can a Google Cloud outage break Firebase?
Yes. Firebase runs on Google Cloud, so a regional cloud incident can hit Firestore, Auth, and Hosting together. Apps in other regions often keep working during the same event.
Why did Firebase Authentication stop working?
Platform incidents, a removed authorized domain, or a wrong API key all break sign-in. Read the error code first. Codes shared across many projects point to an incident, while project-only errors point to config.
Why is my Firebase Hosting site showing the old version?
The deploy may have failed partway, or caches still serve the older release. Check release history in the console to see the live version. Roll back or redeploy once the platform is stable.
What does the Firebase quota exceeded error mean?
Your project passed a plan limit, such as daily database reads on the free plan. Service pauses until the quota resets or you upgrade. Watch usage in the console to avoid a repeat.
How do I tell which Firebase product is down?
Test each part of your app in turn: sign-in, data reads, file loads, and hosted pages. The failing part names the product. The console status for that product confirms how wide the problem runs.