Google Outage History

Started Feb 23, 2026, 06:32 AM UTC· resolved Feb 23, 2026, 08:35 AM UTC

1. investigating Feb 23, 2026, 08:17 AM UTC

   Description: Our engineering team continues to investigate the issue. We will provide an update by Monday, 2026-02-23 00:45 PST with current details. We apologize to all who are affected by the disruption. Customer symptoms: Users may experience errors when attempting to create new conversations or spaces in Google Chat. Existing conversations remain functional. Workaround: None at the moment

2. investigating Feb 23, 2026, 08:34 AM UTC

   Description: Our engineering teams are actively working on mitigation efforts to restore the ability to create new conversations as quickly as possible. We do not have any ETA at the moment. We will provide an update by Monday, 2026-02-23 01:30 PST with current details. Customer symptoms: Users may experience errors when attempting to create new Direct Messages (DM) or new chat spaces in Google Chat. This issue specifically affects the creation of new conversations; however, users can continue to send and receive messages in existing conversations and spaces Workaround: None at the moment

3. resolved Feb 23, 2026, 08:54 AM UTC

   The issue with Google Chat has been resolved for all affected users as of Monday, 2026-02-23 00:35 PST. As per our preliminary analysis, the incident was triggered by a recent configuration update. Our engineering team performed a rollback to mitigate the impact and verified the stability. We thank you for your patience while we worked on resolving the issue.

Read the full incident report →

Started Feb 05, 2026, 05:00 PM UTC· resolved Feb 27, 2026, 10:00 AM UTC

1. monitoring Feb 05, 2026, 05:03 PM UTC

   Released the February 2026 Discover core update for English language users in the US (will look to expand it to all countries and languages in the future). This update is designed to improve the quality of Discover overall. Our guidance about general core updates and Discover applies. The rollout may take up to 2 weeks to complete.

2. resolved Feb 27, 2026, 10:02 AM UTC

   The rollout was complete as of February 27, 2026.

Read the full incident report →

Started Feb 04, 2026, 02:00 PM UTC· resolved Feb 21, 2026, 08:00 AM UTC

1. investigating Feb 20, 2026, 02:43 PM UTC

   We're investigating reports of an issue with Feeds. We will provide more information shortly.

2. resolved Feb 21, 2026, 10:58 AM UTC

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

Read the full incident report →

Started Jan 24, 2026, 01:02 PM UTC· resolved Jan 24, 2026, 05:55 PM UTC

1. investigating Jan 24, 2026, 04:34 PM UTC

   Gmail users might see banners indicating missing spam checks. We are experiencing an issue with Gmail beginning on Saturday, 2026-01-24 05:02 US/Pacific. Users might experience the following banner: “Be careful with this message. Gmail hasn't scanned this message for spam, unverified senders, or harmful software.” We advise the users to be extra diligent in lieu of missing spam checks. Our engineering team is investigating the issue. We will provide an update by Saturday, 2026-01-24 09:30 with current details.

2. monitoring Jan 24, 2026, 05:51 PM UTC

   Description We are experiencing an issue with Gmail beginning on Saturday, 2026-01-24 05:02 US/Pacific. We are aware that some Gmail users are experiencing misclassification of emails in their inbox and additional spam warnings. We are actively working to resolve the issue. As always, we encourage users to follow standard best practices when engaging with messages from unknown senders. We will provide an update by Saturday, 2026-01-24 11:00 US/Pacific with current details

3. monitoring Jan 24, 2026, 06:54 PM UTC

   Description We are experiencing an issue with Gmail beginning on Saturday, 2026-01-24 05:02 US/Pacific. We are aware that some Gmail users are experiencing misclassification of emails in their inbox and additional spam warnings. We are actively working to resolve the issue. As always, we encourage users to follow standard best practices when engaging with messages from unknown senders. We will provide an update by Saturday, 2026-01-24 12:00 US/Pacific with current details.

4. monitoring Jan 24, 2026, 08:15 PM UTC

   Description We are experiencing an issue with Gmail beginning on Saturday, 2026-01-24 05:02 US/Pacific. We are aware that some Gmail users are experiencing misclassification of emails in their inbox and additional spam warnings. We are actively working to resolve the issue. As always, we encourage users to follow standard best practices when engaging with messages from unknown senders. We will provide an update by Saturday, 2026-01-24 13:30 US/Pacific with current details.

5. monitoring Jan 24, 2026, 11:00 PM UTC

   Description We are experiencing an issue with Gmail beginning on Saturday, 2026-01-24 05:02 US/Pacific. We are aware that some Gmail users are experiencing misclassification of emails in their inbox and additional spam warnings. We are actively working to resolve the issue. As always, we encourage users to follow standard best practices when engaging with messages from unknown senders. We will provide an update by Saturday, 2026-01-24 14:00 US/Pacific with current details.

6. monitoring Jan 25, 2026, 12:07 AM UTC

   Description We are experiencing an issue with Gmail beginning on Saturday, 2026-01-24 05:02 US/Pacific. We are aware that some Gmail users are experiencing misclassification of emails in their inbox and additional spam warnings. We are actively working to resolve the issue. As always, we encourage users to follow standard best practices when engaging with messages from unknown senders. We will provide an update by Saturday, 2026-01-24 17:00 US/Pacific with current details.

7. monitoring Jan 25, 2026, 01:28 AM UTC

   Summary : Some Gmail users experienced a misclassification of emails in their inbox, additional spam warnings, and delays in receiving email. Description : The issue with Gmail email classification is resolved as of Saturday, 2026-01-24 09:55 US/Pacific. We will publish an analysis of this incident once we have completed our internal investigation. We thank you for your patience while we worked on resolving the issue. Diagnosis / Customer Symptoms : Some Gmail users experienced a misclassification of emails in their inbox, delays in receiving email. Additionally, misclassified spam warnings from the incident may persist for existing messages received before the issue resolution.

