← Back to Firebase History
minor✓ Resolved

Realtime Database Cloud Functions triggers not firing

Firebase•
Status
resolved
Duration
7h 5m
Updates
3
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
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.
investigating
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.
investigating
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.

📊 TECHNICAL DETAILS

Internal ID
4c8363c1-dca6-4b5e-82bf-ad4e4e0b823c
External ID
XNiKkpH5kjXQFkEQvVWF
🕐 Started
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
7h 5m
Total Duration
3
Status Updates
Affected Components
Realtime Database
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed