# Firebase in July 2026: incidents, uptime and changes

> Firebase in July 2026: 6 incidents on its status page (0 major or critical), 100% free of major or critical incidents (vendor-reported). From Rewindex’s archive of Firebase’s status, pricing and policy pages.

Canonical: https://rewindex.com/company/firebase/2026/07
Last updated: 2026-08-01T00:00:00Z

- Incidents posted: 6 (major/critical: 0) · Maintenance: 0
- By vendor impact label: minor 6
- Uptime (vendor-reported): 100% free of major/critical incidents, 54.71% free of any incident; outage time 0 min, incident time 14.0 days
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [June 2026](https://rewindex.com/company/firebase/2026/06.md) · Next: [August 2026](https://rewindex.com/company/firebase/2026/08.md) · [All months](https://rewindex.com/company/firebase/reports.md) · [Firebase](https://rewindex.com/company/firebase.md)

_Uptime: Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours._

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Visible reduction in data within Performance Monitoring dashboards and BigQuery exports.](https://rewindex.com/company/firebase/incidents/hbvswdqrs8jpc53quj8t.md) | minor | 2026-07-01 07:00 UTC | 2026-09-08 07:00 UTC | 69 d | resolved |
| [Performance Monitoring data is delayed](https://rewindex.com/company/firebase/incidents/mpdcwzzkxieefyx2pann.md) | minor | 2026-07-04 07:00 UTC | 2026-07-06 06:00 UTC | 47 h | resolved |
| [Firebase Crashlytics data is delayed](https://rewindex.com/company/firebase/incidents/czygv7ggtjaspqm7yn8i.md) | minor | 2026-07-13 15:41 UTC | 2026-07-16 04:45 UTC | 3 d | resolved |
| [High execution latency for arm and physical devices.](https://rewindex.com/company/firebase/incidents/tjvpjs86rzqqbmruzffc.md) | minor | 2026-07-20 15:38 UTC | 2026-07-21 16:20 UTC | 25 h | resolved |
| [Firebase Crashlytics data is delayed starting for the 18th](https://rewindex.com/company/firebase/incidents/btyxzwk3kt8djeb8u8bs.md) | minor | 2026-07-21 18:09 UTC | 2026-07-24 16:00 UTC | 3 d | resolved |
| [Firebase Hosting custom domains API returning 501 errors](https://rewindex.com/company/firebase/incidents/e1vzivqdlmv9kfgeejjr.md) | minor | 2026-07-30 21:00 UTC | 2026-07-31 10:20 UTC | 13 h | resolved |

## Cite this

Firebase posted 6 status incidents in July 2026 (0 major or critical); 0 price changes and 0 notable page changes observed.

- Canonical URL: https://rewindex.com/company/firebase/2026/07
- Citation: Firebase, “Firebase in July 2026” (2026-07-01 00:00 UTC). Archived by Rewindex: https://rewindex.com/company/firebase/2026/07 (CC BY 4.0).
- Markdown link: `[Firebase: Firebase in July 2026 (2026-07-01)](https://rewindex.com/company/firebase/2026/07)`


---
Canonical: https://rewindex.com/company/firebase/2026/07 · Markdown: https://rewindex.com/company/firebase/2026/07.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T13:34:20.011Z