Firebase Outage History

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 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.

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 experiencing delayed tests on ARM devices. We are currently investigating the cause.

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

No updates so far

Test Lab ARM devices are experiencing elevated failures rates and delays to test results.

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.

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.

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 .

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.

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.

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 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.

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.