Is Firebase Down?
Real-time status check for firebase.google.com
Checking status...
About Firebase Status
BlueMonitor checks Firebase (firebase.google.com) by sending automated requests to its servers. If the service responds within a normal timeframe and returns a successful status code, it's marked as operational. Response times over 3 seconds indicate the service is slow, and connection failures or server errors indicate the service may be down.
Recent Incidents
RESOLVED: Firebase AI Logic is seeing an elevated RESOURCE_EXHASUTED error rates from both Vertex AI and Generative AI servers.
Incident began at 2026-04-09 05:01 and ended at 2026-04-09 15:00 (all times are US/Pacific ). Problem appears to be mitigated and the error rates are back to normal level. Affected products: Firebase AI Logic
RESOLVED: Physical device tests are delayed and stuck pending
Incident began at 2026-04-09 09:59 and ended at 2026-04-09 14:00 (all times are US/Pacific ). We believe we've addressed the issue and stuck tests will now run. They may still be delayed as the system works through the queue Affected products: Test Lab
UPDATE: Firebase AI Logic is seeing an elevated RESOURCE_EXHASUTED error rates from both Vertex AI and Generative AI servers.
Incident began at 2026-04-09 05:01 and ended at 2026-04-09 15:00 (all times are US/Pacific ). No updates so far Affected products: Firebase AI Logic
UPDATE: Physical device tests are delayed and stuck pending
Incident began at 2026-04-09 09:59 and ended at 2026-04-09 14:00 (all times are US/Pacific ). We've redirected our traffic so newly created tests should run. We're still investigating and working to fix currently stuck tests Affected products: Test Lab
UPDATE: Physical device tests are delayed and stuck pending
Incident began at 2026-04-09 09:59 and ended at 2026-04-09 14:00 (all times are US/Pacific ). We're investigating the issue and determining the cause Affected products: Test Lab
RESOLVED: Firebase Studio App Hosting deployment disruption
Incident began at 2026-03-10 10:51 and ended at 2026-03-31 00:00 (all times are US/Pacific ). This should be resolved for all customers. Please contact Firebase Support if you encounter this issue again. Affected products: Firebase Studio
RESOLVED: Minor Intermittent Latency Increases for Some Firebase Cloud Messaging Services
Incident began at 2026-03-08 11:05 and ended at 2026-03-31 00:00 (all times are US/Pacific ). The issue has been resolved. Please file a bug with Firebase support if you see any continued errors. Affected products: Cloud Messaging
UPDATE: Test Lab is experiencing elevated inconclusive tests
Incident began at 2026-04-01 04:15 (all times are US/Pacific ). Test Lab is experiencing elevated inconclusive tests Affected products: Test Lab
RESOLVED: Delays and elevated inconclusive rates in Test Lab ARM devices
Incident began at 2026-03-31 12:00 and ended at 2026-03-31 23:00 (all times are US/Pacific ). This issue appears to be resolved now. Error rates are back to normal. Affected products: Test Lab
UPDATE: Delays and elevated inconclusive rates in Test Lab ARM devices
Incident began at 2026-03-31 12:00 and ended at 2026-03-31 23:00 (all times are US/Pacific ). Test Lab ARM devices are experiencing elevated failures rates and delays to test results. Affected products: Test Lab
Frequently Asked Questions
Is Firebase down right now?
This page shows the real-time status of Firebase. The status is checked automatically by pinging Firebase's servers. If the status shows "Down", it means Firebase is currently experiencing issues.
Why is Firebase not working?
Firebase may not be working due to server outages, scheduled maintenance, network issues, or high traffic. Check the current status above for real-time information.
How do I check if Firebase is down for everyone?
BlueMonitor checks Firebase's servers from our monitoring infrastructure. If the status shows "Down" here, it's likely down for everyone. If it shows "Up" but you can't access it, the issue may be on your end.
What should I do if Firebase is down?
If Firebase is down, you can: wait a few minutes and try again, check their official social media for updates, clear your browser cache, or try using a different network connection.