VMware Workspace ONE Outage History

Started Mar 13, 2026, 09:28 PM UTC· resolved May 23, 2026, 12:05 AM UTC

1. scheduled Mar 13, 2026, 09:29 PM UTC

   After March 30, 2026, legacy Omnissa Access and Workspace ONE Hub Services tenant URLs will be disabled, impacting authentication, Hub catalog access, and other dependent services. End users will be blocked from accessing legacy URLs listed below. *.vidmpreview.com *.vmwareidentity.asia *.vmwareidentity.com.au *.vmwareidentity.eu *.vmwareidentity.de *.vmwareidentity.co.uk *.vmwareidentity.ca *.vmwareidentity.com Refer to these KBs for background and action needed: https://kb.omnissa.com/s/article/6001323 https://kb.omnissa.com/s/article/6001304 https://kb.omnissa.com/s/article/6001062 Take action to avoid downtime. Complete any remaining steps outlined in the Access Migration Dashboard following instructions on https://kb.omnissa.com/s/article/6001062 before the March 30, 2026 deadline.

2. scheduled Mar 30, 2026, 10:59 PM UTC

   Maintenance will begin as scheduled in 60 minutes.

3. in progress Mar 30, 2026, 11:59 PM UTC

   Scheduled maintenance is currently in progress. We will provide updates as necessary.

Read the full incident report →

Started Mar 13, 2026, 12:00 PM UTC· resolved Mar 13, 2026, 02:30 PM UTC

1. resolved Mar 13, 2026, 01:58 PM UTC

   Description: We are experiencing intermittent errors with Google Docs, Apps Script, Google Slides, Google Drive, Google Calendar beginning on Friday, 2026-03-13 05:00 PDT. Our engineering teams are actively working to mitigate the impact. We will provide an update by Friday, 2026-03-13 08:00 PDT with current details. We apologize to all who are affected by the disruption. Customer symptoms: A subset of customers may experience elevated error rates when accessing the impacted products in the US region. Workaround: Impacted users may re-attempt the unsuccessful action.

2. monitoring Mar 13, 2026, 02:34 PM UTC

   Description: We are experiencing intermittent errors with Google Docs, Apps Script, Google Slides, Google Drive, Google Calendar beginning on Friday, 2026-03-13 05:00 PDT. We have confirmed that the issue affecting Google Drive is now mitigated. Users should no longer experience unavailability when accessing or interacting with Drive files. Our engineering teams continue to actively work on mitigating the remaining impacted products. We will provide an update by Friday, 2026-03-13 09:00 PDT with current details. We apologize to all who are affected by the disruption. Customer symptoms: A subset of customers may experience elevated error rates when accessing the impacted products in the US region. Workaround: Impacted users may re-attempt the unsuccessful action.

3. resolved Mar 13, 2026, 02:56 PM UTC

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

Read the full incident report →

Started Mar 02, 2026, 12:19 PM UTC· resolved Mar 02, 2026, 12:30 PM UTC

1. identified Mar 02, 2026, 12:19 PM UTC

   Omnissa Access and Workspace ONE Hub Services is investigating increased error rates for requests made to the service in vmwareidentity.de / de.wss.workspaceone.com. There may be limited or no service impact at this time. Service reliability is a top priority at Omnissa and we are making continuous improvements to better our systems.

2. monitoring Mar 02, 2026, 12:28 PM UTC

   Omnissa Access and Workspace ONE Hub Services has noted a decrease in error rates. Operations teams continue to monitor the environment.

3. resolved Mar 02, 2026, 12:30 PM UTC

   The issue is now resolved. We apologize for the inconvenience and thank you for your patience and continued support. Service reliability is a top priority at Omnissa and we are making continuous improvements to better our systems.

Read the full incident report →

Started Feb 27, 2026, 08:42 PM UTC· resolved Feb 27, 2026, 08:58 PM UTC

1. investigating Feb 27, 2026, 08:42 PM UTC

   Omnissa Workspace ONE is investigating reports of issues with AutoDiscovery services. We will provide more information shortly. Omnissa Cloud Services portal has been updated for customers affected by this event. System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

2. investigating Feb 27, 2026, 08:52 PM UTC

   Omnissa Workspace ONE has noted improved stability with SaaS environments. Operations teams continue to actively work towards complete recovery.

