rewindex

ChangesFirebaseWe are currently experiencing high error rates on the Firebase console. Investigations are ongoing.

Firebase: Major incident: We are currently experiencing high error rates on the Firebase console. Investigations are ongoing.

Major incidentoutage (model (Jev), 90%)Changed Detected 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.

AddedTitle#1
Before: not present
After: We are currently experiencing high error rates on the Firebase console. Investigations are ongoing.
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-03-10 14:51 UTC
AddedResolved time#5
Before: not present
After: 2026-03-10 16:43 UTC
AddedAffected components#6
Before: not present
After: Crashlytics, Performance Monitoring
AddedUpdateresolved#7
Before: not present
After: We are currently experiencing high error rates on the Firebase console. Investigations are ongoing.

First version of this incident archived by Rewindex. 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 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.

History of this incident

Tuesday, March 10

1 incident change

All Firebase changesFirebase profileMarkdownJSON