Firebase: Firebase Crashlytics data is delayed
Affected components: Crashlytics
Timeline of updates
- service disruption
Firebase Crashlytics data is delayed for 2026-07-10
- service disruption
Firebase Crashlytics data is delayed for 2026-07-10 and 2026-07-11
- resolved
Firebase Crashlytics data is currently delayed for 2026-07-12 and 2026-07-13. Processing for earlier dates has completed. Exported BigQuery batch and streaming data remain accurate.
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
c68dce03d3334738…
Impact, status and times are the vendor’s own, as last archived. View on status.firebase.google.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Firebase, started 2026-07-13 15:41 UTC, resolved after 3 d, 3 update(s).
- Title
- Firebase Crashlytics data is delayed
- Vendor
- Firebase
- Date
- URL
- https://rewindex.com/company/firebase/incidents/czygv7ggtjaspqm7yn8i
Firebase profileRecent Firebase incidentsAll outages on July 13, 2026Firebase in July 2026MarkdownJSON