8. resolved Jan 30, 2026, 07:26 PM UTC

   User experience: - Warning Banners: Users received a banner on incoming messages stating: "Be careful with this message. Gmail hasn't scanned this message for spam, unverified senders, or harmful software." - Delivery Delays: Impacted messages experienced delivery delays, majorly between 5 to 10 minutes. However, there were no instances of lost emails or erroneously delivered during this period. - Some users may have noticed that promotional or social labels were not correctly applied during the disruption.

9. resolved Feb 06, 2026, 04:32 AM UTC

   User experience: * Warning Banners: Users received a banner on incoming messages stating: "Be careful with this message. Gmail hasn't scanned this message for spam, unverified senders, or harmful software." * Delivery Delays: Impacted messages experienced delivery delays, up to 10 minutes. However, there were no instances of lost emails or erroneously delivered during this period. * Message Labeling: Users may have noticed that promotional or social labels were not correctly applied during the disruption.

Read the full incident report →

Started Jan 14, 2026, 10:30 PM UTC· resolved Jan 16, 2026, 12:30 AM UTC

1. monitoring Jan 16, 2026, 12:25 AM UTC

   We're currently investigating this issue.

2. resolved Jan 16, 2026, 12:43 AM UTC

   We believe the issue has been mitigated. Please reach out to Firebase support if the error is still present in new builds.

Read the full incident report →

Started Jan 13, 2026, 06:00 PM UTC· resolved Jan 15, 2026, 09:00 PM UTC

1. investigating Jan 15, 2026, 01:44 AM UTC

   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. Google Ad Manager is experiencing systemic decline in Ad Exchange (AdX) match rates and delivery.

2. investigating Jan 15, 2026, 04:51 AM UTC

   Our team is continuing to investigate this issue. We will provide an update by Jan 15, 2026, 2:00 PM UTC with more information about this problem. Thank you for your patience. The affected users are able to access Google Ad Manager, but are seeing error messages, high latency, and/or other unexpected behavior. Google Ad Manager is experiencing systemic decline in Ad Exchange (AdX) match rates and delivery specifically impacting Google demand sources (Google Ads and DV360). The impact appears to be concentrated on Web and mWeb display inventory.

3. investigating Jan 15, 2026, 02:42 PM UTC

   Our team is continuing to investigate this issue. We will provide an update by Jan 15, 2026, 7:00 PM UTC with more information about this problem. Thank you for your patience. The affected users are able to access AdSense and Google Ad Manager, but are seeing error messages, high latency, and/or other unexpected behavior. Google Ad Manager and Adsense for Content (AFC) is experiencing systemic decline in Ad Exchange (AdX) match rates and delivery specifically impacting Google demand sources (Google Ads and DV360). The impact appears to be concentrated on Web and mWeb display inventory.

4. investigating Jan 15, 2026, 07:10 PM UTC

   Our team is continuing to investigate this issue. We will provide an update by Jan 15, 2025, 10:00 PM UTC with more information about this problem. Thank you for your patience. The affected users are able to access AdSense and Google Ad Manager, but are seeing error messages, high latency, and/or other unexpected behavior. Google Ad Manager and Adsense for Content (AFC) is experiencing systemic decline in Ad Exchange (AdX) match rates and delivery specifically impacting Google demand sources (Google Ads and DV360). The impact appears to be concentrated on Web and mWeb display inventory.

5. resolved Jan 15, 2026, 09:57 PM UTC

   The problem with AdSense and Google Ad Manager has been resolved. We apologize for the inconvenience and thank you for your patience and continued support. The issue impacting match rates and delivery of Google demand sources (Google Ads and DV360) on Ad Exchange (AdX) and AdSense for Content (AFC) inventory has been resolved.

Read the full incident report →

Started Jan 08, 2026, 01:00 PM UTC· resolved Jan 14, 2026, 09:00 PM UTC

1. monitoring Jan 13, 2026, 11:10 PM UTC

   Description: We are experiencing an issue with sending MMS messages via Google Voice beginning on Thursday, 2026-01-08 05:00 PST. Our engineering team continues to investigate the issue with a 3rd party vendor. We will provide an update by Tuesday, 2026-01-13 20:30 PST with current details. We apologize to all who are affected by the disruption. Customer symptoms: Google Voice customers may experience issues while sending MMS messages where the messages may appear to be successfully sent but recipients may not receive them. Workaround: SMS messages can be sent successfully, so the users can send 1-to-1 messages or messages without attachments instead of MMS messages.

2. monitoring Jan 14, 2026, 04:16 AM UTC

   Description: We are experiencing an issue with sending MMS messages via Google Voice beginning on Thursday, 2026-01-08 05:00 PST. Our engineering team continues to investigate the issue with a 3rd party vendor to mitigate the issue. We will provide an update by Wednesday, 2026-01-14 10:30 PST with current details. Customer symptoms: Google Voice customers may experience issues while sending MMS messages where the messages may appear to be successfully sent but recipients may not receive them. Workaround: SMS messages can be sent successfully, so the users can send 1-to-1 messages or messages without attachments instead of MMS messages.

3. monitoring Jan 14, 2026, 06:33 PM UTC

   Description: We are experiencing an issue with sending MMS messages via Google Voice beginning on Thursday, 2026-01-08 05:00 PST. Our engineering team continues to investigate the issue with a 3rd party vendor to mitigate the issue. We will provide an update by Thursday, 2026-01-15 10:30 PST with current details. Customer symptoms: Google Voice customers may experience issues while sending MMS messages where the messages may appear to be successfully sent but recipients may not receive them. Workaround: SMS messages can be sent successfully, so the users can send 1-to-1 messages or messages without attachments instead of MMS messages.