3. resolved Feb 27, 2026, 08:58 PM UTC

   The issue is now resolved. We apologize for the inconvenience and thank you for your patience and continued support. Operations teams will continue to monitor system performance levels and investigate the root cause of the issue. System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

Read the full incident report →

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

1. resolved 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 18, 2026, 04:30 PM UTC· resolved Feb 22, 2026, 08:08 PM UTC

1. resolved Feb 19, 2026, 10:57 AM UTC

   Description: We are investigating an issue where chat histories are not visible on Gemini Web (gemini.google.com) and the Gemini mobile apps on Wednesday, 2026-02-18 08:30 PST. Our engineering team has identified a background process that was causing the missing user conversation metadata and has successfully stopped the process to prevent further impact. Mitigation efforts are underway, and we do not have an ETA for completion at this time. We will provide an update by Thursday, 2026-02-19 09:00 PST with current details. We apologize to all who are affected by the disruption. Symptoms: * Users may find that their sidebar is empty or that previously saved conversations are missing. * Users may receive an empty response when attempting to list or search for existing conversations. * New conversations can still be created and utilized normally. Workaround: * Impacted web users on gemini.google.com can navigate to Menu (top left) > Settings & Help > Activity. * Alternatively, users can navigate to myactivity.google.com/product/gemini to view their conversation history. * Mobile users could navigate to their profile (top right) and select Gemini Apps Activity.

2. investigating Feb 19, 2026, 04:49 PM UTC

   Description: We are investigating an issue where chat histories are not visible on Gemini Web (gemini.google.com) and the Gemini mobile apps on Wednesday, 2026-02-18 08:30 PST. Our engineering team has identified a background process that was causing the missing user conversation metadata and has successfully stopped the process to prevent further impact. Mitigation efforts are underway, and our engineers are working to restore the missing chat histories. We do not have an ETA for completion at this time. We will provide an update by Thursday, 2026-02-19 15:00 PST with current details. We apologize to all who are affected by the disruption. Symptoms: * Users may find that their sidebar is empty or that previously saved conversations are missing. * Users may receive an empty response when attempting to list or search for existing conversations. * New conversations can still be created and utilized normally. Workaround: * Impacted web users on gemini.google.com can navigate to Menu (top left) > Settings & Help > Activity. * Alternatively, users can navigate to myactivity.google.com/product/gemini to view their conversation history. * Mobile users could navigate to their profile (top right) and select Gemini Apps Activity.

3. investigating Feb 20, 2026, 03:02 AM UTC

   Description: We are investigating an issue where chat histories are not visible on Gemini Web (gemini.google.com) and the Gemini mobile apps on Wednesday, 2026-02-18 08:30 PST. Our engineering team has identified a background process that was causing the missing user conversation metadata and has successfully stopped the process to prevent further impact. Mitigation efforts are underway, and our engineers are working to restore the missing chat histories. We do not have an ETA for completion at this time. We will provide an update by Thursday, 2026-02-19 18:00 PST with current details. Symptoms: ** Users may find that their sidebar is empty or that previously saved conversations are missing. ** Users may receive an empty response when attempting to list or search for existing conversations. ** New conversations can still be created and utilized normally. Workaround: * Impacted web users on gemini.google.com can navigate to Menu (top left) > Settings & Help > Activity. * Alternatively, users can navigate to myactivity.google.com/product/gemini to view their conversation history. * Mobile users could navigate to their profile (top right) and select Gemini Apps Activity.

4. investigating Feb 20, 2026, 03:03 AM UTC

   Description: We are investigating an issue where chat histories are not visible on Gemini Web (gemini.google.com) and the Gemini mobile apps on Wednesday, 2026-02-18 08:30 PST. Our engineering team has identified a background process that was causing the missing user conversation metadata and has successfully stopped the process to prevent further impact. Mitigation efforts are underway, and our engineers are working to restore the missing chat histories. We do not have an ETA for completion at this time. We will provide an update by Friday, 2026-02-20 20:00 PST with current details. Symptoms: ** Users may find that their sidebar is empty or that previously saved conversations are missing. ** Users may receive an empty response when attempting to list or search for existing conversations. ** New conversations can still be created and utilized normally. Workaround: * Impacted web users on gemini.google.com can navigate to Menu (top left) > Settings & Help > Activity. * Alternatively, users can navigate to myactivity.google.com/product/gemini to view their conversation history. * Mobile users could navigate to their profile (top right) and select Gemini Apps Activity.

