- Sep 21, 2022
- 71
- Content source
- https://status.firebase.google.com/
Overview of the Incident
Date of incident: June 12, 2025
Start time (PDT): around 11:00 (≈ 19:00 UTC)
Last dashboard update: 11:42 PDT (≈ 19:42 UTC)
Earlier today, Firebase experienced a widespread service disruption impacting several key services across multiple regions:
- Realtime Database: authentication issues and access errors
- Hosting API: failures when deploying or accessing hosted sites
- Data Connect: offline due to an underlying Google Cloud outage
- App Check: higher error rates and failures
- Console UI: reduced availability
- Cloud Messaging: increased latency and message errors
- Test Lab: blocked tests
- App Hosting: origin/API outages
In short, essential Firebase components—from backend systems to developer tools—were affected simultaneously.
Why It Matters
Firebase powers countless mobile and web apps with real-time data, hosting, authentication, messaging, and CI/CD workflows. An outage like this can lead to:
- App crashes or frozen interfaces
- Broken deployments and updates
- Message delivery failures (push notifications)
- Development delays and blocked testing
If you're running production apps,
this could translate into major user-facing issues and revenue losses.
What Developers Should Do
- Check the status dashboard. Firebase actively monitors and updates the status page at Firebase Status Dashboard.
- Use SDK fallbacks. Implement offline modes for Realtime Database and handle Hosted URL failures gracefully.
- Delay non-critical operations. Postpone deployments, testing, or messaging if possible.
- Monitor Google Cloud Health. Since this likely stems from a broader GCP disruption, code resilience against upstream failures is key.
- Plan for redundancy. Consider multi-region setup or mesh across alternatives for critical services.
