rewindex

ChangesFirebaseWe are tracking a networking issue that may affect a significant part of the fleet. Devices may be unable to connect to backends that support IPv4 only (IPv6 and dual support are not affected).

Firebase: Incident silently edited: We are tracking a networking issue that may affect a significant part of the fleet. Devices may be unable to connect to backends that support IPv4 only (IPv6 and dual support are not affected).

Silent editNot classified yetChanged status.firebase.google.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Firebase removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: investigating
After: resolved
AddedResolved time#2
Before: not present
After: 2026-10-24 08:00 UTC
ChangedUpdateservice_disruption → resolved#3
Before: The issue has been identified and mitigation is in process.
After: The issue has been identified and mitigation is in process.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

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 these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

YesterdayTuesday, October 27Tue, Oct 27

1 rewrite

All Firebase changesFirebase profileMarkdownJSON