5. resolved Feb 23, 2026, 01:20 AM UTC

   Description: The issue with Gemini has been resolved for all affected users as of Sunday, 2026-02-22 12:08 PST. Based on our initial analysis, the incident was caused by an internal job that caused some valid conversation metadata to be deleted, which resulted in the conversations from the side navigation to be hidden. Users could still access the hidden conversations requests and responses from the activity section. Our engineering team mitigated the impact by restoring the data from the appropriate backups. We thank you for your patience while we worked on resolving the issue. Symptoms: * Users may have found that their sidebar was empty or that previously saved conversations were missing. * Users may have received an empty response when attempting to list or search for existing conversations. * New conversations were still created and utilized normally. Workaround: * Impacted web users on gemini.google.com can navigate to Menu (top left) > Settings & Help > Activity. * Alternatively, users can navigate to myactivity.google.com/product/gemini to view their conversation history. * Mobile users could navigate to their profile (top right) and select Gemini Apps Activity.

Read the full incident report →

Started Feb 03, 2026, 02:30 AM UTC· resolved Feb 03, 2026, 04:18 AM UTC

1. investigating Feb 03, 2026, 02:30 AM UTC

   Omnissa Access and Workspace ONE Hub Services is investigating increased error rates for requests made to the service in workspaceoneaccess.com. There may be limited or no service impact at this time. Service reliability is a top priority at Omnissa and we are making continuous improvements to better our systems.

2. monitoring Feb 03, 2026, 03:09 AM UTC

   Omnissa Access and Workspace ONE Hub Services has noted a decrease in error rates. Operations teams continue to monitor the environment.

3. resolved Feb 03, 2026, 04:18 AM UTC

   The issue is now resolved. We apologize for the inconvenience and thank you for your patience and continued support. Service reliability is a top priority at Omnissa and we are making continuous improvements to better our systems.

Read the full incident report →

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

1. resolved 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 23, 2026, 05:45 PM UTC· resolved Jan 23, 2026, 07:14 PM UTC

1. investigating Jan 23, 2026, 05:45 PM UTC

   The Horizon Cloud Service team is investigating degraded virtual machine (VM) provisioning issue. Updates will be provided as more information becomes available. End users launching desktops will not be affected if sufficient spare capacity exists and there is no impact to existing connections.

2. investigating Jan 23, 2026, 06:21 PM UTC

   The Horizon Cloud Service team continues to investigate degraded virtual machine (VM) provisioning. End users launching desktops should not be impacted if sufficient spare capacity is available, and existing connections remain unaffected. We will provide an update in one hour or sooner as more information becomes available.

3. monitoring Jan 23, 2026, 06:55 PM UTC

   Horizon Cloud Service has completed actions to remediate the issues and confirm that VM provisioning operations execute as expected. Operations teams are continuing to monitor the availability of the service to ensure the recovery is complete.

4. resolved Jan 23, 2026, 07:14 PM UTC

   The issue is resolved. If you are experiencing any residual effects from this issue, please open a Service Request for assistance. We apologize for the inconvenience and thank you for your patience and continued support. Service reliability is a top priority at Horizon Cloud Service, and we are making continuous improvements to better our systems.

Read the full incident report →

Started Jan 22, 2026, 11:37 PM UTC· resolved Jan 23, 2026, 02:33 AM UTC

1. investigating Jan 22, 2026, 11:37 PM UTC

   Omnissa Workspace ONE is investigating reports of internal application downloads with SaaS environments. Operations teams have identified an issue with CDN infrastructure and are actively working with the vendor to resolve it. Omnissa Cloud Services portal has been updated for customers affected by this event. Please check the Omnissa Cloud Services portal to confirm if your environment is affected by this event. System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

2. investigating Jan 23, 2026, 12:18 AM UTC

   Omnissa Workspace ONE continues to experience issues. Operations teams are actively working to resolve it.

3. investigating Jan 23, 2026, 01:09 AM UTC

   Omnissa Workspace ONE continues to experience issues. Operations teams are actively working to resolve it.

