Firebase: SLA evidence report
Firebase: SLA evidence report
We hold no probe record for Firebase: we read its status page, so the only incident record here is what Firebase declared there. Nothing below is a measurement of ours, and the absence of one is not a record of no downtime.
- Incidents Firebase declared
- 3
- On its own status page, in this window.
- Window
- 2026-09-22 to 2026-10-22
- UTC, 30 days.
Sep 22, 2026, 10:00 AM UTC to Sep 22, 2026, 11:30 PM UTC
Firebase Test Lab is experiencing availability issues with ARM emulator devices., impact minor
This incident started before the report window shown above.
Oct 7, 2026, 4:30 PM UTC to Oct 9, 2026, 2:06 AM UTC
Firebase Hosting projects presenting intermittent "Bandwidth Quota Exceeded" errors or failing deployments with quota errors., impact minor
Oct 21, 2026, 1:05 PM UTC to Oct 22, 2026, 3:30 AM UTC
Partial performance degradation for RTDB users in us-central1 from 6 AM to 8:30 PM PT., impact minor
Methodology
These incidents come from Firebase's own public status feed, polled on our own schedule, and are shown as the vendor wrote them. They are not our measurement, we do not estimate an SLA credit from them, and they are not proof of downtime for your account. The credit Firebase owes, if any, is decided under its own SLA.