Google Workspace Outage History

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 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 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 30, 2025, 03:05 PM UTC· resolved Oct 31, 2025, 11:56 AM UTC

1. monitoring Oct 30, 2025, 04:19 PM UTC

   Description: The Dialer on Android has a feature to upgrade a call to a Google Meet meeting. Users taking this action are seeing a high rate of failures to upgrade the call. Our engineering team has identified the root cause and is working on mitigation. We will provide more information by Thursday, 2025-10-30 15:00 US/Pacific with current details. We apologize to all who are affected by the disruption. Customer symptoms: Users on Android that upgrade calls to Google Meet meetings are seeing high error rates in upgrading the call Workaround: Users can stay in the call, or set up a meeting using the Google Meet app.

2. monitoring Oct 30, 2025, 10:00 PM UTC

   Description: The Dialer on Android has a feature to upgrade a call to a Google Meet meeting. Users taking this action are seeing a high rate of failures to upgrade the call. Our engineering team is actively working on the mitigation efforts. We will provide more information by Thursday, 2025-10-30 16:00 US/Pacific with current details. Symptoms: Users on Android that upgrade calls to Google Meet meetings are seeing high error rates in upgrading the call. Workaround: Users can stay in the call, or set up a meeting using the Google Meet app.

3. monitoring Oct 30, 2025, 10:50 PM UTC

   Description: The Dialer on Android has a feature to upgrade a call to a Google Meet meeting. Users taking this action are seeing a high rate of failures when upgrading the call. Our engineering team has identified the underlying cause of the issue and a rollback was initiated to mitigate impact. Based on the progress of the rollback, we are observing positive results pertaining to recovery. We expect full mitigation to be completed by Friday, 2025-10-31 12:00 US/Pacific. We will provide more information by Friday, 2025-10-31 12:30 US/Pacific with current details. Symptoms: Users on Android that upgrade calls to Google Meet meetings are observing high error rates when upgrading the call. Workaround: Users can stay in the call, or set up a meeting using the Google Meet app.

4. resolved Oct 31, 2025, 12:41 PM UTC

   Description: The issue with Google Meet has been resolved for all affected customers as of Friday, 2025-10-31 04:56 US/Pacific. From preliminary analysis, the issue was triggered by a recent UI change that made a feature for upgrading calls to Google Meet more prominent for Android users. This led to a surge in usage and revealed an underlying issue with the feature, causing a high failure rate when upgrading calls. Our engineers mitigated the issue by rolling back the UI change. The team will continue to investigate and address the underlying deficiencies in the feature. We thank you for your patience while we worked on resolving the issue. Symptoms: Users on Android that upgrade calls to Google Meet meetings were observing high error rates when upgrading the call. Workaround: Users can stay in the call, or set up a meeting using the Google Meet app.

Read the full incident report →

Started Oct 25, 2025, 06:05 AM UTC· resolved Oct 25, 2025, 08:00 AM UTC

1. investigating Oct 25, 2025, 07:19 AM UTC

   Description: We are experiencing an issue with AppSheet beginning at Friday, 2025-10-24 23:05 PDT. Our engineering team continues to investigate the issue. We will provide an update by Saturday, 2025-10-25 01:30 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: The impacted customers may experience failures while loading apps or writing data using AppSheet. Workaround: None at this time.

2. resolved Oct 25, 2025, 08:24 AM UTC

   Description: The issue with AppSheet has been resolved for all affected users as of Saturday, 2025-10-25 01:00 PDT. The issue was triggered due to a maintenance event on a database resulting in lock contention and our engineering mitigated the impact by manually resolving the contention issue. We thank you for your patience while we worked on resolving the issue. Symptoms: The impacted customers might have experienced failures while loading apps or writing data using AppSheet. Workaround: None

3. resolved Oct 27, 2025, 04:15 AM UTC

   Affected services and features: AppSheet Regions/zones: Global Description: Starting on 24 October 23:05 US/Pacific, AppSheet experienced failures while loading apps or writing data for a duration of 1 hour and 55 minutes. From preliminary analysis, the issue was caused due to a maintenance event on a database resulting in lock contention. Our engineering mitigated the impact by manually resolving the contention issue. Customer impact: The impacted customers might have experienced failures while loading apps or writing data using AppSheet.

Read the full incident report →

Started Oct 24, 2025, 05:45 PM UTC· resolved Oct 25, 2025, 07:05 PM UTC

1. monitoring Oct 25, 2025, 12:15 AM UTC

   Description: We are experiencing an issue with Gmail beginning on Friday, 2025-10-24 10:45 PDT. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2025-10-24 20:30 PDT with current details. Symptoms: Affected customers are experiencing issues accessing Gmail mobile applications. Gmail web access is unaffected. Workaround: Customers can access Gmail from the web browser.

