Firebase Outage History

49 incidents recorded over the last 365 days, 49 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live Firebase status100.00% uptime history

Every Recorded Firebase Incident

Firebase incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Oct 8, 2026Hosting: mediumThe issue has been resolved.9h 29mResolved
Sep 22, 2026Test Lab: mediumARM emulator availability issues have been mitigated and full traffic capacity has been restored.6h 38mResolved
Sep 22, 2026Hosting: mediumThe connectivity issues seem to be resolved and we are seeing requests complete from those regions once again. We will continue to monitor but believe the situation has recovered.-80 minResolved
Sep 22, 2026App Hosting: mediumFirebase App Hosting's actuations of Cloud Run have been restored and builds should be working as expected now.33 minResolved
Sep 21, 2026Test Lab: mediumWe are rolling out a new server update to mitigate the issue.3h 58mResolved
Sep 16, 2026Multiple Products: mediumDisruption is resolved at 13:30 PDT1h 4mResolved
Sep 10, 2026Test Lab: mediumFirebase Test Lab is experiencing execution delay on ARM based virtual devices. We are currently investigating the cause.16h 3mResolved
Sep 1, 2026Cloud Messaging: mediumThe problem has been resolved. All services in scope are back to normal.2h 1mResolved
Aug 20, 2026Performance Monitoring: low**Summary** Network trace ingestion was delayed for Firebase Performance Monitoring customers. **Description** The issue with Firebase Performance Monitoring has been resolved for all affected users as of Saturday…46h 41mResolved
Aug 17, 2026App Distribution: mediumIncident has been resolved-38 minResolved
Aug 13, 2026A/B Testing (Beta): mediumThe issue with Firebase A/B Testing has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.17h 16mResolved
Aug 11, 2026Test Lab: mediumMitigations have been rolled out and tests should be running as normal.13h 27mResolved
Jul 31, 2026Hosting: mediumThe fix is being rolled out. The ETA for complete resolution is July 31 at ~11:00 UTC, though some users may have restored functionality before then.6h 41mResolved
Jul 21, 2026Crashlytics: mediumFirebase Crashlytics data is delayed69h 48mResolved
Jul 20, 2026Test Lab: mediumFirebase Test Lab is experiencing high execution latency for arm devices. We are currently investigating the cause and will provide more information shortly.24h 40mResolved
Jul 14, 2026Performance Monitoring: mediumWe are investigating a system issue. To protect platform stability, we have limited the volume of collected data. Expect a visible reduction in data within Performance Monitoring dashboards and BigQuery exports.1330h 21mResolved
Jul 13, 2026Crashlytics: mediumFirebase 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.61h 2mResolved
Jul 4, 2026Performance Monitoring: mediumPerformance Monitoring data is delayed39h 14mResolved
Jun 15, 2026Multiple Products: highWe are experiencing an issue causing elevated error rates when loading data on the Crashlytics, Release Monitoring, and Performance Monitoring dashboards, within Android Studio, and via our MCP tools. The team is…-3 minResolved
Jun 11, 2026Cloud Messaging: highWe believe the incident was fully mitigated as of 11:40pm.1h 19mResolved
Jun 1, 2026Test Lab: mediumAndroid physical tests delayed in FTL. Mitigation in progress.5h 53mResolved
May 21, 2026App Distribution: mediumThe fix has been rolled out and service has returned to normal22h 27mResolved
May 11, 2026Test Lab: mediumFirebase Test Lab is no longer experiencing delays for tests on ARM devices. Unless something unexpected happens, this is the last update.5h 32mResolved
Apr 28, 2026Test Lab: mediumThe problem with Firebase Test Lab has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.34h 29mResolved
Apr 9, 2026AI Logic: mediumProblem appears to be mitigated and the error rates are back to normal level.3h 50mResolved
Apr 9, 2026Test Lab: highWe believe we've addressed the issue and stuck tests will now run. They may still be delayed as the system works through the queue3h 59mResolved
Apr 1, 2026Test Lab: mediumTest Lab is experiencing elevated inconclusive tests2984h 45mResolved
Apr 1, 2026Test Lab: mediumThis issue appears to be resolved now. Error rates are back to normal.1h 38mResolved
Mar 31, 2026Hosting: mediumThe logs from the missing period should be restored. However, metrics may not have fully been restored from the time period due to technical limitations.9h 55mResolved
Mar 30, 2026Multiple Products: highServices are functioning normally as of 2026-03-30 09:00 PDT1h 7mResolved
Mar 20, 2026Cloud Messaging: mediumThe rollback is complete - service is fully restored.-4255 minResolved
Mar 13, 2026Cloud Messaging: mediumThe issue has been resolved. Please file a bug with Firebase support if you see any continued errors.420h 45mResolved
Mar 13, 2026Crashlytics: mediumAll BigQuery export jobs for Firebase Crashlytics have caught up.20h 50mResolved
Mar 11, 2026Studio (Preview): mediumThis should be resolved for all customers. Please contact Firebase Support if you encounter this issue again.469h 0mResolved
Mar 10, 2026Multiple Products: highWe are currently experiencing high error rates on the Firebase console. Investigations are ongoing.43 minResolved
Mar 5, 2026App Hosting: mediumThe issue has been resolved.58 minResolved
Mar 2, 2026App Hosting: mediumFor approximately 1 hour starting at 06:11 PST on February 26, 2026, Firebase App Hosting backends in europe-west4 were seeing elevated errors on un-cached content due to increased network congestion and elevated…-6186 minResolved
Jan 16, 2026App Hosting: lowWe believe the issue has been mitigated. Please reach out to Firebase support if the error is still present in new builds.4 minResolved
Jan 12, 2026Crashlytics: mediumAll dates have been processed up to January 16.112h 45mResolved
Jan 7, 2026Realtime Database: highThe issue with Firebase Realtime Database has been resolved for all affected users as of Tuesday, 2026-01-06 19:46 PST. From preliminary analysis, we have identified that the issue was triggered by a recent change. The…2h 27mResolved
Jan 6, 2026Hosting: mediumThe Firebase Hosting team is currently rolling out a fix. It should be available globally within a few hours.2h 55mResolved
Dec 17, 2025Cloud Messaging: mediumThe issue has been resolved. Please file a bug with Firebase support if you see any continued errors.4h 1mResolved
Dec 4, 2025App Hosting: mediumAffected builds will have failed with the error "Cannot find package 'semver'". This is now fully rolled back and mitigated.-28 minResolved
Dec 3, 2025Test Lab: mediumThe issue is resolved. Some device may have increased latency for a few more hours.3h 47mResolved
Nov 27, 2025Remote Config: mediumIssue is now mitigated1h 28mResolved
Nov 3, 2025Realtime Database: mediumThe issue with Firebase Realtime Database has been resolved for all affected projects as of Monday, 2025-11-03 18:13 PST. During the incident, Firebase Cloud Functions that are triggered by Realtime Database events were…7h 5mResolved
Oct 31, 2025SQL Connect: medium(The service has been in a stable state since last update. We just want to give an update to the cause.) The issue was due to a bad rollout in a downstream dependency, and our engineers have mitigated the issue by fully…3h 4mResolved
Oct 28, 2025Test Lab: mediumThe issue is external and has been mitigated. Tests should start to pass again. This is the last update unless something changes.16 minResolved
Oct 15, 2025Studio (Preview): mediumFirebase Studio users are experiencing publishing errors when using the "Publish" button.6h 45mResolved

Hear about the next one while it is open

Everything above is a record written after the fact. We can email you when the next Firebase incident opens instead, at the point where knowing still changes what you do.

Free, no password, no card. Unsubscribe in one click.

How to Read This Firebase Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Firebase acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single Firebase outage in this window ran 124d 8h, against a mean recovery of 5d 14h. If you depend on Firebase in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.