Firebase Outage History
Firebase is up right nowPingoru has recorded 57 incidents for Firebase: 49 in the last 12 months and 17 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 3 | 51 of 720 (7%) |
| May 2026 | 2 | 78 of 744 (11%) |
| June 2026 | 3 | 13 of 720 (2%) |
| July 2026 | 6 | 466 of 744 (63%) |
| August 2026 | 4 | 80 of 744 (11%) |
| September 2026 | 7 | 52 of 720 (7%) |
| October 2026 | 6 | 97 of 744 (13%) |
| November 2026 | 0 | 0 of 98 (0%) |
Incidents, newest first
Major October 22, 2026 Incident affecting Test Lab 1d 9h Test Lab, Test Lab (global)
Started Oct 22, 2026, 10:54 PM UTC· resolved Oct 24, 2026, 08:00 AM UTC
- investigating Oct 22, 2026, 10:56 PM UTC
The issue has been identified and mitigation is in process.
Major October 21, 2026 Partial performance degradation for RTDB users in us-central1 from 6 AM to 8:30 PM PT. 14h 25m Realtime Database, Realtime Database (global)
Started Oct 21, 2026, 01:05 PM UTC· resolved Oct 22, 2026, 03:30 AM UTC
- investigating Oct 21, 2026, 02:39 PM UTC
Users may be experiencing intermittent 500's and elevated latencies.
- resolved Oct 22, 2026, 07:19 PM UTC
We've successfully mitigated the network overloads on RTDB's backend that were causing network delays and intermittent 500's to REST requests.
Minor October 17, 2026 Reduced overall capacity for Android, iOS and Arm Emulator devices from 5 PM to 10 PM PT. 8h Test Lab, Test Lab (global)
Started Oct 17, 2026, 12:00 AM UTC· resolved Oct 17, 2026, 08:00 AM UTC
- monitoring Oct 16, 2026, 11:23 PM UTC
Network maintenance from 5PM to 8PM PT resulting in reduced capacity for all Android & iOS physical, and Arm emulator devices.
- monitoring Oct 17, 2026, 03:32 AM UTC
Network maintenance window extended by 2 hours, ETA 10PM. Reduced capacity for all Android & iOS physical, and Arm emulator devices.
Minor October 15, 2026 Reduced overall capacity for Android, iOS and Arm Emulator devices from 2 PM to 8 PM PT. 5h 20m Test Lab, Test Lab (global)
Started Oct 15, 2026, 09:00 PM UTC· resolved Oct 16, 2026, 02:20 AM UTC
- monitoring Oct 15, 2026, 08:54 PM UTC
Network maintenance from 2PM to 8PM PT resulting in reduced capacity for all Android & iOS physical, and Arm emulator devices.
Minor October 13, 2026 Drop in ARM emulator capacity due to network disruption to datacenter 2h 17m Test Lab, Test Lab (global)
Started Oct 13, 2026, 02:13 PM UTC· resolved Oct 13, 2026, 04:30 PM UTC
- monitoring Oct 13, 2026, 02:16 PM UTC
Currently, no significant impact to customer queue latency observed.
- resolved Oct 13, 2026, 04:47 PM UTC
Capacity has been restored.
Major October 7, 2026 Incident affecting Hosting 1d 9h Hosting, Hosting (global)
Started Oct 07, 2026, 04:30 PM UTC· resolved Oct 09, 2026, 02:06 AM UTC
- investigating Oct 08, 2026, 04:36 PM UTC
We are investigating an issue with Firebase Hosting where projects—including those on the Blaze plan—may intermittently serve HTTP 509 "Bandwidth Quota Exceeded" errors or fail deployments with HTTP 429 quota errors. Workaround / Immediate Mitigation: Affected customers can mitigate the issue immediately by ensuring that the Firebase Hosting API is enabled for their project in Google Cloud Console: https://console.cloud.google.com/apis/library/firebasehosting.googleapis.com?project=_ Our engineering team is actively investigating the issue and working on a resolution.
- investigating Oct 08, 2026, 08:21 PM UTC
A rollback has completed that should mitigate the bandwidth quota errors. Deployments that are failing due to quota may still be impacted as the rollback for that service continues. Ensuring the API is enabled is still a mitigation for more immediate resolution.
- resolved Oct 09, 2026, 09:44 PM UTC
The issue has been resolved.
Major September 22, 2026 Firebase Test Lab is experiencing availability issues with ARM emulator devices. 13h 30m Test Lab, Test Lab (global)
Started Sep 22, 2026, 10:00 AM UTC· resolved Sep 22, 2026, 11:30 PM UTC
- investigating Sep 22, 2026, 04:51 PM UTC
Firebase Test Lab is experiencing availability issues with ARM emulator devices.
- investigating Sep 22, 2026, 09:28 PM UTC
ARM emulator availability issues have been mitigated and full traffic capacity has been restored.
Major September 22, 2026 Firebase App Hosting experiencing issues actuating Cloud Run 2h 6m App Hosting, App Hosting (global)
Started Sep 22, 2026, 02:34 AM UTC· resolved Sep 22, 2026, 04:40 AM UTC
- investigating Sep 22, 2026, 04:06 AM UTC
Firebase App Hosting is having issues actuating Run. Services that are already running should be unaffected, but new builds or rollouts may be having issues.
- resolved Sep 22, 2026, 05:17 AM UTC
Firebase App Hosting's actuations of Cloud Run have been restored and builds should be working as expected now.
Major September 21, 2026 Firebase Hosting dataplane connectivity is in some regions. 17h 27m Hosting, Hosting (global)
Started Sep 21, 2026, 09:38 PM UTC· resolved Sep 22, 2026, 03:05 PM UTC
- investigating Sep 22, 2026, 04:25 PM UTC
Firebase Hosting has received report of sites being unavailable in some regions.
- resolved Sep 22, 2026, 04:26 PM UTC
The 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.
Major September 21, 2026 Firebase Test Lab is experiencing availability issues with ARM emulator devices. 4h Test Lab, Test Lab (global)
Started Sep 21, 2026, 07:39 PM UTC· resolved Sep 21, 2026, 11:39 PM UTC
- investigating Sep 21, 2026, 07:40 PM UTC
We are experiencing high test latencies for ARM tests due to reduced capacity and high demand.
- investigating Sep 21, 2026, 07:46 PM UTC
We are rolling out a new server update to mitigate the issue.
Major September 16, 2026 Crashlytics and Performance Monitoring consoles experiencing low availability. 2h 30m Crashlytics, Performance Monitoring, Crashlytics (global), Performance Monitoring (global)
Started Sep 16, 2026, 06:00 PM UTC· resolved Sep 16, 2026, 08:30 PM UTC
- investigating Sep 16, 2026, 07:25 PM UTC
Starting at 2PM ET, Crashlytics and Performance Monitoring console started experiencing low availability. We are working to remediate ASAP.
- resolved Sep 16, 2026, 08:36 PM UTC
Disruption is resolved at 13:30 PDT
Major September 10, 2026 Incident affecting Test Lab 17h 20m Test Lab, Test Lab (global)
Started Sep 10, 2026, 06:00 AM UTC· resolved Sep 10, 2026, 11:20 PM UTC
- investigating Sep 10, 2026, 07:16 AM UTC
Firebase Test Lab is experiencing execution delay on ARM based virtual devices. We are currently investigating the cause.
Major September 1, 2026 RESOLVED: Firebase Cloud Messaging - low availability in North America 3h 51m Cloud Messaging, Cloud Messaging (global)
Started Sep 01, 2026, 08:40 AM UTC· resolved Sep 01, 2026, 12:31 PM UTC
- investigating Sep 01, 2026, 10:29 AM UTC
We're aware of a problem with Firebase Cloud Messaging affecting its availability and latency in North America. We will provide an update by 04:30AM detailing when we expect to resolve the problem. Please note that this resolution time is an estimate and may change.
- investigating Sep 01, 2026, 11:43 AM UTC
Services are recovering. Next update at 05:30
- resolved Sep 01, 2026, 12:53 PM UTC
The problem has been resolved. All services in scope are back to normal.
Minor August 20, 2026 Network trace ingestion is delayed for Firebase Performance Monitoring customers. 1d 23h Performance Monitoring, Performance Monitoring (global)
Started Aug 20, 2026, 02:30 PM UTC· resolved Aug 22, 2026, 01:50 PM UTC
- monitoring Aug 20, 2026, 03:08 PM UTC
Description: We are experiencing an issue with Firebase Performance Monitoring, beginning on Thursday, 2026-08-20 07:30 PDT. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2026-08-20 11:00 PDT with details. We apologize to all who are affected by the disruption. Diagnosis / customer symptoms: Network trace ingestion data from August 17, 2026 is delayed for Firebase Performance Monitoring customers. All other Performance Monitoring data and BigQuery exports remain accurate. There is no data loss associated with this event. Workaround: None at this time.
- monitoring Aug 20, 2026, 06:39 PM UTC
Description: We are experiencing an issue with Firebase Performance Monitoring, beginning on Thursday, 2026-08-20 07:30 PDT. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2026-08-20 15:30 PDT with details. Diagnosis / customer symptoms: Network trace ingestion data from August 17, 2026 is delayed for Firebase Performance Monitoring customers. All other Performance Monitoring data and BigQuery exports remain accurate. There is no data loss associated with this event. Workaround: None at this time.
- monitoring Aug 20, 2026, 10:34 PM UTC
Description: We are experiencing an issue with Firebase Performance Monitoring, beginning on Thursday, 2026-08-20 07:30 PDT. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2026-08-21 08:00 PDT with details. Diagnosis / customer symptoms: Network trace ingestion data from August 17, 2026 is delayed for Firebase Performance Monitoring customers. All other Performance Monitoring data and BigQuery exports remain accurate. There is no data loss associated with this event. Workaround: None at this time.
- monitoring Aug 21, 2026, 12:21 PM UTC
Description: We are experiencing an issue with Firebase Performance Monitoring, beginning on Thursday, 2026-08-20 07:30 PDT. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2026-08-21 20:00 PDT with details. Diagnosis / customer symptoms: Network trace ingestion data from August 18, 2026 is delayed for Firebase Performance Monitoring customers. All other Performance Monitoring data and BigQuery exports remain accurate. There is no data loss associated with this event. Workaround: None at this time.
- monitoring Aug 21, 2026, 11:30 PM UTC
Description: We are experiencing an issue with Firebase Performance Monitoring, beginning on Thursday, 2026-08-20 07:30 PDT. Our engineering team has identified the cause of this issue and is currently working on a mitigation. We will provide an update by Saturday, 2026-08-22 09:00 PDT with details. Diagnosis / customer symptoms: Network trace ingestion data for August 18, 2026 is delayed for Firebase Performance Monitoring customers. All other Performance Monitoring data and BigQuery exports remain accurate. There is no data loss associated with this event. Workaround: None at this time.
- resolved Aug 22, 2026, 02:01 PM UTC
Description: The issue with Firebase Performance Monitoring has been resolved for all affected users as of Saturday, 2026-08-22 06:50 PDT. We thank you for your patience while we worked on resolving the issue. Diagnosis / customer symptoms: The Firebase Dashboard has been fixed and currently is up to date, BigQuery is delayed for 2026-08-18 and 2026-08-19. All other Performance Monitoring data and BigQuery exports remain accurate. There is no data loss associated with this event. Workaround: None as the issue has been mitigated.
- resolved Aug 22, 2026, 02:03 PM UTC
Description: The issue with Firebase Performance Monitoring has been resolved for all affected users as of Saturday, 2026-08-22 06:50 PDT. We thank you for your patience while we worked on resolving the issue. Diagnosis / customer symptoms: The Firebase Dashboard has been fixed and currently is up to date, BigQuery was delayed for 2026-08-18 and 2026-08-19. All other Performance Monitoring data and BigQuery exports remained accurate. There was no data loss associated with this event. Workaround: None as the issue has been mitigated.
Major August 17, 2026 Outage in App Distribution affecting uploads 1h 7m App Distribution, App Distribution (global)
Started Aug 17, 2026, 09:13 PM UTC· resolved Aug 17, 2026, 10:20 PM UTC
- investigating Aug 17, 2026, 10:58 PM UTC
App Distribution uploads started failing
- resolved Aug 17, 2026, 10:59 PM UTC
Incident has been resolved
Major August 13, 2026 Firebase A/B Testing Issue 17h 50m A/B Testing (Beta), A/B Testing (Beta) (global)
Started Aug 13, 2026, 05:23 PM UTC· resolved Aug 14, 2026, 11:13 AM UTC
- investigating Aug 13, 2026, 05:56 PM UTC
We are investigating an issue with Firebase A/B Testing. Some users are not able to modify or create an experiment. We will provide more information shortly.
- investigating Aug 13, 2026, 06:42 PM UTC
We are still looking into this.
- investigating Aug 13, 2026, 08:49 PM UTC
We are still working on this. Meanwhile, please contact Firebase support for help in case you face any issues with A/B Testing
- resolved Aug 14, 2026, 11:14 AM UTC
The issue with Firebase A/B Testing has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.
Major August 11, 2026 Incident affecting Test Lab 13h 32m Test Lab, Test Lab (global)
Started Aug 11, 2026, 01:13 PM UTC· resolved Aug 12, 2026, 02:45 AM UTC
- investigating Aug 11, 2026, 01:17 PM UTC
We are in the progress of fixing.
- investigating Aug 11, 2026, 11:55 PM UTC
Mitigations have been applied, and tests should start running again. However, wait times may still be longer than normal during this recovery period.
- resolved Aug 12, 2026, 04:04 AM UTC
Mitigations have been rolled out and tests should be running as normal.
Major July 30, 2026 Firebase Hosting custom domains API returning 501 errors 13h 20m Hosting, Hosting (global)
Started Jul 30, 2026, 09:00 PM UTC· resolved Jul 31, 2026, 10:20 AM UTC
- investigating Jul 31, 2026, 03:38 AM UTC
The engineering team is investigating elevated 501 "unimplemented" errors seen in Hosting's API when managing custom domains. It does not appear at this time that the data plane is effected.
- investigating Jul 31, 2026, 04:38 AM UTC
We believe to have found the root cause and are working to restore this portion of our API. We are more confident now that the data plane is unaffected and that this was limited in scope to the management of Hosting custom domains.
- investigating Jul 31, 2026, 05:14 AM UTC
The 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.
Major July 21, 2026 Firebase Crashlytics data is delayed starting for the 18th 2d 21h Crashlytics, Crashlytics (global)
Started Jul 21, 2026, 06:09 PM UTC· resolved Jul 24, 2026, 04:00 PM UTC
- investigating Jul 21, 2026, 06:11 PM UTC
Firebase Crashlytics data is delayed
Major July 20, 2026 High execution latency for arm and physical devices. 1d Test Lab, Test Lab (global)
Started Jul 20, 2026, 03:38 PM UTC· resolved Jul 21, 2026, 04:20 PM UTC
- investigating Jul 20, 2026, 03:39 PM UTC
Firebase Test Lab is experiencing high execution latency for arm devices. We are currently investigating the cause and will provide more information shortly.
- investigating Jul 20, 2026, 04:56 PM UTC
Firebase Test Lab is currently experiencing increased execution error rates for arm and physical devices (Android and iOS). We have investigated the cause and are mitigating the issue.
- investigating Jul 21, 2026, 02:31 PM UTC
Firebase Test Lab is experiencing high execution latency for arm devices. We are currently investigating the cause and will provide more information shortly.
Major July 13, 2026 Firebase Crashlytics data is delayed 2d 13h Crashlytics, Crashlytics (global)
Started Jul 13, 2026, 03:41 PM UTC· resolved Jul 16, 2026, 04:45 AM UTC
- investigating Jul 13, 2026, 03:42 PM UTC
Firebase Crashlytics data is delayed for 2026-07-10
- investigating Jul 14, 2026, 07:25 PM UTC
Firebase Crashlytics data is delayed for 2026-07-10 and 2026-07-11
- investigating Jul 15, 2026, 05:23 PM UTC
Firebase 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.
Major July 4, 2026 Performance Monitoring data is delayed 1d 23h Performance Monitoring, Performance Monitoring (global)
Started Jul 04, 2026, 07:00 AM UTC· resolved Jul 06, 2026, 06:00 AM UTC
- investigating Jul 04, 2026, 02:45 PM UTC
Performance Monitoring data is delayed
Major July 1, 2026 Visible reduction in data within Performance Monitoring dashboards and BigQuery exports. 69d Performance Monitoring, Performance Monitoring (global)
Started Jul 01, 2026, 07:00 AM UTC· resolved Sep 08, 2026, 07:00 AM UTC
- investigating Jul 14, 2026, 08:38 PM UTC
We 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.
Critical June 15, 2026 Incident affecting Crashlytics and Performance Monitoring 2h 30m Crashlytics, Performance Monitoring, Crashlytics (global), Performance Monitoring (global)
Started Jun 15, 2026, 03:30 PM UTC· resolved Jun 15, 2026, 06:00 PM UTC
- investigating Jun 15, 2026, 06:03 PM UTC
We 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 actively investigating.
Critical June 11, 2026 Firebase Cloud Monitoring - Low sending availability in Asia-Pacific region 1h 50m Cloud Messaging, Cloud Messaging (global)
Started Jun 11, 2026, 04:50 AM UTC· resolved Jun 11, 2026, 06:40 AM UTC
- investigating Jun 11, 2026, 05:20 AM UTC
We are experiencing an issue with Firebase Cloud Messaging’s send apis in Asia beginning on Wednesday, 2026-06-10 21:50 PDT. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2026-06-10 23:45 PDT with current details.
- investigating Jun 11, 2026, 06:19 AM UTC
Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Thursday, 2026-06-11 03:00 PDT. Customers may observe requests to send messages to FCM taking longer to complete. A small number may experience 5xx errors and should retry with backoff.
- investigating Jun 11, 2026, 06:36 AM UTC
We are starting to see some recovery.
- investigating Jun 11, 2026, 07:15 AM UTC
We believe the incident was fully mitigated as of 11:40pm.