Firebase Status Dashboard

Firebase Status Dashboard
Incidents
Realtime Database Cloud Functions triggers not firing

This page provides status information on the services that are part of Firebase. Check back here to view the current status of the services listed below. If you are experiencing an issue not listed here, please contact Support. Learn more about what's posted on the dashboard in this FAQ. For additional information on these services, please visit https://firebase.google.com/.

NOTE

For incidents related to Cloud Functions, Cloud Firestore and Cloud Storage, please see Cloud Service Health. For incidents related to Google Analytics, please see Ads Status Dashboard.

Available
Service information
Service disruption
Service outage

Incident affecting Realtime Database

Realtime Database Cloud Functions triggers not firing

Incident began at 2025-10-31 14:03 and ended at 2025-11-03 17:18 (all times are US/Pacific).

Date	Time	Description
3 Nov 2025	18:30 PST	The issue with Firebase Realtime Database has been resolved for all affected projects as of Monday, 2025-11-03 18:13 PST. During the incident, Firebase Cloud Functions that are triggered by Realtime Database events were not firing, which might have impacted automated workflows for customers. While the databases themselves are working, any function that is configured to trigger on certain read/write events may have been significantly delayed and may only have executed after the issue got mitigated. From preliminary analysis, the issue was triggered by an internal backwards incompatible change in a new version rollout. Our engineers mitigated the issue by deploying a fix to all affected regions. We thank you for your patience while we worked on resolving the issue.
3 Nov 2025	12:27 PST	Mitigation work is underway by our engineering team. Impact in europe-west1 and asia-southeast1 regions have already subsided. Customers in these regions may notice functions triggering for events from as early as 31 October, 2025 (when the incident started). The events are only delayed and are not missing. We will provide more information by Monday, 2025-11-03 16:30 US/Pacific with details, including impact / mitigation status in us-central1.
3 Nov 2025	10:13 PST	We've received customer reports that Cloud Functions triggers on RTDB events are not triggering / executing. While the databases themselves are working, any function that is configured to trigger on certain read/write events will not execute. We're rolling back the latest build to mitigate while we investigate the root cause.

Date

Time

Description

3 Nov 2025

18:30 PST

The issue with Firebase Realtime Database has been resolved for all affected projects as of Monday, 2025-11-03 18:13 PST.

During the incident, Firebase Cloud Functions that are triggered by Realtime Database events were not firing, which might have impacted automated workflows for customers. While the databases themselves are working, any function that is configured to trigger on certain read/write events may have been significantly delayed and may only have executed after the issue got mitigated.

From preliminary analysis, the issue was triggered by an internal backwards incompatible change in a new version rollout.

Our engineers mitigated the issue by deploying a fix to all affected regions.

We thank you for your patience while we worked on resolving the issue.

3 Nov 2025

12:27 PST

Mitigation work is underway by our engineering team.

Impact in europe-west1 and asia-southeast1 regions have already subsided. Customers in these regions may notice functions triggering for events from as early as 31 October, 2025 (when the incident started). The events are only delayed and are not missing.

We will provide more information by Monday, 2025-11-03 16:30 US/Pacific with details, including impact / mitigation status in us-central1.

3 Nov 2025

10:13 PST

We've received customer reports that Cloud Functions triggers on RTDB events are not triggering / executing. While the databases themselves are working, any function that is configured to trigger on certain read/write events will not execute. We're rolling back the latest build to mitigate while we investigate the root cause.

All times are US/Pacific