4. resolved Jan 14, 2026, 09:30 PM UTC

   The issue with Google Voice has been resolved for all affected users as of Wednesday, 2026-01-14 13:00 PST. We thank you for your patience while we worked on resolving the issue.

Read the full incident report →

Started Jan 07, 2026, 03:00 PM UTC· resolved Jan 17, 2026, 08:00 AM UTC

1. investigating Jan 12, 2026, 03:14 PM UTC

   The daily Crashlytics BigQuery export job is delayed for Jan 7 to 9. We are working on populating these daily tables, and are investigating the cause. Streaming BigQuery table data is not impacted.

2. resolved Jan 17, 2026, 01:46 PM UTC

   All dates have been processed up to January 16.

Read the full incident report →

Started Jan 07, 2026, 04:16 AM UTC· resolved Jan 07, 2026, 07:30 AM UTC

1. investigating Jan 07, 2026, 05:04 AM UTC

   We're investigating reports of an issue with AdMob. We will provide more information shortly. The affected users are able to access AdMob, but are seeing error messages, high latency, and/or other unexpected behavior. App Open ads are not closable on both iOS and Android platforms. The Close button is missing preventing users from exiting the advertisement to access the app. To avoid these App open ads from showing up, publisher can temporarily pause the ad units serving Open Ads until the issue is fixed.

2. investigating Jan 07, 2026, 07:03 AM UTC

   We expect to resolve the problem affecting a majority of users of AdMob and Google Ad Manager at Jan 6, 2026, 7:25 PM UTC. Please note that this time frame is an estimate and may change. The affected users are able to access AdMob and Google Ad Manager, but are seeing error messages, high latency, and/or other unexpected behavior. App Open ads are not closable on both iOS and Android platforms. The Close button is missing preventing users from exiting the advertisement to access the app. For the publishers who have temporarily paused the ad units to prevent Open Ads from serving, please stand by to enable them back as we expect the fix to be in production in a few minutes.

3. resolved Jan 07, 2026, 07:30 AM UTC

   The problem with AdMob and Google Ad Manager has been resolved. We apologize for the inconvenience and thank you for your patience and continued support. The affected users are able to access AdMob and Google Ad Manager, but are seeing error messages, high latency, and/or other unexpected behavior. App Open ads close button is now visible. Closing App Open ads on both iOS and Android platforms is no longer an issue.

Read the full incident report →

Started Jan 06, 2026, 09:10 PM UTC· resolved Jan 07, 2026, 03:46 AM UTC

1. investigating Jan 07, 2026, 01:18 AM UTC

   We are experiencing an issue with Firebase Realtime Database beginning on Tuesday, 2026-01-06 13:10 PST. Impacted customers may experience request timeouts and/or errors when using the Firebase Realtime Database SDK or directly through APIs. Our engineering team has identified the root cause of the issue and the fix rollout is currently in progress. The vast majority of customers should stop experiencing issues and we're working to mitigate the impact for rest. We will provide an update by Tuesday, 2026-01-06 18:00 PST with current details. We apologize to all who are affected by the disruption.

2. investigating Jan 07, 2026, 02:03 AM UTC

   Our engineering team has identified a recent change which has triggered the issue. The engineering team is currently rolling back the change to mitigate the impact. While the majority of the impact is already subsided, we do not have ETA for full mitigation at this time. We will provide an update by Tuesday, 2026-01-06 20:00 PST with current details.

3. resolved Jan 07, 2026, 03:50 AM UTC

   The 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 engineering team rolled back the change to mitigate the impact. We thank you for your patience while we worked on resolving the issue.

Read the full incident report →

Started Jan 03, 2026, 07:54 PM UTC· resolved Jan 03, 2026, 09:05 PM UTC

1. investigating Jan 03, 2026, 08:46 PM UTC

   We're investigating reports of an issue with Android LoadPaymentData API. We will provide more information shortly.

2. resolved Jan 03, 2026, 09:04 PM UTC

   The problem with Android LoadPaymentData API has been resolved. After further investigation, we believe the issue existed outside of Google's infrastructure. No further updates will be added to this dashboard.

3. resolved Jan 03, 2026, 09:05 PM UTC

   Incident began at 2026-01-03 19:54 and ended at 2026-01-03 21:05 (times are in Coordinated Universal Time (UTC)). The problem with Android LoadPaymentData API has been resolved. After further investigation, we believe the issue existed outside of Google's infrastructure. No further updates will be added to this dashboard. Affected products: Android LoadPaymentData API

Read the full incident report →

Started Dec 17, 2025, 06:00 PM UTC· resolved Dec 18, 2025, 04:00 AM UTC

1. investigating Dec 17, 2025, 11:58 PM UTC

   Webpush topic subscriptions may be throttled for some registrations. The team has identified a mitigation and is currently working on a fix.

2. resolved Dec 18, 2025, 04:00 PM UTC

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

Read the full incident report →

Started Dec 11, 2025, 05:25 PM UTC· resolved Dec 29, 2025, 07:00 PM UTC

1. monitoring Dec 11, 2025, 05:25 PM UTC

   Released the December 2025 core update . The rollout may take up to 3 weeks to complete.

2. resolved Dec 29, 2025, 07:05 PM UTC

   The rollout was complete as of December 29, 2025.

Read the full incident report →

Started Dec 04, 2025, 08:30 PM UTC· resolved Dec 04, 2025, 10:00 PM UTC

