Firebase had 45 outages in the last 2 years totaling 2796h 57m of downtime — averaging 1.8 incidents per month.
There were 45 Firebase outages since July 18, 2025 totaling 2796h 57m of downtime. Each is summarised below — incident details, duration, and resolution information.
Crashlytics and Performance Monitoring consoles experiencing low availability.
Disruption is resolved at 13:30 PDT
Firebase Test Lab is experiencing execution delay on ARM based virtual devices. We are currently investigating the cause.
We're aware of a problem with Firebase Cloud Messaging affecting its availability and latency in North America. We will provide an update by 04:30AM detailing when we expect to resolve the problem. Please note that this resolution time is an estimate and may change.
Services are recovering. Next update at 05:30
The problem has been resolved. All services in scope are back to normal.
App Distribution uploads started failing
Incident has been resolved
We are investigating an issue with Firebase A/B Testing. Some users are not able to modify or create an experiment. We will provide more information shortly.
We are still looking into this.
We are still working on this. Meanwhile, please contact Firebase support for help in case you face any issues with A/B Testing
The issue with Firebase A/B Testing has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.
The engineering team is investigating elevated 501 "unimplemented" errors seen in Hosting's API when managing custom domains. It does not appear at this time that the data plane is effected.
We believe to have found the root cause and are working to restore this portion of our API. We are more confident now that the data plane is unaffected and that this was limited in scope to the management of Hosting custom domains.
The fix is being rolled out. The ETA for complete resolution is July 31 at ~11:00 UTC, though some users may have restored functionality before then.
Firebase Crashlytics data is delayed
Firebase Test Lab is experiencing high execution latency for arm devices. We are currently investigating the cause and will provide more information shortly.
Firebase Test Lab is currently experiencing increased execution error rates for arm and physical devices (Android and iOS). We have investigated the cause and are mitigating the issue.
Firebase Test Lab is experiencing high execution latency for arm devices. We are currently investigating the cause and will provide more information shortly.
Firebase Crashlytics data is delayed for 2026-07-10
Firebase Crashlytics data is delayed for 2026-07-10 and 2026-07-11
Firebase Crashlytics data is currently delayed for 2026-07-12 and 2026-07-13. Processing for earlier dates has completed. Exported BigQuery batch and streaming data remain accurate.
Performance Monitoring data is delayed
We are investigating a system issue. To protect platform stability, we have limited the volume of collected data. Expect a visible reduction in data within Performance Monitoring dashboards and BigQuery exports.
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.