Firebase incident
Realtime Database Cloud Functions triggers not firing
Firebase experienced a major incident on October 31, 2025 affecting Realtime Database and Realtime Database (global), lasting 3d 4h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Nov 03, 2025, 06:13 PM UTC
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.
- investigating Nov 03, 2025, 08:27 PM UTC
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.
- resolved Nov 04, 2025, 02:30 AM UTC
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.