Google Outage History

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.

The problem with Firebase Test Lab has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.

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: 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.

The problem with Google Ad Manager has been resolved. We apologize for the inconvenience and thank you for your patience and continued support. The issue causing stale data to display in the "suggested ad units" UI in Ad Manager has now been resolved.

Description: The issue with Admin Console has been resolved for all affected users as of Friday, 2026-04-10 07:50 PDT. Suspected CL have been rolled back and we are seeing in our graphs errors rate have gone down. Customers also confirmed that issues have been mitigated. We thank you for your patience while we worked on resolving the issue. Customer symptoms: Google Workspace users using Google IdP were unable to sign into their accounts using security keys and hardware based passkeys. Workaround: Below steps should be performed by Admin as the workaround: * Admin should revoke the key. * Admin to create the verification code to sign-in. * The user should sign-in using Backup verification code and then re-enrolls the security key.

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

Problem appears to be mitigated and the error rates are back to normal level.

The problem with Content API for Shopping and Feeds has been resolved. We apologize for the inconvenience and thank you for your patience and continued support. The affected users are able to access Content API for Shopping and Feeds, but are seeing error messages, high latency, and/or other unexpected behavior.

Description: The issue with AppSheet has been resolved for all the affected customers as of Wednesday, 2026-04-08 15:40 US/Pacific. As per the preliminary analysis, the issue was triggered by a recent change that caused the users to be erroneously redirected to the asia-southeast region. Our engineering team rolled back the change to mitigate the impact and verified the service stability. We thank you for your patience while we worked on resolving the issue. Customer symptoms: Users may have experienced automatic redirection to asia-southeast.appsheet.com, resulting in errors when attempting to access their apps. Workaround: None at this time.

Description: The issue with Gmail has been resolved for all affected users as of Wednesday, 2026-04-08 14:49 PDT. Our engineering team identified a potential issue with a noisy neighbour and has successfully mitigated impact. A full root cause analysis is in progress and further details will be shared through a subsequent incident report. We thank you for your patience while we worked on resolving the issue. Symptoms: Customers may have experienced delays in receiving and sending emails. Workaround: None at this time.

Preliminary Incident Report We apologize for the inconvenience this Gmail service disruption may have caused. We would like to provide some information about this incident below. Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. A final Incident Report with preventative actions will be posted once our investigation is complete. If you have experienced an impact outside of what is listed below, please reach out to Google Workspace Support using the help article https://support.google.com/a/answer/1047213. Date/Time of the Issue (All time US/Pacific) - Incident Start: 08 April 2026 06:30 - Incident End: 08 April 2026 14:40 - Duration: 8 hours, 10 minutes Summary On Wednesday, 08 April 2026, Gmail customers may have experienced delays/failures when sending or receiving emails. The impact lasted for a duration of 8 hours, 10 minutes. The issue primarily affected the delivery of messages to external recipient domains, where impacted users observed delays or received failure messages when sending emails. To our customers whose communications were impacted during this disruption, we sincerely apologize. This is not the level of quality and reliability we strive to offer you, and we are taking immediate steps to improve the platform’s performance and availability. Preliminary Root Cause The preliminary root cause was identified as increased connection errors to some external mail services. Google engineers have begun a full root cause analysis and will provide additional information once it is available. Remediation The issue was detected by our engineering team through internal alerts. Engineering teams immediately started an investigation and took the following steps to contain the impact: Account Suspension: One of the domains responsible for spamming was identified, resulting in the suspension of the abusive account after review. Traffic Blocking: A block rule was implemented to specifically address and stop traffic originating from an abusive sending domain. Teams monitored rejection rates until they returned to normal levels, confirming that the system was healthy for over an hour to confirm resolution. Google is committed to improving its technology and operations to prevent similar service disruptions. A comprehensive Incident Report that will be published to provide further details and outline preventative measures. Description of Impact On Wednesday, 8 April 2026, starting at approximately 06:30, Gmail customers may have experienced delays/failures when sending or receiving emails. The issue primarily affected the delivery of messages to external recipient domains, with impacted users receiving bounce messages. Specifically, some users observed error messages stating, "The user you are trying to contact is receiving email at a rate that prevents additional messages from being delivered".

Incident Report Summary On Wednesday, 08 April 2026, Gmail customers may have experienced delays/failures when sending or receiving emails. The impact lasted for a duration of 8 hours, 10 minutes. The issue primarily affected the delivery of messages to external recipient domains, where impacted users observed delays or received failure messages when sending emails. To our customers whose communications were impacted during this disruption, we sincerely apologize. This is not the level of quality and reliability we strive to offer you, and we are taking immediate steps to improve the platform’s performance and availability. Root Cause The root cause was identified as increased connection errors to external mail services hosted by a specific 3rd party provider. Remediation and Prevention The issue was detected by our engineering team through internal alerts. Engineering teams immediately started an investigation and took the following steps to contain the impact: External Mail Provider Reachout: Google worked with the external mail provider to unblock connections and prevent similar issues in the future. Teams monitored rejection rates until they returned to normal levels, verifying that the system was healthy for over an hour to confirm resolution. Google is committed to improving its technology and operations to prevent similar service disruptions. Google is committed to preventing a repeat of this issue in the future and is completing the following actions: - Deploy systems to proactively track external blocklists and alert on degradation before users are impacted. - Improve monitoring and alerting systems to proactively detect errors related to external email recipient communication. Detailed Description of Impact On Wednesday, 8 April 2026, starting at approximately 06:30 PDT, Gmail customers may have experienced delays/failures when sending or receiving emails. The issue primarily affected the delivery of messages to external recipient domains, with impacted users receiving bounce messages. Specifically, some users observed error messages stating, "The user you are trying to contact is receiving email at a rate that prevents additional messages from being delivered".

This issue appears to be resolved now. Error rates are back to normal.

Services are functioning normally as of 2026-03-30 09:00 PDT

The problem with 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.

The rollout was complete as of April 8, 2026.

The rollout was complete as of March 25, 2026.

The logs from the missing period should be restored. However, metrics may not have fully been restored from the time period due to technical limitations.

Description: The issue has been mitigated as of Friday, 2026-03-20 22:03 US/Pacific. The service issue which resulted in connection timeouts and 502 error pages, was caused by excess traffic impacting the keep.google.com. Our engineering team has implemented a mitigation and is continuing to work to ensure long-term service stability and prevent recurrence. We thank you for your patience while we worked on resolving the issue.

The problem with Play Billing Purchases has been resolved. We apologize for the inconvenience and thank you for your patience and continued support. Some users in Indonesia experienced error messages when attempting to complete a purchase using a regional cash payment method. This was due to a service disruption at a third-party payment provider.

The rollback is complete - service is fully restored.

Description: The issue with Google Workspace has been resolved for all affected users as of Friday, 2026-03-13 07:30 PDT. From preliminary analysis, the incident was triggered by resource contention in the impacted location, following a recent update. This led to elevated error rates and latency for several Workspace products. Our engineering teams mitigated the impact by increasing infrastructure capacity,performing traffic restarts, and rolling back the identified change We thank you for your patience while we worked to resolve this issue. Customer symptoms: A subset of customers may have experienced elevated error rates when accessing the impacted products in the US region. Workaround: NA. Issue is now mitigated

This should be resolved for all customers. Please contact Firebase Support if you encounter this issue again.

We are currently experiencing high error rates on the Firebase console. Investigations are ongoing.

All BigQuery export jobs for Firebase Crashlytics have caught up.

The issue has been resolved. Please file a bug with Firebase support if you see any continued errors.