4. investigating Jan 23, 2026, 02:21 AM UTC

   Omnissa Workspace ONE has noted improved stability with SaaS environments. Operations teams continue to actively work towards complete recovery.

5. resolved Jan 23, 2026, 02:33 AM UTC

   The issue is now resolved. We apologize for the inconvenience and thank you for your patience and continued support. Operations teams will continue to monitor system performance levels and investigate the root cause of the issue. System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

Read the full incident report →

Started Jan 19, 2026, 06:10 PM UTC· resolved Jan 20, 2026, 07:49 PM UTC

1. resolved Jan 20, 2026, 03:32 PM UTC

   Symptoms: - Admin Console: Administrators searching for or viewing users may see empty fields for primary email addresses and account creation dates. The issue may also affect display of user information where a user's email address would normally be present (such as Reporting or Activity events). - Directory API: Applications accessing the Directory API, such as Google Cloud Directory Sync (GCDS), may receive responses with missing email and account creation metadata. Workaround: None at the time.

2. investigating Jan 20, 2026, 03:59 PM UTC

   Symptoms: - Admin Console: Administrators searching for or viewing users may see empty fields for primary email addresses and account creation dates. The issue may also affect display of user information where a user's email address would normally be present (such as Reporting or Activity events). - Directory API: Applications accessing the Directory API, such as Google Cloud Directory Sync (GCDS), may receive responses with missing email and account creation metadata. Workaround: None at the time.

3. investigating Jan 20, 2026, 04:59 PM UTC

   Description: We believe the issue with Admin Console is mitigated for the vast majority of the users. Engineering continues to work on full resolution and is expected to complete by Tuesday, 2026-01-20 09:15 PST. We will provide an update by Tuesday, 2026-01-20 09:30 PST with current details. Diagnosis / customer symptoms: Admin Console: Administrators searching for or viewing users may see empty fields for primary email addresses and account creation dates. The issue may also affect display of user information where a user's email address would normally be present (such as Reporting or Activity events). Directory API: Applications accessing the Directory API, such as Google Cloud Directory Sync (GCDS), may receive responses with missing email and account creation metadata. Some customers may see Single Sign-On (SSO) failures due to this issue. Workaround: None at this time.

4. investigating Jan 20, 2026, 05:09 PM UTC

   Description: The issue with Admin Console has been resolved for all affected users as of Tuesday, 2026-01-20 11:49 PST. From preliminary analysis, the issue was due to a recent change to a job writing to the metadata store. Our engineers mitigated the issue by restoring the metadata from an unaffected source of truth. We thank you for your patience while we worked on resolving the issue. Diagnosis / customer symptoms: Admin Console: Administrators searching for or viewing users may have seen empty fields for primary email addresses and account creation dates. The issue may have also affected display of user information where a user's email address would normally be present (such as Reporting or Activity events). Directory API: Applications accessing the Directory API, such as Google Cloud Directory Sync (GCDS), may have received responses with missing email and account creation metadata. Some customers saw Single Sign-On (SSO) failures due to this issue. Workaround: The issue is resolved, no workaround necessary.

5. resolved Jan 21, 2026, 12:39 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. A final Incident Report with preventative actions will be posted once our investigation is complete. If you have experienced an impact outside of what is listed below, please reach out to Google Workspace Support using the help article https://support.google.com/a/answer/1047213. Date/time of the issue (all time us/pacific): Incident Start: 19 January 2026, 10:10 Incident End: 20 January 2026 11:49 Duration: 1 day, 1 hour, 39 minutes Preliminary root cause: This incident was identified to be caused by corrupted user account metadata in a secondary data store, triggered by a faulty code change. In Google's infrastructure, user account information is maintained in a primary backend system of record. This data is periodically synchronized to secondary data stores, which applications such as the Admin Console use to retrieve and display user profile information. The trigger for this incident was a faulty code change deployed to a synchronization job. This change caused the job to malfunction and write invalid or empty information into the secondary data store for a subset of user accounts. Although the correct user data remained intact in the primary backend system of record, the corrupted copy in the secondary data store was served to dependent services. Google will complete a full Incident report in the following days that will provide a full root cause. Remediation: Google engineers were alerted to the issue via support case on 20 January at 03:32. Engineering quickly identified a faulty code change that was deployed to a synchronization job as the source of the issue. A rollback of the application service was performed in parallel with synchronizing the data for affected users from the primary backend account system. A script was run to accomplish this, correcting the data for affected accounts. The script was deployed in batches, which led to the mitigation of the affected accounts and restored services on 20 January at 11:49. Description of impact: Between 19 January, 10:10 and 20 January, 11:49, Admin Console: Administrators searching for or viewing users may have seen empty fields for primary email addresses and an incorrect account creation date of "January 1, 1970". The issue may have also affected the display of user information where a user's email address would normally be present (such as in Reporting or Activity events). Directory API: Applications accessing the Directory API, such as Google Cloud Directory Sync (GCDS), may have received responses with missing fields including email and account creation metadata. Single Sign-On (SSO): Some customers experienced SSO failures for external services that rely on Google Workspace as an identity provider.

