Firebase: Firebase Realtime Database (RTDB) customers may experience connectivity issues in us-central1, europe-west1 and asia-southeast1
Affected components: Realtime Database
Timeline of updates
- service outage
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. - service outage
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. - resolved
The issue with Firebase Realtime Database has been resolved for all affected users as of Tuesday, 2026-01-06 19:46 PST.
From preliminary analysis, we have identified that the issue was triggered by a recent change. The engineering team rolled back the change to mitigate the impact.
We thank you for your patience while we worked on resolving the issue.
Changes Rewindex caught on this incident
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
dd7ddb84c8006d06…
Impact, status and times are the vendor’s own, as last archived. View on status.firebase.google.com (opens in new tab).