1. investigating Dec 04, 2025, 10:04 PM UTC

   We're investigating reports of an issue with Web LoadPaymentData API. We will provide more information shortly. The affected users are able to access Web LoadPaymentData API, but are seeing error messages, high latency, and/or other unexpected behavior.

2. resolved Dec 04, 2025, 10:45 PM UTC

   The problem with Web LoadPaymentData API has been resolved. We apologize for the inconvenience and thank you for your patience and continued support.

Read the full incident report →

Started Dec 04, 2025, 12:27 AM UTC· resolved Dec 04, 2025, 01:09 AM UTC

1. investigating Dec 04, 2025, 01:37 AM UTC

   Next.js app builds were failing due to an issue in a recent update to the App Hosting Next.js adapter. The change has been rolled back and we believe the issue has been mitigated.

2. resolved Dec 04, 2025, 01:41 AM UTC

   Affected builds will have failed with the error "Cannot find package 'semver'". This is now fully rolled back and mitigated.

Read the full incident report →

Started Dec 02, 2025, 11:02 PM UTC· resolved Dec 03, 2025, 04:30 AM UTC

1. investigating Dec 03, 2025, 12:42 AM UTC

   We're aware of a problem with Firebase Test Lab causing very slow test allocation times. We will provide an update by 6:00PM PST detailing when we expect to resolve the problem. Please note that this resolution time is an estimate and may change.

2. investigating Dec 03, 2025, 02:06 AM UTC

   Our team is continuing to investigate this issue. We will provide an update by 7:00PM PST with more information about this problem. Thank you for your patience.

3. resolved Dec 03, 2025, 04:42 AM UTC

   The issue is resolved. Some device may have increased latency for a few more hours.

Read the full incident report →

Started Dec 01, 2025, 08:00 AM UTC· resolved Dec 04, 2025, 09:23 PM UTC