6. resolved Jan 23, 2026, 02:07 AM UTC

   Incident Report Summary Starting 19 January at 10:10, Google Workspace customers may have experienced missing account metadata, including primary email address and account creation time in the Admin Console. Additionally, some customers experienced authentication failures for external services via Single Sign-On (SSO). The issue lasted for 1 day, 1 hour and 39 minutes. To our Workspace customers whose services were impacted during this disruption, we sincerely apologize. This is not the level of quality and reliability we strive to offer you, and we are taking immediate steps to improve the platform’s performance and availability. Root Cause This incident was caused by corrupted user account metadata in a secondary data store, triggered by a faulty code change. In Google's infrastructure, user account information is maintained in a primary backend system of record. This data is periodically synchronized to secondary data stores, which applications such as the Admin Console use to retrieve and display user profile information. The trigger for this incident was a faulty code change deployed to a synchronization job. This change caused the job to malfunction and write invalid or empty information into the secondary data store for a subset of user accounts. Although the correct user data remained intact in the primary backend system of record, the corrupted copy in the secondary data store was served to dependent services. Remediation and Prevention Google engineers were first alerted to the potential issue via a support case submitted on 20 January at 03:32. Upon receiving the alert, engineering teams initiated an investigation and quickly identified that a faulty code change, which had been recently deployed to a synchronization job, was the primary source of the data discrepancies. This specific job was responsible for updating secondary data stores from the primary backend account system. To resolve the incident, a multi-pronged remediation strategy was executed. A rollback of the application service was performed in parallel with a manual synchronization process to restore data for all affected users. This restoration relied on the primary backend account system, which remained accurate throughout the event. A specialized script was developed and run to correct the corrupted metadata for the impacted accounts. To ensure system stability during the recovery phase, the script was deployed in controlled batches. This systematic approach successfully mitigated the issue for all affected accounts and fully restored services by 20 January at 11:49. Google is committed to preventing a recurrence of this issue and is implementing the following action items: - Binary Release Controls: Automated release gates were established for the affected synchronization service to ensure stability and prevent a recurrence. - Enhanced Release Validation: We are implementing stricter validation checks within the synchronization job to detect and block invalid metadata writes before they reach secondary stores. - Monitoring and Alerting: We are expanding automated monitoring to detect data integrity discrepancies between our primary system of record and secondary data stores, allowing for faster detection. Detailed Description of Impact The service disruption occurred between 19 January at 10:10 and 20 January at 11:49, lasting a total of 1 day, 1 hour and 39 minutes. During this period, Google Workspace customers experienced significant issues with missing account metadata, specifically impacting the visibility and accuracy of user profiles. - Admin Console Impact: Administrators searching for or viewing user details found that primary email addresses appeared as empty fields. Additionally, the account creation date for affected users was incorrectly displayed as "January 1, 1970". This data corruption also cascaded into other areas where user email addresses are typically populated, such as Reporting logs and Activity events, hindering administrative oversight and auditing. - Directory API and Tooling: The issue extended beyond the web interface to programmatic access. Applications utilizing the Directory API, including critical tools like Google Cloud Directory Sync (GCDS), received incomplete responses. These API responses were missing vital fields, including primary emails and account creation metadata, potentially disrupting automated synchronization and provisioning workflows. - Single Sign-On (SSO) Failures: A subset of customers experienced authentication failures for external services. These failures occurred when the external services relied on Google Workspace as the identity provider via SSO, as the required user identifiers were unavailable during the disruption.

Read the full incident report →