2. monitoring Oct 25, 2025, 02:55 AM UTC

   Description: We are experiencing an issue with Gmail beginning on Friday, 2025-10-24 10:45 PDT. Our engineering team has identified the root cause and implemented mitigation measures. And, currently we are monitoring the status of mitigation. We will provide an update by Monday, 2025-10-27 11:00 PDT with current details. We apologize to all who are affected by the disruption. Symptoms: Affected customers may have experienced issues accessing Gmail mobile applications. Gmail web access is unaffected. Workaround: Customers can access Gmail from the web browser.

3. monitoring Oct 26, 2025, 02:18 AM UTC

   Description: The issue with the GMail is resolved for all the users on Saturday, 2025-10-25 12:05 PDT As per our preliminary analysis, the issue was caused due to a recent code change introduced to OneGoogle for Android and iOS apps. Our engineering team mitigated the issue by rolling back these problematic changes. We apologize to all who are affected by the disruption. We thank you for your patience while we worked on resolving the issue.

4. resolved Oct 27, 2025, 11:44 PM UTC

   Affected services and features: Gmail - Mobile application users on both ios and android Description: Some Workspace for Education users reported experiencing issues accessing Gmail on their mobile devices. Preliminary analysis indicates that the issue was caused by a recent code change in the UX stack of our first-party mobile applications. Our engineering team mitigated the impact by rolling back the problematic changes. Customer impact: Affected users were unable to access Gmail through mobile applications on Android and iOS devices. Gmail web access was unaffected during the issue.

Read the full incident report →

Started Oct 20, 2025, 07:41 PM UTC· resolved Oct 24, 2025, 12:19 AM UTC

