Google had 127 outages in the last 2 years totaling 1173h 52m of downtime — averaging 5.2 incidents per month.
There were 127 Google outages since June 25, 2025 totaling 1173h 52m of downtime. Each is summarised below — incident details, duration, and resolution information.
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.
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.
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.
We are starting to see some recovery.
We believe the incident was fully mitigated as of 11:40pm.
We're investigating reports of an issue with Content API for Shopping. We will provide more information shortly.
Android physical tests delayed in FTL. Mitigation in progress.
We're investigating reports of an issue with Play Billing Purchases and Play Developer Subscriptions and In-App Purchases API. We will provide more information shortly.
The problem with Play Billing Purchases and Play Developer Subscriptions and In-App Purchases API has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.
We're investigating reports of an issue with Play Subscriptions Renewal and Management. We will provide more information shortly.
The problem with Play Subscriptions Renewal and Management has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.
We're investigating reports of an issue with Google Ad Manager. We will provide more information shortly. The affected users are able to access Google Ad Manager, but are seeing error messages, high latency, and/or other unexpected behavior. Affected networks will see some Third Party type Audience Segments showing as inactive status, even though no manual changes were made. No workaround at the moment.
The problem with Google Ad Manager has been resolved. We apologize for the inconvenience and thank you for your patience and continued support. Affected networks will once again see the relevant Third-Party Audience segments as active.
We're investigating reports of an issue with Play Integrity API. We will provide more information shortly.
The problem with Play Integrity API has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.
Released the May 2026 core update . The rollout may take up to 2 weeks to complete.
The rollout was complete as of June 2, 2026.
Description: We are experiencing an issue with Gmail beginning on Thursday, 2026-05-21 at 00:00 PDT. Mitigation efforts are currently underway by our engineering team. We will provide the next update by Thursday, 2026-05-21 at 09:30 PDT. Diagnosis / customer symptoms: Gmail users are experiencing delayed delivery of messages sent from the bank.in domains. Workaround: None at this time.
Description: Our internal telemetry shows that the issue with Gmail has been resolved for all affected users as of Thursday, 2026-05-21 at 08:47 US/Pacific. Our engineering team is actively monitoring the system to ensure continued stability. Diagnosis / customer symptoms: Customers should expect new messages to be delivered normally, older emails could take some time as the senders continue to retry. Workaround: This issue is now mitigated.
Description: We are continuing to investigate an issue with NotebookLM where customers may experience a temporary downgrade in their account tier. Our engineering team has identified a potential root cause related to a recent software update and is currently working on a mitigation plan. We will provide an update by Tuesday, 2026-05-19 20:30 PDT with current details. Customer symtomps: Customers may notice lower resource limits (e.g., hitting limits for Studio artifacts, source count per notebook, etc) and the absence of premium features like advanced sharing and analytics. Workaround: None at this time
Description: We are continuing to investigate an issue with NotebookLM where customers may experience a temporary downgrade in their account tier. Our engineering team has identified a potential root cause related to a recent software update and is currently working on a mitigation plan. We will provide an update by Tuesday, 2026-05-19 22:00 PDT with current details. Symptoms: Customers may notice lower resource limits (e.g., hitting limits for Studio artifacts, source count per notebook, etc) and the absence of premium features like advanced sharing and analytics. Workaround: None at this time.
Description: The issue with NotebookLM has been resolved for all affected users as of Tuesday, 2026-05-19 21:04 PDT. From preliminary analysis, the issue was triggered by a recent software update resulting in accounts on premium plans being incorrectly recognized as free accounts. The issue was mitigated by restoring the system to a previous stable state, which successfully reinstated the appropriate service tiers for all affected accounts. We thank you for your patience while we worked on resolving the issue. Symptoms: Customers may have noticed lower resource limits (e.g., hitting limits for Studio artifacts, source count per notebook, etc) and the absence of premium features like advanced sharing and analytics. Workaround: None at this time.
The issue was triaged and a fix has been found. We will update soon on expected end of this disruption.
The fix has mitigated the issue and we are actively rolling it out. We expect the rollout to complete within 6 hours.
The fix has been rolled out and service has returned to normal
Description: We were experiencing an issue with Cameyo by Google, beginning on Tuesday, 12 May 2026 09:01 US/Pacific. The issue was mitigated on Tuesday, 12 May 2026 15:16 US/Pacific by restarting the RAP system service, and performing full server reboots. From preliminary investigation, this was caused by a faulty code for logging improvement on the Player VMs. Log files were unexpectedly duplicated until the disk was full leading to the session failures. Some customers were recovered automatically after the channel binaries were rolled back, while the others were required to restart their VMs manually. Currently, the issue is fully mitigated and change is rolled back. We apologise to those who were impacted by this issue. Customer symptoms: The customers were experiencing an issue that couldn’t connect to the Player VMs normally. The disk utilization on the affected VMs reaches 99% or even 100%. Workaround: Not needed because all affected servers have been mitigated.
Firebase Test Lab is experiencing higher wait times on ARM devices. We are currently investigating the cause. Next update in when something significantly changes.
Firebase Test Lab is no longer experiencing delays for tests on ARM devices. Unless something unexpected happens, this is the last update.
Description: We are experiencing an issue with Classroom beginning at Wednesday, 2026-04-29 11:30 PDT. Our engineering team continues to investigate the issue. We will provide more information by Wednesday, 2026-04-29 13:00 PDT. Symptoms: Affected users may experience issues accessing classroom. Workaround: No workarounds available at this time.
Description: Our engineering team has identified the cause and working on mitigation of the issue . The mitigation is expected to complete by Wednesday, 2026-04-29 15:00 PDT. We will provide more information by Wednesday, 2026-04-29 15:15 PDT. Symptoms: Affected users may experience issues accessing classroom. Workaround: No workarounds available at this time.
Description: A fix has been deployed, and services have stabilized for the majority of users. We are aware that a small subset of users may still encounter errors. Our engineering team is actively working on a secondary resolution to address these remaining users. Full resolution for remaining users is expected to complete by Wednesday, 2026-04-29 14:00 PDT. We will provide an update by Wednesday, 2026-04-29 14:15 PDT with current details. Symptoms: Affected users may experience issues accessing classroom. Workaround: No workarounds available at this time.
Description: A fix has been deployed, and services have stabilized for all users. The issue with Google Classroom has been resolved for all affected users as of Wednesday, 2026-04-29 13:45 PDT. The issue was due to an internal software migration. Our engineers have mitigated the issue by rolling back the migration for impacted users. We thank you for your patience while we worked on resolving the issue. Symptoms: Affected users may have experienced issues accessing the classroom. Workaround: The issue is resolved.
Firebase Test Lab is experiencing delayed tests on ARM devices. We are currently investigating the cause.
The problem with Firebase Test Lab has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.
We're aware of a problem with AdMob affecting a majority of users. We will provide an update by Apr 29, 2026, 1:00 AM UTC detailing when we expect to resolve the problem. Please note that this resolution time is an estimate and may change. The affected users are able to access AdMob, but are seeing error messages, high latency, and/or other unexpected behavior. Google AdMob publishers are experiencing zero or low match rates for newly published iOS apps. There is currently no workaround.
We are continuing to investigate this issue. We will provide an update by Apr 29, 2026, 7:00 PM UTC detailing when we expect to resolve the problem. The affected users are able to access AdMob, but are seeing error messages, high latency, and/or other unexpected behavior. Google AdMob publishers are experiencing zero or low match rates for newly published iOS apps. Engineering has identified the root cause and is developing a resolution. There is currently no workaround.
We are continuing to investigate this issue. We will provide an update by Apr 30, 2026, 12:00 AM UTC detailing when we expect to resolve the problem. The affected users are able to access AdMob, but are seeing error messages, high latency, and/or other unexpected behavior. Google AdMob publishers are experiencing zero or low match rates for newly published iOS apps. Engineering is continuing to develop a resolution. There is currently no workaround.
The problem with AdMob should be resolved for the vast majority of affected users. We will continue to work towards restoring service for the remaining affected users, but no further updates will be added to this dashboard. The affected users are able to access AdMob, but are seeing error messages, high latency, and/or other unexpected behavior. Google AdMob publishers should now see expected match rates for newly published iOS apps.
Description: We are experiencing an issue with AppSheet beginning at Tuesday, 2026-04-28 00:30 PDT. Our engineering team continues to investigate the issue. We will provide an update by Tuesday, 2026-04-28 09:00 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Affected customers would experience slow loading times and internal server errors for AppSheet apps. Workaround: None at this time.
Description: Our engineering team has implemented a fix and system telemetry indicates that latency and error rates have returned to normal levels. We are continuing to monitor the environment closely to ensure full stability. We will provide an update by Tuesday, 2026-04-28 10:30 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Affected customers would experience slow loading times and internal server errors for AppSheet apps. Workaround: None at this time.
Description: The issue with AppSheet has been resolved for all affected users as of Tuesday, 2026-04-28 08:50 PDT. We thank you for your patience while we worked on resolving the issue. Symptoms: Affected customers would have experienced slow loading times and internal server errors for AppSheet apps.
We're investigating the issue and determining the cause
We've redirected our traffic so newly created tests should run. We're still investigating and working to fix currently stuck tests
We believe we've addressed the issue and stuck tests will now run. They may still be delayed as the system works through the queue
No updates so far
Problem appears to be mitigated and the error rates are back to normal level.