Started Jan 16, 2026, 06:07 PM UTC· resolved Jan 17, 2026, 12:43 AM UTC

1. investigating Jan 16, 2026, 06:07 PM UTC

   The Horizon Cloud Service team is investigating degraded virtual machine (VM) provisioning. Updates will be provided as more information becomes available. Service reliability is a top priority at Horizon Cloud Service, and we are making continuous improvements to better our systems

2. investigating Jan 16, 2026, 07:07 PM UTC

   The Horizon Cloud Service team continues to investigate degraded virtual machine (VM) provisioning issues due to network delays. End users launching desktops will not be affected if sufficient spare capacity exists and there is no impact to existing connections. We will provide an update in two hours or as soon as we have more information.

3. investigating Jan 16, 2026, 09:20 PM UTC

   The Horizon Cloud Service team continues to investigate degraded virtual machine (VM) provisioning issues. We identified increased latency in database updates and are investigating its impact on VM provisioning operations. End users launching desktops will not be affected if sufficient spare capacity exists and there is no impact to existing connections. We will provide an update in two hours or as soon as we have more information.

4. monitoring Jan 16, 2026, 11:59 PM UTC

   Horizon Cloud Service has completed actions to remediate the issues and confirm that VM provisioning operations execute as expected. Operations teams are continuing to monitor the availability of the service to ensure the recovery is complete.

5. resolved Jan 17, 2026, 12:43 AM UTC

   The issue is resolved. If you are experiencing any residual effects from this issue, please open a Service Request for assistance. We apologize for the inconvenience and thank you for your patience and continued support. Service reliability is a top priority at Horizon Cloud Service, and we are making continuous improvements to better our systems.

Read the full incident report →

Started Jan 08, 2026, 05:55 PM UTC· resolved Jan 08, 2026, 08:00 PM UTC

1. identified Jan 08, 2026, 05:55 PM UTC

   Omnissa Workspace ONE detected issues which may have impacted availability for SaaS environments. Customers leveraging on-premise hosted Omnissa Workspace ONE integration modules such as Omnissa Workspace ONE Cloud Connector (ACC), Enterprise System Connect (VESC), Omnissa Tunnel, Mobile Access Gateway (MAG), Secure Email Gateway (SEG) may experience issues as a result of the issues. We will provide more information shortly. Omnissa Cloud Services portal has been updated for customers affected by this event. System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

2. identified Jan 08, 2026, 06:32 PM UTC

   Omnissa Workspace ONE has initiated a restore protocol to recover service. System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

3. identified Jan 08, 2026, 07:13 PM UTC

   Omnissa Workspace ONE continues to experience issues. Operations teams are actively working to resolve it.

4. identified Jan 08, 2026, 07:46 PM UTC

   Omnissa Workspace ONE has noted improved stability with SaaS environments. Operations teams continue to actively work towards complete recovery.

5. resolved Jan 08, 2026, 08:00 PM UTC

   The issue is now resolved. We apologize for the inconvenience and thank you for your patience and continued support. Customers leveraging on-premise hosted Omnissa Workspace ONE integration modules such as Omnissa Workspace ONE Cloud Connector (ACC), Omnissa Tunnel, Mobile Access Gateway (MAG), Secure Email Gateway (SEG) may experience residual issues as a result of the outage. Omnissa Workspace ONE recommends restarting the impacted integration modules as a troubleshooting measure. If issues persist, please engage Omnissa Workspace ONE Support for further assistance. System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

Read the full incident report →

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

1. resolved 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 08, 2026, 10:17 AM UTC· resolved Jan 08, 2026, 11:23 AM UTC

1. investigating Jan 08, 2026, 10:17 AM UTC

   Omnissa Workspace ONE is investigating reports of performance issues with SaaS environments. Operations teams have identified the issue with database infrastructure and are actively working to resolve it. Omnissa Cloud Services portal has been updated for customers affected by this event. Please check the Omnissa Cloud Services portal to confirm if your environment is affected by this event. System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

2. identified Jan 08, 2026, 10:46 AM UTC

   Omnissa Workspace ONE continues to experience issues. Operations teams have identified the issue database infrastructure which persists after following standard remediation protocols. Operations teams are actively working to resolve the issue.