1. investigating Oct 20, 2025, 07:50 PM UTC

   Description: We are experiencing an issue with Endpoint management beginning on Wednesday, 2025-10-01 00:00 PDT. We detected the impact progressively increasing on Tuesday, 2025-10-14 10:23 PDT. The Windows native settings app responsible for communicating with Google Identity and Endpoint management is using Internet Explorer 11 which has been deprecated by Microsoft. Google Identity servers are failing to serve requests for IE11 which is impacting device enrollment. Our engineering team continues to investigate the issue. We will provide an update by Monday, 2025-10-20 15:00 PDT with current details. Symptoms: Customers are not able to enroll new Windows devices to Endpoint management using Windows Settings app or deeplink. (https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0) Customers using GCPW (Google Credential Provider for Windows) are not impacted. (https://support.google.com/a/answer/9250996?hl=en&src=supportwidget0&authuser=0) Workaround: None at this time

2. investigating Oct 20, 2025, 09:41 PM UTC

   Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Monday, 2025-10-20 18:30 PDT with current details. Symptoms: Customers are not able to enroll new Windows devices to Endpoint management using Windows Settings app or deeplink. (https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0) Customers using GCPW (Google Credential Provider for Windows) are not impacted. (https://support.google.com/a/answer/9250996?hl=en&src=supportwidget0&authuser=0) Workaround: None at this time.

3. investigating Oct 21, 2025, 01:39 AM UTC

   Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Monday, 2025-10-20 20:00 PDT with current details. Symptoms: Customers are not able to enroll new Windows devices to Endpoint management using Windows Settings app or deeplink. (https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0) Customers using GCPW (Google Credential Provider for Windows) are not impacted. (https://support.google.com/a/answer/9250996?hl=en&src=supportwidget0&authuser=0) Workaround: None at this time.

4. investigating Oct 21, 2025, 02:59 AM UTC

   Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Tuesday, 2025-10-21 01:00 PDT with current details. Symptoms: Customers are not able to enroll new Windows devices to Endpoint management using Windows Settings app or deeplink. (https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0) Customers using GCPW (Google Credential Provider for Windows) are not impacted. (https://support.google.com/a/answer/9250996?hl=en&src=supportwidget0&authuser=0) Workaround: None at this time.

5. investigating Oct 21, 2025, 03:58 AM UTC

   Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Tuesday, 2025-10-21 11:00 PDT with current details. Symptoms: Customers are not able to enroll new Windows devices to Endpoint management using Windows Settings app or deeplink. (https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0) Customers using GCPW (Google Credential Provider for Windows) are not impacted. (https://support.google.com/a/answer/9250996?hl=en&src=supportwidget0&authuser=0) Workaround: None at this time.

6. investigating Oct 21, 2025, 07:17 PM UTC

   Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Thursday, 2025-10-23 17:00 PDT with current details. Symptoms: Customers are not able to enroll new Windows devices to Endpoint management using Windows Settings app or deeplink. (https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0) Customers using GCPW (Google Credential Provider for Windows) are not impacted. (https://support.google.com/a/answer/9250996?hl=en&src=supportwidget0&authuser=0) Workaround: None at this time.

7. investigating Oct 23, 2025, 11:05 PM UTC

   Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide an update by Friday, 2025-10-24 12:00 PDT with current details. Symptoms: Customers are not able to enroll new Windows devices to Endpoint management using Windows Settings app or deeplink. (https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0) Customers using GCPW (Google Credential Provider for Windows) are not impacted. (https://support.google.com/a/answer/9250996?hl=en&src=supportwidget0&authuser=0) Workaround: None at this time.

8. resolved Oct 24, 2025, 01:04 AM UTC

   Description: The issue with Endpoint management for Windows enrollment has been resolved for all affected customers as of Thursday, October 23, 2025, 17:19 PDT. From preliminary analysis, the issue was caused by a browser compatibility problem with the deprecated IE11 used by Microsoft provided Windows Settings app. Our engineers resolved this by deploying a fix to the Google Identity servers to restore support for these requests. We thank you for your patience while we worked on resolving the issue. Symptoms: Customers were not able to enroll new Windows devices to Endpoint management using Windows Settings app or deeplink. (https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0) Customers using GCPW (Google Credential Provider for Windows) were not impacted. (https://support.google.com/a/answer/9250996?hl=en&src=supportwidget0&authuser=0) Workaround: None.

9. resolved Oct 24, 2025, 06:50 AM UTC

   Affected services and features: Endpoint Management Description: Starting on 01 October 2025, Endpoint Management customers experienced the inability to enroll new Windows devices using Windows Settings app or deeplink. We detected the impact when it progressively increased on Tuesday, 2025-10-14 10:23 PDT. From our analysis, the issue originated from a browser compatibility concern. Specifically, the Microsoft-provided Windows Settings application utilized the deprecated Internet Explorer 11, rendering it incompatible with recent modifications to the identity servers. Our engineers resolved this by deploying a fix to the Google Identity servers to restore support for these requests. Customer impact: The Windows native settings application, which facilitates communication with Google Identity and Endpoint management, relies on Internet Explorer 11, a browser no longer supported by Microsoft. Device enrollment was affected due to Google Identity servers unable to fulfill requests from Internet Explorer 11. Customers encountered issues enrolling new Windows devices in Google Endpoint management through the Windows Settings app or deeplink1. However, users leveraging Google Credential Provider for Windows (GCPW) were unaffected by this problem2. Reference(s): 1 Enroll a device in Windows device management (https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0%29*%29[https://support.google.com/a/answer/9539504?hl=en&sjid=13524530415918932254-NC&authuser=0) 2 Install Google Credential Provider for Windows (https://support.google.com/a/answer/9250996?hl=en&src=supportwidget0&authuser=0)

10. resolved Oct 27, 2025, 11:10 AM UTC

    Incident Report Summary Beginning on 1 October 2025, Google Endpoint Management customers experienced issues enrolling new Windows devices using the native Windows Settings application or direct enrollment deeplinks. This incident started on 1 October 2025 at 00:00 US/Pacific and lasted for 22 days, 17 hours and 19 minutes, with resolution on 23 October 2025 at 17:19 US/Pacific. We sincerely apologize for any impact this disruption had on your device management workflows. We are taking measures to prevent a recurrence. Root Cause The root cause of this incident was a deprecated[1] browser compatibility issue. The device enrollment process initiated from the Windows Settings application relies on an embedded browser component. This component's behavior is based on the now deprecated Internet Explorer 11. Recent updates to Google's Identity servers, intended to enhance security and modernize the platform, inadvertently removed compatibility with the outdated protocols and behaviors exhibited by the Internet Explorer 11 engine. As a result, authentication requests from the Windows Settings enrollment flow could no longer be processed successfully by the updated Identity servers, causing the enrollment to fail. [1] Deprecated browser compatibility issue: https://learn.microsoft.com/en-us/lifecycle/products/internet-explorer-11 Remediation and Prevention The issue was detected on Tuesday, 14 October 2025, at 10:23 US/Pacific, as the impact progressively increased, prompting a detailed investigation. Google engineers traced the failures back to the incompatibility between the Google Identity servers and the enrollment process embedded within the Windows Settings application, which uses a deprecated Internet Explorer 11 component. To remediate the issue, Google engineers developed and deployed a targeted fix to the Google Identity servers. This update restored the servers' ability to handle authentication requests originating from the enrollment flow dependent on the Internet Explorer 11 technology. The rollout of this fix was completed on 23 October 2025 at 17:19 US/Pacific, fully restoring the ability to enroll new Windows devices via the Windows Settings application and deeplinks. Google is committed to preventing similar incidents in the future and is completing the following actions: We are enhancing our testing procedures for Windows device enrollment flows. We are exploring improvements in monitoring to detect issues on lower-traffic enrollment pathways more rapidly. Detailed Description of Impact Google Endpoint Management - From 1 October 2025, 00:00 US/Pacific to 23 October 2025, 17:19 US/Pacific, customers were unable to enroll new Windows devices into Google Endpoint Management when using the built-in Windows Settings application (as described in “Enroll a device” in Windows device management) or an enrollment deeplink. The enrollment process would fail during the authentication phase due to the incompatibility. Customers using the Google Credential Provider for Windows (GCPW) for device setup and login (as described in “Install Google Credential Provider for Windows”) were not affected by this incident and could continue to enroll and manage devices without issue. The impact was limited to the specific enrollment method relying on the Windows Settings interface.

Read the full incident report →