Firebase had 50 outages in the last 2 years totaling 2167h 17m of downtime — averaging 2.1 incidents per month.
There were 50 Firebase outages since June 27, 2025 totaling 2167h 17m of downtime. Each is summarised below — incident details, duration, and resolution information.
We are experiencing an issue causing elevated error rates when loading data on the Crashlytics, Release Monitoring, and Performance Monitoring dashboards, within Android Studio, and via our MCP tools. The team is actively investigating.
We are experiencing an issue with Firebase Cloud Messaging’s send apis in Asia beginning on Wednesday, 2026-06-10 21:50 PDT. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2026-06-10 23:45 PDT with current details.
Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2026-06-11 03:00 PDT. Customers may observe requests to send messages to FCM taking longer to complete. A small number may experience 5xx errors and should retry with backoff.
We are starting to see some recovery.
We believe the incident was fully mitigated as of 11:40pm.
Android physical tests delayed in FTL. Mitigation in progress.
The issue was triaged and a fix has been found. We will update soon on expected end of this disruption.
The fix has mitigated the issue and we are actively rolling it out. We expect the rollout to complete within 6 hours.
The fix has been rolled out and service has returned to normal
Firebase Test Lab is experiencing higher wait times on ARM devices. We are currently investigating the cause. Next update in when something significantly changes.
Firebase Test Lab is no longer experiencing delays for tests on ARM devices. Unless something unexpected happens, this is the last update.
Firebase Test Lab is experiencing delayed tests on ARM devices. We are currently investigating the cause.
The problem with Firebase Test Lab has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.
We're investigating the issue and determining the cause
We've redirected our traffic so newly created tests should run. We're still investigating and working to fix currently stuck tests
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
No updates so far
Problem appears to be mitigated and the error rates are back to normal level.
Test Lab ARM devices are experiencing elevated failures rates and delays to test results.
This issue appears to be resolved now. Error rates are back to normal.
Firebase Hosting is aware of missing metrics and logs from Cloud Logging.
Firebase Hosting engineers are working on backfilling missing Cloud Logging entries from 2026-03-23 21:46 UTC to 2026-03-30 16:04 UTC. The ETA is about 11:30 UTC March 31 for that process to complete.
The logs from the missing period should be restored. However, metrics may not have fully been restored from the time period due to technical limitations.
A recent change is causing 404 errors for clients who send messages to a URL which includes a trailing slash (/v1/projects/my-project/messages:send/ vs /v1/projects/my-project/messages:send). We are in the process of rolling back this change. For clients that are impacted, removing the trailing slash from the send URL will immediately resolve the problem.
The rollback is complete - service is fully restored.
Investigating: We are aware of a service disruption affecting App Hosting deployments from Firebase Studio. Impact: Users are currently unable to publish apps with App Hosting from Firebase Studio. Action: Our engineers are currently working to identify the root cause and restore deployment functionality as quickly as possible. We will provide an update as soon as we can. Workaround: In the meantime, you can publish using the Firebase App Hosting console or the Firebase CLI. Learn more at https://firebase.google.com/docs/app-hosting/get-started .
This should be resolved for all customers. Please contact Firebase Support if you encounter this issue again.
We are currently experiencing high error rates on the Firebase console. Investigations are ongoing.
Firebase Crashlytics is currently experiencing delays exporting data to BigQuery. Data from 03/09 and onwards have not been exported. We are currently investigating ways to expedite the export.
All BigQuery export jobs for Firebase Crashlytics have caught up.
We're aware of a problem with FCM affecting some users. We will provide an update by 13:00 PDT detailing when we expect to resolve the problem. Please note that this resolution time is an estimate and may change.
We are continuing to investigate this issue. We will provide an update by 18:00 PDT detailing when we expect to resolve the problem.
We are continuing to investigate this issue. We will provide updates in the next few days, but we believe the issue is quite minor and should not be a problem for most customers. Thank you for your patience.
We have pinpointed the issue and are actively working on a resolution; only a very small number of request are being sporadically impacted by minor latency increases. We will provide updates in the coming days.
We are actively working on a resolution. Only a very small number of request are being sporadically impacted by minor latency increases. We will provide updates in the coming days.
The issue has been resolved. Please file a bug with Firebase support if you see any continued errors.
We are investigating increased errors when connecting to GitHub in us-east5. This is believed to affect automatic and manual deploys from GitHub as well as updating commit statuses with GitHub checks. As a workaround, you may deploy from local source using the Firebase command line tools.
The issue has been resolved.
For approximately 1 hour starting at 06:11 PST on February 26, 2026, Firebase App Hosting backends in europe-west4 were seeing elevated errors on un-cached content due to increased network congestion and elevated requests. The issue was resolved for all affected projects as of 07:10 PST. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence.
We're currently investigating this issue.
We believe the issue has been mitigated. Please reach out to Firebase support if the error is still present in new builds.
The daily Crashlytics BigQuery export job is delayed for Jan 7 to 9. We are working on populating these daily tables, and are investigating the cause. Streaming BigQuery table data is not impacted.
All dates have been processed up to January 16.
We are experiencing an issue with Firebase Realtime Database beginning on Tuesday, 2026-01-06 13:10 PST. Impacted customers may experience request timeouts and/or errors when using the Firebase Realtime Database SDK or directly through APIs. Our engineering team has identified the root cause of the issue and the fix rollout is currently in progress. The vast majority of customers should stop experiencing issues and we're working to mitigate the impact for rest. We will provide an update by Tuesday, 2026-01-06 18:00 PST with current details. We apologize to all who are affected by the disruption.
Our engineering team has identified a recent change which has triggered the issue. The engineering team is currently rolling back the change to mitigate the impact. While the majority of the impact is already subsided, we do not have ETA for full mitigation at this time. We will provide an update by Tuesday, 2026-01-06 20:00 PST with current details.
The issue with Firebase Realtime Database has been resolved for all affected users as of Tuesday, 2026-01-06 19:46 PST. From preliminary analysis, we have identified that the issue was triggered by a recent change. The engineering team rolled back the change to mitigate the impact. We thank you for your patience while we worked on resolving the issue.
POST requests against Firebase Hosting Sites with rewrites to Firebase Fuctions can occasionally return unexpected 431 errors.
The Firebase Hosting team is currently rolling out a fix. It should be available globally within a few hours.
Webpush topic subscriptions may be throttled for some registrations. The team has identified a mitigation and is currently working on a fix.
The issue has been resolved. Please file a bug with Firebase support if you see any continued errors.
Next.js app builds were failing due to an issue in a recent update to the App Hosting Next.js adapter. The change has been rolled back and we believe the issue has been mitigated.
Affected builds will have failed with the error "Cannot find package 'semver'". This is now fully rolled back and mitigated.
We're aware of a problem with Firebase Test Lab causing very slow test allocation times. We will provide an update by 6:00PM PST detailing when we expect to resolve the problem. Please note that this resolution time is an estimate and may change.
Our team is continuing to investigate this issue. We will provide an update by 7:00PM PST with more information about this problem. Thank you for your patience.
The issue is resolved. Some device may have increased latency for a few more hours.
Firebase Remote Config is currently experiencing a service disruption. Please check back for status.
Issue is now mitigated