3. resolved Jan 08, 2026, 11:23 AM UTC

   The issue is now resolved. We apologize for the inconvenience and thank you for your patience and continued support. Operations teams will continue to monitor system performance levels and investigate the root cause of the issue. System reliability is a top priority at Omnissa Workspace ONE, and we are making continuous improvements to better our systems.

Read the full incident report →

Started Dec 17, 2025, 01:52 AM UTC· resolved Dec 17, 2025, 02:03 AM UTC

1. investigating Dec 17, 2025, 01:52 AM UTC

   The Horizon Cloud Service team is investigating reports of issues with Custom Client Access Subdomain URLs (.omnissahorizon.com). Users accessing this URL may experience Desktop/Application launch failures. Existing user connections remain unaffected. As a workaround, we recommend using the https://cloud.omnissahorizon.com URL to launch Desktops. We are looking into this further and will provide more information soon. Service reliability is a top priority at Horizon Cloud Service, and we are continuously improving our systems.

2. monitoring Dec 17, 2025, 01:56 AM UTC

   Horizon Cloud Service Next-Gen has completed actions to remediate the issues and confirm that the services are available. Operations teams are continuing to monitor the availability of the service to ensure the recovery is complete.

3. resolved Dec 17, 2025, 02:03 AM UTC

   The issue is resolved. We apologize for the inconvenience and thank you for your patience and continued support. Service reliability is a top priority at Horizon Cloud Service, and we are making continuous improvements to better our systems.

Read the full incident report →

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

1. resolved 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. resolved 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. resolved 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 19, 2025, 08:03 PM UTC· resolved Nov 19, 2025, 11:26 PM UTC

1. monitoring Nov 19, 2025, 08:03 PM UTC

   Omnissa Access is investigating reports of issues with login. We will provide more information shortly. Service reliability is a top priority at Omnissa and we are making continuous improvements to better our systems.

2. monitoring Nov 19, 2025, 08:05 PM UTC

   Omnissa Access has completed actions to remediate the issues and confirm that the services are available. Operations teams are continuing to monitor the availability of the service to ensure the recovery is complete.

3. monitoring Nov 19, 2025, 08:42 PM UTC

   The issue is now resolved. We apologize for the inconvenience and thank you for your patience and continued support. Service reliability is a top priority at Omnissa and we are making continuous improvements to better our systems.

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

   The issue is now resolved. We apologize for the inconvenience and thank you for your patience and continued support. Service reliability is a top priority at Omnissa and we are making continuous improvements to better our systems.

Read the full incident report →

Started Nov 16, 2025, 07:39 AM UTC· resolved Nov 16, 2025, 07:44 AM UTC

1. investigating Nov 16, 2025, 08:37 AM UTC

   Omnissa Access and Workspace ONE Hub Services is investigating reports of issues with login. We will provide more information shortly. Service reliability is a top priority at Omnissa and we are making continuous improvements to better our systems.

2. investigating Nov 16, 2025, 08:39 AM UTC

   We are continuing to investigate this issue.

3. monitoring Nov 16, 2025, 08:40 AM UTC

   Omnissa Access and Workspace ONE Hub Services has completed actions to remediate the issues and confirm that the services are available. Operations teams are continuing to monitor the availability of the service to ensure the recovery is complete.

4. resolved Nov 16, 2025, 08:42 AM UTC

   The issue is now resolved. We apologize for the inconvenience and thank you for your patience and continued support. Service reliability is a top priority at Omnissa and we are making continuous improvements to better our systems.

Read the full incident report →

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

1. resolved 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. resolved 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. resolved 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 Nov 05, 2025, 05:56 AM UTC· resolved Nov 05, 2025, 07:45 AM UTC

1. investigating Nov 05, 2025, 05:56 AM UTC

   Omnissa Connect is investigating reports of issues in launch for Access and Hub services in Australia region. We will provide more information shortly. Service reliability is a top priority at Omnissa and we are making continuous improvements to better our systems.

2. identified Nov 05, 2025, 06:02 AM UTC

   Omnissa Connect continues to experience issues. Operations teams have identified the issue and are working to resolve it.

3. resolved Nov 05, 2025, 07:45 AM UTC

   The issue is now resolved. We apologize for the inconvenience and thank you for your patience and continued support. Service reliability is a top priority at Omnissa and we are making continuous improvements to better our systems.

Read the full incident report →