1. monitoring Dec 02, 2025, 04:20 AM UTC

   Description: Google Workspace released a feature to a subset of Workspace customers Continue your conversations in Google Chat (https://support.google.com/meet/answer/9308979?visit_id=639002449653293387-821172296&p=chat_in_meet&rd=1). Some Google Workspace users are experiencing issues with Google Meet host controls for this feature. This may include inability to disable the feature or the ‘disable’ option not being visible under the host controls within Google Calendar meeting invites. We are investigating and will provide an update by Friday, 2025-12-05 10:00 PST with current details. We apologize to all who are affected by this issue. Symptoms: The impacted users are unable to observe Chat moderation settings under the Host Controls for ‘Continuous meeting chat’ feature. Workaround: None at this time.

2. monitoring Dec 02, 2025, 10:42 PM UTC

   Description: Google Workspace released a feature to a subset of Workspace customers Continue your conversations in Google Chat (https://support.google.com/meet/answer/9308979?visit_id=639002449653293387-821172296&p=chat_in_meet&rd=1). Some Google Workspace users are experiencing issues with Google Meet host controls for this feature. This may include inability to disable the feature or the ‘disable’ option not being visible under the host controls within Google Calendar meeting invites. To resolve the issues impacting host controls for the "Continue your conversations in Google Chat" feature, we are in the process of rolling back this feature. We will provide a further update by Monday, 2025-12-08 10:00 PST. We apologize to all who are affected by this issue. Symptoms: The impacted users are unable to observe Chat moderation settings under the Host Controls for ‘Continuous meeting chat’ feature. Workaround: None at this time.

3. resolved Dec 04, 2025, 09:28 PM UTC

   Description: The rollback of the "Continue your conversations in Google Chat" feature in Google Meet is now complete. This resolves the issues some users experienced, including the inability to disable the feature and the missing toggle in Calendar host controls. We will commence the rollout of this feature again starting Monday, 2025-12-08. No further updates will be provided here. For more detailed information regarding the updated rollout schedule, please refer to the Google Workspace Updates Blog (https://workspaceupdates.googleblog.com/2025/11/continue-conversations-google-chat-google-meet.html). We apologize for the disruption this may have caused. Symptoms: The impacted users are unable to observe Chat moderation settings under the Host Controls for ‘Continuous meeting chat’ feature. Workaround: None at this time.

Read the full incident report →

Started Nov 27, 2025, 12:08 PM UTC· resolved Nov 27, 2025, 01:38 PM UTC

1. investigating Nov 27, 2025, 12:09 PM UTC

   Firebase Remote Config is currently experiencing a service disruption. Please check back for status.

2. resolved Nov 27, 2025, 01:37 PM UTC

   Issue is now mitigated

Read the full incident report →

Started Nov 26, 2025, 05:34 AM UTC· resolved Nov 26, 2025, 10:30 AM UTC

1. investigating Nov 26, 2025, 07:38 AM UTC

   Description: We are experiencing an issue with Google Meet beginning on Tuesday, 2025-11-25 21:34 PST. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2025-11-26 02:00 PST with current details. We apologize to all who are affected by the disruption. Symptoms: Customers are experiencing issues loading meet.google.com. Workaround: Customers can use the mobile version to load Meet.

2. investigating Nov 26, 2025, 08:38 AM UTC

   Description: We are experiencing an issue with Google Meet beginning on Tuesday, 2025-11-25 21:34 PST. Our engineering team continues to investigate the issue and work on a mitigation strategy. We will provide an update by Wednesday, 2025-11-26 02:00 PST with current details. We apologize to all who are affected by the disruption. Symptoms: Customers are experiencing issues loading meet.google.com. Workaround: Customers can use the mobile version to load Meet.

3. investigating Nov 26, 2025, 09:33 AM UTC

   Description: We are experiencing an issue with Google Meet beginning on Tuesday, 2025-11-25 21:34 PST. Our engineering team continues to investigate the issue and work on a mitigation strategy. We will provide an update by Wednesday, 2025-11-26 03:00 PST with current details. We apologize to all who are affected by the disruption. Symptoms: Customers are experiencing issues loading meet.google.com. Workaround: Customers can use the mobile version to load Meet.

4. resolved Nov 26, 2025, 10:46 AM UTC

   Description: The issue with Google Meet has been resolved for all affected users as of Wednesday, 2025-11-26 02:30 PST. We will publish an analysis of this incident once we have completed our internal investigation. We thank you for your patience while we worked on resolving the issue. Symptoms: Customers experienced issues loading meet.google.com. This issue affected Google Meet traffic in Asia. Other regions were not affected. Workaround: None as the issue has been mitigated.

5. resolved Nov 27, 2025, 01:49 PM UTC

   # preliminary incident report: We apologize for the inconvenience this 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. If you have experienced 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. ## summary: Between 25 November 2025 21:34 US/Pacific and 26 November 2025 2:30 US/Pacific, Google Meet experienced a service disruption for a total duration of 5 hours and 10 minutes. A subset of Google Meet users in the Asia region were unable to start or join meetings via the web and on meeting devices. Google is committed to quickly and continually improving our technology and operations to prevent service disruptions. We appreciate your patience and apologize again for the impact to your organization. We thank you for your business. ## root cause: The incident was caused by an issue within the Meet web frontend server located in the Singapore (SIN) metropolitan area, which is a critical component and responsible for handling Google Meet connections for users in the Asia region. The issue began with a software update to the Meet web frontend server. Approximately three hours after this update was complete, a combination of traffic patterns and a code change creating a thread deadlock risk which is currently being investigated further, acted as the trigger for the outage. This trigger led to a sustained period of long-hanging requests in the server's processing queue. This abnormal workload ultimately consumed all available resources, causing the server to experience Out-Of-Memory (OOM) errors and subsequent task crashes. The result (effect) was that the server could not properly process requests, leading to failures when users attempted to load the meeting UI or join meetings. Furthermore, the issue detection was slightly delayed because traffic patterns in the immediate interval after the software update did not trigger the issue, delaying our response and mitigation efforts. ## remediation: The issue started on 25 November 2025 at 21:34 US/Pacific and the problem was first detected by Google's internal alerting systems at 21:41 US/Pacific. Our engineers promptly began working to restore service by taking the following actions in chronological order: 25 November, 22:08 US/Pacific - Draining of the most affected cluster Efforts were made to shift traffic away from the specific server cluster experiencing the crashes. 25 November, 22:20 US/Pacific - Increase in capacity Our engineers increased the resources available to the affected service. 25 November, 23:27 US/Pacific - Rollback of the webfrontend binary The most effective step taken was reverting the software on the Meet web frontend server back to the previous stable version. This action mitigated the issue and restored service availability. Service was fully restored on 26 November 2025 at 02:30 US/Pacific. ## detailed description of impact: A subset of Google Meet users in the Asia Pacific region experienced issues loading the meeting user interface (meet.google.com) or were unable to start or join meetings between 25 November 2025 21:34 US/Pacific and 26 November 2025 2:30 US/Pacific. The issue primarily affected users accessing Google Meet via Web browsers and Meeting Devices. Mobile users were not affected.

6. resolved Dec 02, 2025, 12:52 PM UTC

   ## summary: Between 25 November 2025 21:34 US/Pacific and 26 November 2025 2:30 US/Pacific, Google Meet experienced a service disruption for a total duration of 4 hours and 56 minutes. A subset of Google Meet users in Asia were unable to start or join meetings via the web and on meeting devices. Google is committed to quickly and continually improving our technology and operations to prevent service disruptions. We appreciate your patience and apologize again for the impact to your organization. We thank you for your business. ## root cause: The incident was caused by an issue within the Meet web frontend server located in the Singapore (SIN) metropolitan area, which is a critical component and responsible for handling Google Meet connections for users in the Asia region. The root cause of the issue was a software update to the Meet web frontend server. The update introduced a blocking call to a dependency in a critical code path, creating a thread deadlock risk. Approximately three hours after the update was complete, tasks started deadlocking. The trigger was a combination of regional traffic patterns and latency accessing the dependency involved. This led to stuck requests, Out-Of-Memory (OOM) errors and subsequent task crashes leading to failures when users attempted to load the meeting UI or join meetings. ## remediation and prevention: The issue started on 25 November 2025 at 21:34 US/Pacific and the problem was first detected by Google's internal alerting systems at 21:41 US/Pacific. Our engineers promptly began working to restore service by taking the following actions in chronological order: 25 November, 22:08 US/Pacific - Shifted traffic away from the most affected Meet web frontend servers. Efforts were made to shift traffic away from the specific Meet web frontend servers experiencing the crashes. 25 November, 22:20 US/Pacific - Increase in capacity Our engineers increased the resources available to the affected service. 25 November, 23:27 US/Pacific - Rollback of the webfrontend binary The most effective step taken was reverting the software on the Meet web frontend server back to the previous stable version. This action mitigated the issue and restored service availability. Service was fully restored on 26 November 2025 at 02:30 US/Pacific after the rollback was complete. Google is completing the following actions to prevent a repeat of this issue: - We are reviewing critical code paths to identify and address potential blocking operations for the dependency that resulted in the deadlocking. - We are adding additional checks to prevent adding blocking operations in critical code paths. - Increase the load in our canary environments to make it more likely to detect similar issues. ## detailed description of impact: A subset of Google Meet users in the Asia Pacific region experienced issues loading the meeting user interface (meet.google.com) or were unable to start or join meetings between 25 November 2025 21:34 US/Pacific and 26 November 2025 2:30 US/Pacific. The issue primarily affected users accessing Google Meet via Web browsers and Meeting Devices. Mobile users were not affected.

Read the full incident report →

Started Nov 24, 2025, 08:02 AM UTC· resolved Nov 24, 2025, 09:55 AM UTC

1. investigating Nov 24, 2025, 09:47 AM UTC

   Description: We are experiencing an issue with Google Chat beginning on Monday, 2025-11-24 00:02 PST. Our engineering team continues to investigate the issue. We will provide an update by Monday, 2025-11-24 03:00 PST with current details. We apologize to all who are affected by the disruption. Symptoms: Google Chat users might not be able to open chat while connecting from Europe. Workaround: None at this time.

2. investigating Nov 24, 2025, 10:06 AM UTC

   Description: The issue with Google Chat has been resolved for all affected users as of Monday, 2025-11-24 01:55 PST. We will publish an analysis of this incident once we have completed our internal investigation. We thank you for your patience while we worked on resolving the issue. Symptoms: Google Chat users might not be able to open chat while connecting from Europe. Workaround: None at this time.

3. resolved Nov 25, 2025, 06:28 PM UTC

   Preliminary Incident Report We apologize for the inconvenience this service disruption/outage 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. 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. Summary On Monday, 24 November 2025, Google Chat experienced an overload which led to service disruptions for users for a duration of 1 hour and 53 minutes. Customers encountered issues including the inability to send messages, load the chat application, and start new conversations. Some notifications were also incorrectly displayed with "Anonymous" as the sender Root Cause The trigger of the outage was transient errors served from an internal microservice in Europe that caused Chat backend processes to execute a fallback path to retrieve this data. The root cause was that the data retrieved from the fallback path subsequently caused an update to Chat metadata which were sent to user devices, causing those devices to reload data from Chat backend servers, thereby causing more updates to be sent to user devices, resulting in a cascading effect that overloaded Chat servers in Europe. Google engineers have implemented a mitigation to limit high rates of requests to prevent this cascading loop from recurring. Remediation Google engineers were alerted to the incident via alerts and immediately started an investigation. To fully mitigate the impact, our engineering teams took the following steps: 1. Increased Server Capacity: To handle the unexpected surge in traffic, we significantly increased the capacity of our servers in the affected region to ensure the system could process all incoming requests smoothly. 2. Limited the Rate of Metadata Updates: To prevent the cascading loop of requests from overloading Chat servers again, Google engineers have limited the rate of metadata updates so that Chat servers will not be overloaded in this way. 3. Paused Non-Essential Background Tasks: To prioritize the restoration of core chat functions, we temporarily halted several internal background processes. This action helped to reduce the overall load on our systems, freeing up resources to serve user traffic more effectively. 4. Gradual Traffic Restoration: Our automated defenses had initially blocked some traffic to prevent a complete system overload. A crucial part of the recovery was to gradually and carefully allow this traffic back. This controlled approach ensured that as users reconnected, the system wouldn't be overwhelmed again, allowing everyone to successfully re-establish their connection to Google Chat without getting stuck in a retry loop. Detailed Description of Impact For a duration of 1 hour and 53 minutes, Google Chat users in Europe experienced a service disruption which manifested as an inability to use core features of the service, such as sending messages and starting conversations.

4. resolved Nov 26, 2025, 11:56 PM UTC

   Incident Report Summary On Monday, 24 November 2025, Google Chat experienced an overload which led to service disruptions for users for a duration of 1 hour and 53 minutes. Customers encountered issues including the inability to send messages, load the chat application, and start new conversations. Some notifications were also incorrectly displayed with "Anonymous" as the sender. We deeply regret the disruption our Google Workspace customers experienced. We are committed to improving our platform's reliability and performance, and we are taking immediate steps to improve the platform’s performance and availability. Root Cause The trigger of the outage was transient errors served from an internal microservice in Europe that caused Chat backend processes to execute a fallback path to retrieve this data. The root cause was that the data retrieved from the fallback path subsequently caused an update to Chat metadata which were sent to user devices, causing those devices to reload data from Chat backend servers, thereby causing more updates to be sent to user devices resulting in a cascading effect that overloaded Chat servers in Europe. Google engineers have implemented a mitigation to limit high rates of requests to prevent this cascading loop from recurring. Remediation and Prevention Google engineers were alerted to the incident via alerts and immediately started an investigation. To fully mitigate the impact, our engineering teams took the following steps: 1. Increased Server Capacity: To handle the unexpected surge in traffic, we significantly increased the capacity of our servers in the affected region to ensure the system could process all incoming requests smoothly. 2. Limited the Rate of Metadata Updates: To prevent the cascading loop of requests from overloading Chat servers again, Google engineers have limited the rate of metadata updates so that Chat servers will not be overloaded in this way. 3. Paused Non-Essential Background Tasks: To prioritize the restoration of core chat functions, we temporarily halted several internal background processes. This action helped to reduce the overall load on our systems, freeing up resources to serve user traffic more effectively. 4. Gradual Traffic Restoration: Our automated defenses had initially blocked some traffic to prevent a complete system overload. A crucial part of the recovery was to gradually and carefully allow this traffic back. This controlled approach ensured that as users reconnected, the system wouldn't be overwhelmed again, allowing everyone to successfully re-establish their connection to Google Chat without getting stuck in a retry loop. Google is committed preventing a repeat of this issue in the future and is completing the following actions: * Fix the immediate cause: Stop errors in calls to the microservices from triggering metadata updates to devices. The fix prevents a cascading loop of client devices making requests back to Chat servers resulting in overload. * Prevent devices from sending excessive load: Implement changes in Chat web and mobile apps to prevent them from performing full reload of data from Chat servers when it is not needed. This reloading contributed greatly to the overload of Chat servers. * Improve Monitoring: Enhance monitoring to identify which specific metadata updates to user devices cause reloads in order to more quickly mitigate similar issues in the future. Detailed Description of Impact On Monday, 24 November 2025 at 00:02 US/Pacific, Google Chat users in Europe experienced a service disruption affecting core features of the service for a duration of 1 hour and 53 minutes. At its peak, the incident affected approximately 20.2% of users in Europe. The issue was resolved by 01:55 US/Pacific. Users encountered problems with the following core functionality: * Initial Application Load: Many users had trouble loading the Google Chat application. * Opening Chat Rooms: Users experienced errors when trying to open existing chat rooms. * Sending Messages: Users faced delays sending messages. * Increased Latency: There was an increase in message delivery latency for affected users. * Notification Rendering: Some notifications were also incorrectly displayed with "Anonymous" as the sender.

Read the full incident report →

Started Nov 14, 2025, 06:05 PM UTC· resolved Nov 17, 2025, 03:10 AM UTC

1. monitoring Nov 17, 2025, 02:29 AM UTC

   Description: We are experiencing an intermittent issue with Google Workspace Chat Support beginning at Friday, 2025-11-14 10:05 PST. Our engineering team continues to investigate the issue. We will provide an update by Sunday, 2025-11-16 20:30 PST with current details. We apologize to all who are affected by the disruption. Symptoms: A subset Customers using Chat to Google Workspace Support might encounter a UI issue where uploaded files appear as a blank message instead of showing the file directly in the chat interface. Despite this UI issue, files are successfully uploaded and accessible by clicking on the blank message. Workaround: None at this time.

2. resolved Nov 17, 2025, 04:11 AM UTC

   Description: The issue with Google Cloud Support has been resolved for all affected users as of Sunday, 2025-11-16 19:10 PST. The issue was due to a recent code change. Our engineers have mitigated the issue by rolling back the system to a previous version. We thank you for your patience while we worked on resolving the issue. Symptoms: A subset of customers using Chat to Google Support might have encountered a UI issue where uploaded files appeared as a blank message instead of showing the file directly in the chat interface. Despite this UI issue, files were successfully uploaded and accessible by clicking on the blank message. Workaround: Not applicable as the issue has been resolved. None at this time.

Read the full incident report →

Started Nov 12, 2025, 05:00 PM UTC· resolved Nov 12, 2025, 09:45 PM UTC

1. monitoring Nov 12, 2025, 06:44 PM UTC

   Description: We are experiencing an issue with Google Drive, Google Sheets, Google Docs beginning at Wednesday, 2025-11-12 09:00 PST Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2025-11-12 11:10 PST with current details. We apologize to all who are affected by the disruption. Symptoms: Some customers are encountering SSL errors such as "This site can't provide a secure connection / ERR_SSL_PROTOCOL_ERROR" when accessing Google Drive, Google Sheets, and Google Docs. Workaround: None at this time.

2. monitoring Nov 12, 2025, 07:05 PM UTC

   Description: We are experiencing an issue with Google Drive, Google Sheets, Google Docs beginning at Wednesday, 2025-11-12 09:00 PST Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2025-11-12 11:45 PST with current details. We apologize to all who are affected by the disruption. Symptoms: Some customers are encountering SSL errors such as "This site can't provide a secure connection / ERR_SSL_PROTOCOL_ERROR" when accessing Google Drive, Google Sheets, and Google Docs. Workaround: None at this time.

3. monitoring Nov 12, 2025, 07:46 PM UTC

   Description: We are experiencing an issue with Google Drive, Google Sheets, Google Docs beginning at Wednesday, 2025-11-12 09:00 PST Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2025-11-12 12:10 PST with current details. We apologize to all who are affected by the disruption. Symptoms: Some customers are encountering SSL errors such as "This site can't provide a secure connection / ERR_SSL_PROTOCOL_ERROR" when accessing Google Drive, Google Sheets, and Google Docs. Workaround: None at this time.

4. investigating Nov 12, 2025, 08:08 PM UTC

   Description: We are experiencing an issue with Google Drive, Google Sheets, Google Docs beginning at Wednesday, 2025-11-12 09:00 PST Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2025-11-12 12:40 PST with current details. We apologize to all who are affected by the disruption. Symptoms: Some customers are encountering SSL errors such as "This site can't provide a secure connection / ERR_SSL_PROTOCOL_ERROR" when accessing Google Drive, Google Sheets, Google Docs, Google Slides, and Google Forms. Workaround: None at this time.

5. investigating Nov 12, 2025, 08:57 PM UTC

   Description: We are experiencing an issue with Google Drive, Google Sheets, Google Docs, Google Slides, Google Forms beginning at Wednesday, 2025-11-12 09:00 PST. Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2025-11-12 13:15 PST with current details. Symptoms: Some customers are encountering SSL errors such as "This site can't provide a secure connection / ERR_SSL_PROTOCOL_ERROR" when accessing Google Drive, Google Sheets, Google Docs, Google Slides, and Google Forms. Workaround: None at this time.

6. investigating Nov 12, 2025, 09:18 PM UTC

   Description: We are experiencing an issue with Google Drive, Google Sheets, Google Docs, Google Forms, Google Slides beginning at Wednesday, 2025-11-12 09:00 PST. Our engineering team is actively investigating the issue. We will provide an update by Wednesday, 2025-11-12 14:15 PST with current details. Symptoms: Some customers are encountering SSL errors such as "This site can't provide a secure connection / ERR_SSL_PROTOCOL_ERROR" when accessing Google Drive, Google Sheets, Google Docs, Google Slides, and Google Forms. Workaround: Impacted customers may try and reboot their routers as a potential workaround. Customers may also try to access via a mobile device..

7. investigating Nov 12, 2025, 10:24 PM UTC

   Description: Our engineering team has identified the root cause. We are seeing a decrease in user impact and are currently working to resolve the issue. We will provide an update by Wednesday, 2025-11-12 15:30 PST with current details. Customer symptoms: Some customers are encountering SSL errors such as "This site can't provide a secure connection / ERR_SSL_PROTOCOL_ERROR" when accessing Google Drive, Google Sheets, Google Docs, Google Slides, and Google Forms. Workaround: Affected customers may try accessing via a mobile device.

8. investigating Nov 12, 2025, 11:32 PM UTC

   Description: Our engineering team has identified the root cause. We are continuing to see a decrease in user impact and are currently working to resolve the issue. We will provide an update by Wednesday, 2025-11-12 16:30 PST with current details. Customer symptoms: Some customers are encountering SSL errors such as "This site can't provide a secure connection / ERR_SSL_PROTOCOL_ERROR" when accessing Google Drive, Google Sheets, Google Docs, Google Slides, and Google Forms. Workaround: Affected customers may try accessing via a mobile device.

9. resolved Nov 13, 2025, 01:23 AM UTC

   Description: The issue with Google Sheets, Google Docs, Google Slides, and Google Forms has been resolved for all affected users as of Wednesday, 2025-11-12 13:45 PST. The root cause was associated with a third party and external to Google infrastructure. We thank you for your patience while we worked on resolving the issue. Customer symptoms: A small number of customers may have encountered SSL errors such as "This site can't provide a secure connection / ERR_SSL_PROTOCOL_ERROR" when accessing Google Sheets, Google Docs, Google Slides, and Google Forms. Workaround: Not applicable.

Read the full incident report →

Started Nov 10, 2025, 02:00 PM UTC· resolved Nov 10, 2025, 04:58 PM UTC

1. monitoring Nov 10, 2025, 03:50 PM UTC

   Description: We are experiencing an issue with Gmail beginning at Monday, 2025-11-10 06:19 PST. Our engineering team continues to investigate the issue. We will provide an update by Monday, 2025-11-10 09:00 PST with current details. Symptoms: Customers may experience issues with images not loading in Gmail. This might appear as broken images in the emails. Workaround: None at this time.

2. monitoring Nov 10, 2025, 04:43 PM UTC

   Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We are seeing significant improvement and the error rates have subsided. We will provide an update by Monday, 2025-11-10 10:00 US/Pacific with current details. Symptoms: Customers may experience issues with images not loading in Gmail. This might appear as broken images in the emails. Workaround: None at this time.

3. resolved Nov 10, 2025, 05:26 PM UTC

   Description: The issue with Gmail has been resolved for all affected users as of Monday, 2025-11-10 08:58 US/Pacific. The issue was due to network latency which eventually translated into errors. Our engineers have mitigated the issue by diverting the traffic to other regions. We thank you for your patience while we worked on resolving the issue. Symptoms: Customers may experience issues with images not loading in Gmail. This might appear as broken images in the emails. Workaround: None at this time.

Read the full incident report →

Started Oct 31, 2025, 09:03 PM UTC· resolved Nov 04, 2025, 01:18 AM UTC

1. investigating Nov 03, 2025, 06:13 PM UTC

   We've received customer reports that Cloud Functions triggers on RTDB events are not triggering / executing. While the databases themselves are working, any function that is configured to trigger on certain read/write events will not execute. We're rolling back the latest build to mitigate while we investigate the root cause.

2. investigating Nov 03, 2025, 08:27 PM UTC

   Mitigation work is underway by our engineering team. Impact in europe-west1 and asia-southeast1 regions have already subsided. Customers in these regions may notice functions triggering for events from as early as 31 October, 2025 (when the incident started). The events are only delayed and are not missing. We will provide more information by Monday, 2025-11-03 16:30 US/Pacific with details, including impact / mitigation status in us-central1.

3. resolved Nov 04, 2025, 02:30 AM UTC

   The 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 not firing, which might have impacted automated workflows for customers. While the databases themselves are working, any function that is configured to trigger on certain read/write events may have been significantly delayed and may only have executed after the issue got mitigated. From preliminary analysis, the issue was triggered by an internal backwards incompatible change in a new version rollout. Our engineers mitigated the issue by deploying a fix to all affected regions. We thank you for your patience while we worked on resolving the issue.

Read the full incident report →

Started Oct 31, 2025, 08:10 AM UTC· resolved Nov 01, 2025, 12:17 AM UTC

1. investigating Oct 31, 2025, 09:12 PM UTC

   [Firebase Data Connect] Customers in europe-west1 may see elevated error rates and latency since around 1:10am Pacific Time on October 31st, 2025. This affects control plane actions such as creating, updating and viewing resources (such as services and schemas). Data plane operations like serving end user requests are not affected. We're still investigating the issue.

2. resolved Nov 01, 2025, 12:52 AM UTC

   The issue has been mitigated on our end. Customers should now be able to change resources (e.g. firebase deploy) normally. For customers who ran into partial / total failures during an earlier deployment, we recommend double-checking the current resource status and deploying again if needed.

3. resolved Nov 01, 2025, 02:21 AM UTC

   (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 rolling back to a previous version. We are continuing to monitor the situation to ensure the issue is fully resolved.

Read the full incident report →