# Firebase in June 2026: incidents, uptime and changes

> Firebase in June 2026: 3 incidents on its status page (2 major or critical), 99.39% 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/06
Last updated: 2026-07-01T00:00:00Z

- Incidents posted: 3 (major/critical: 2) · Maintenance: 0
- By vendor impact label: major 2, minor 1
- Uptime (vendor-reported): 99.39% free of major/critical incidents, 98.14% free of any incident; outage time 4 h 20 min, incident time 13 h 20 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [May 2026](https://rewindex.com/company/firebase/2026/05.md) · Next: [July 2026](https://rewindex.com/company/firebase/2026/07.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._

## Major and critical incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Firebase Cloud Monitoring - Low sending availability in Asia-Pacific region](https://rewindex.com/company/firebase/incidents/kp6qhxupgqdb6dzuxfxv.md) | major | 2026-06-11 04:50 UTC | 2026-06-11 06:40 UTC | 1.8 h | resolved |
| [Elevated error rates when loading data on the Crashlytics, Release Monitoring, and Performance Monitoring dashboards, within Android Studio, and via our MCP tools.](https://rewindex.com/company/firebase/incidents/zzgy2qfsdsgpxedluu28.md) | major | 2026-06-15 15:30 UTC | 2026-06-15 18:00 UTC | 2.5 h | resolved |

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Android physical tests delayed in FTL](https://rewindex.com/company/firebase/incidents/ufnmvqsko4kkmqr6t1fe.md) | minor | 2026-06-01 18:30 UTC | 2026-06-02 03:30 UTC | 9.0 h | resolved |
| [Firebase Cloud Monitoring - Low sending availability in Asia-Pacific region](https://rewindex.com/company/firebase/incidents/kp6qhxupgqdb6dzuxfxv.md) | major | 2026-06-11 04:50 UTC | 2026-06-11 06:40 UTC | 1.8 h | resolved |
| [Elevated error rates when loading data on the Crashlytics, Release Monitoring, and Performance Monitoring dashboards, within Android Studio, and via our MCP tools.](https://rewindex.com/company/firebase/incidents/zzgy2qfsdsgpxedluu28.md) | major | 2026-06-15 15:30 UTC | 2026-06-15 18:00 UTC | 2.5 h | resolved |

## Cite this

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

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


---
Canonical: https://rewindex.com/company/firebase/2026/06 · Markdown: https://rewindex.com/company/firebase/2026/06.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T15:26:34.048Z