VMware Workspace ONE Outage History

Started Nov 05, 2025, 05:05 AM UTC· resolved Nov 05, 2025, 05:55 AM UTC

1. resolved Nov 05, 2025, 06:07 AM UTC

   Description: We are experiencing an issue with Google Chat , beginning on Tuesday, 2025-11-04 21:05 US/Pacific. Our engineering team continues to investigate the issue. We will provide more information by Tuesday, 2025-11-04 22:30 US/Pacific with current details. We apologize to all who are affected by the disruption. Symptoms: Impacted customers may experience issues while loading Chat, creating DMs (Direct Messages) and Chat Spaces, and may experience high latency while sending and receiving messages. Workaround: None at this time.

2. investigating Nov 05, 2025, 06:19 AM UTC

   The issue with Google Chat has been resolved for all affected users as of Tuesday, 2025-11-04 21:45 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.

3. resolved Nov 05, 2025, 10:14 AM UTC

   Affected services and features: Google Chat Description: Google Chat users experienced issues when loading Chat, creating and opening DMs (Direct Messages) and Chat Spaces for a duration of 50 minutes. From preliminary analysis the root cause was a temporary contention in the underlying storage system. Customer impact: Affected users faced error when trying to load Google Chat, start new direct messages, or create/open chat spaces.

4. resolved Nov 10, 2025, 09:31 PM UTC

   Incident Report Summary Google Chat users experienced errors when creating new direct messages (DMs) and chat spaces for a total duration of 50 minutes between 21:05 US/Pacific to 21:55 US/Pacific on Tuesday November 4, 2025. At its peak, the issue impacted approximately 0.3% of users. Affected users also observed increased latency in message delivery and issues with initial application loading and opening chat rooms. To our Google Chat users who were impacted during this disruption, we sincerely apologize. This is not the level of quality and reliability we strive to offer you, and we are taking immediate steps to improve the platform’s performance and availability. Root Cause The incident was triggered by database lock contention and hotspotting caused by a large volume of automated background jobs for database maintenance. These resource-intensive tasks created a bottleneck. This resulted in a cascading failure where other unrelated operations that relied on database resources were delayed, causing yet more operations to be delayed in a similar way. This resulted in the errors that users experienced when trying to perform actions like creating new conversations. Remediation and Prevention Google engineers were alerted to the incident through a series of monitoring alerts at 21:06 US/Pacific on Tuesday November 4, 2025 for high error rates on our internal chat services, and immediately started to investigate. The primary mitigation action was to temporarily halt the queue that processes these background cleanup jobs at 21:45 US/Pacific. This action immediately reduced the load and relieved hotspotting on the database, allowing normal operations to resume. A more specific control was later introduced to disable only the problematic background task on November 5, 2025 at 17:34 US/Pacific. We apologize for the disruption this incident caused. We are committed to learning from this event and implementing changes to prevent similar issues in the future. The following preventative measures are planned and will be implemented: - Improve Monitoring: Enhance monitoring to quickly identify the specific background tasks causing database contention. - Improve Resilience: Improve and document procedures for our engineering teams to mitigate similar incidents more quickly, such as by temporarily pausing or slowing down non-essential background tasks. - Fix Underlying Cause: Implement a fix to prevent root cause from occurring again by reducing the excessive resource usage during background cleanup jobs and to prevent them from overloading the system and cascading to other operations in the future. Detailed Description of Impact The incident had a wide-ranging impact on Google Chat users and connected services, with the most significant effects detailed below: At its peak, the incident affected approximately 0.3% of users. The primary and most direct impact was on core chat functionalities, where users experienced errors when creating new direct messages (DMs) and chat spaces. - In addition to the primary issue, users also encountered problems with: - 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.

Read the full incident report →

Started Oct 30, 2025, 03:05 PM UTC· resolved Oct 31, 2025, 11:56 AM UTC

1. resolved 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 29, 2025, 11:58 PM UTC· resolved Oct 30, 2025, 01:49 AM UTC

1. identified Oct 29, 2025, 11:58 PM UTC

   Omnissa Workspace ONE is investigating reports of performance issues with a subset of SaaS environments. Operations teams have identified the issue with modernized services 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 Oct 30, 2025, 12:31 AM UTC

   Omnissa Workspace ONE has initiated failover 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 Oct 30, 2025, 01:04 AM UTC

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

4. monitoring Oct 30, 2025, 01:29 AM UTC

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

5. resolved Oct 30, 2025, 01:49 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 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 Oct 29, 2025, 04:50 PM UTC· resolved Oct 29, 2025, 07:01 PM UTC

1. investigating Oct 29, 2025, 04:50 PM UTC

   Horizon Cloud Service Next-Gen is investigating reports of issues with Virtual Desktop connections and Horizon Universal Console logins. We will share updates as more information becomes available. Service reliability is a top priority for Horizon Cloud Service, and we are committed to continuous improvements in our systems.

2. identified Oct 29, 2025, 06:06 PM UTC

   Horizon Cloud Service Next-Gen identified issues with Microsoft Azure Front Door and implemented remediation steps to ensure end users connecting to Virtual Desktops remain fully operational. However, Horizon Cloud Service Next-Gen still faces issues with Horizon Cloud Universal Console logins. The operations team is collaborating with Microsoft to resolve these problems. Please refer to Azure Status page for more details: https://azure.status.microsoft/en-us/status We will share updates within the next hour or as soon as more information becomes available.

3. monitoring Oct 29, 2025, 06:57 PM 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.

4. resolved Oct 29, 2025, 07:01 PM 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 Oct 25, 2025, 06:05 AM UTC· resolved Oct 25, 2025, 08:00 AM UTC

1. resolved 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. resolved 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. resolved 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 →

Started Oct 20, 2025, 09:15 AM UTC· resolved Oct 20, 2025, 09:59 AM UTC

1. investigating Oct 20, 2025, 09:15 AM UTC

   Omnissa Access and Workspace ONE Hub Services is investigating reports of issues with login in workspaceair.com, workspaceoneaccess.com, vmwareidentity.de, de.wss.workspaceone.com, vmwareidentity.ca, ca.wss.workspaceone.com. 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 Oct 20, 2025, 09:47 AM UTC

   Omnissa Access and Workspace ONE Hub Services has noted improved stability with SaaS environments. Operations teams continue to work with our third party vendor to resolve the issue.

3. monitoring Oct 20, 2025, 09:50 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 Oct 20, 2025, 09:59 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 Oct 09, 2025, 12:25 PM UTC· resolved Oct 09, 2025, 01:20 PM UTC

1. resolved Oct 09, 2025, 03:09 PM UTC

   Some AppSheet users in Europe and America experienced increased latency, resulting in app synchronization failures and editor loading timeouts from Thursday, 2025-10-09 5:25 AM PDT to 2025-10-09 6:20 PDT We will provide an update by Thursday, 2025-10-09 08:30 PDT with current details.

2. resolved Oct 09, 2025, 03:14 PM UTC

   The issue with AppSheet in Europe and America is now resolved. From preliminary investigation the issue was due to resource contention that resulted in our servers not being able to startup during the duration of the issue. The issue was mitigated by rerouting traffic away from the impacted servers.

3. resolved Oct 09, 2025, 05:52 PM UTC

   Affected services and features: AppSheet - App synchronization and Editor loading Regions/zones: * EMEA * AMER (partial impact) Description: On Thursday, 9 October 2025, some AppSheet users in the EMEA and AMER regions experienced elevated latency, resulting in app synchronization failures and editor loading timeouts. The cumulative duration of impact across both windows was 2 hours, 50 minutes. Preliminary investigation identified the issue was due to failures in autoscaling in 2 regions which caused servers to overload and cross-region failover did not occur. The issue was mitigated by rerouting traffic away from the impacted regions. Google will complete a full Incident Report in the following days that will provide a detailed root cause. Customer impact: Customers in the affected regions may have experienced high latency, resulting in errors when syncing data and loading AppSheet applications. The issue was initially observed in the EMEA region and was later observed in both EMEA and parts of the AMER region. The timeline of the two distinct impact windows is as follows: * EMEA only: 9 October 2025, from 00:10 to 02:05 US/Pacific. * EMEA and partial AMER: 9 October 2025, from 05:25 to 06:20 US/Pacific. ---

4. resolved Oct 10, 2025, 01:28 AM UTC

   Prevention ais: * We added an alert to detect missing HPA, ensuring that our engineers can remediate the issue manually if needed. * We updated the migration process for our Kubernetes infrastructure to prevent the continuous removal of HPA after migration. * We are fixing cross region failover routing in Anthos Service Mesh. 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. Detailed Description of Impact The overarching issue was that AppSheet servers became overloaded in two regions due to a failure in the automatic scaling mechanism. This resulted in high latency and elevated error rates, causing cascading issues with app synchronization and the ability to load the editor. The impact occurred across two distinct windows, initially affecting users in the EMEA region, and later expanding to include a partial section of the AMER region.

Read the full incident report →

Started Oct 09, 2025, 10:49 AM UTC· resolved Oct 09, 2025, 12:12 PM UTC

1. investigating Oct 09, 2025, 10:49 AM UTC

   The Horizon Cloud Service team is investigating issues with launching new virtual desktop sessions and reconnecting to existing sessions, caused by a Microsoft Azure Front Door capacity problem. Active sessions remain unaffected. For the latest updates from Microsoft, please visit https://azure.status.microsoft/en-us/status The Horizon Cloud team is closely monitoring the situation and will provide another update within an hour or as necessary. Service reliability is a top priority for Horizon Cloud Service, and we are committed to continuous improvements in our systems.

2. monitoring Oct 09, 2025, 11:56 AM UTC

   Horizon Cloud Service Next-Gen has completed actions to remediate the issues and confirm that the services are available, even though Microsoft Azure Front Door has not yet fully recovered. Operations teams are continuing to monitor the availability of the service to ensure the recovery is complete.

3. resolved Oct 09, 2025, 12:12 PM 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 Oct 09, 2025, 07:10 AM UTC· resolved Oct 09, 2025, 09:05 AM UTC

1. resolved Oct 09, 2025, 08:29 AM UTC

   Description: We are experiencing an issue with AppSheet beginning on Thursday, 2025-10-09 00:10 PDT. Our engineering team continues to investigate the issue. We will provide an update by Thursday, 2025-10-09 02:30 PDT with current details. We apologize to all who are affected by the disruption. Customer symptoms: Customers in the Europe may experience high latency, resulting in errors when syncing data and loading AppSheet applications Workaround: None at this time.

2. investigating Oct 09, 2025, 08:37 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 more information by Thursday, 2025-10-09 03:00 PDT. Customer symptoms: Customers in the Europe may experience high latency, resulting in errors when syncing data and loading AppSheet applications Workaround: None at this time.

3. resolved Oct 09, 2025, 09:50 AM UTC

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

4. resolved Oct 09, 2025, 05:53 PM UTC

   Affected services and features: AppSheet - App synchronization and Editor loading Regions/zones: * EMEA * AMER (partial impact) Description: On Thursday, 9 October 2025, some AppSheet users in the EMEA and AMER regions experienced elevated latency, resulting in app synchronization failures and editor loading timeouts. The cumulative duration of impact across both windows was 2 hours, 50 minutes. Preliminary investigation identified the issue was due to failures in autoscaling in 2 regions which caused servers to overload and cross-region failover did not occur. The issue was mitigated by rerouting traffic away from the impacted regions. Google will complete a full Incident Report in the following days that will provide a detailed root cause. Customer impact: Customers in the affected regions may have experienced high latency, resulting in errors when syncing data and loading AppSheet applications. The issue was initially observed in the EMEA region and was later observed in both EMEA and parts of the AMER region. The timeline of the two distinct impact windows is as follows: * EMEA only: 9 October 2025, from 00:10 to 02:05 US/Pacific. * EMEA and partial AMER: 9 October 2025, from 05:25 to 06:20 US/Pacific. ---

5. resolved Oct 10, 2025, 01:30 AM UTC

   Prevention ais: * We added an alert to detect missing HPA, ensuring that our engineers can remediate the issue manually if needed. * We updated the migration process for our Kubernetes infrastructure to prevent the continuous removal of HPA after migration. * We are fixing cross region failover routing in Anthos Service Mesh. 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. Detailed Description of Impact The overarching issue was that AppSheet servers became overloaded in two regions due to a failure in the automatic scaling mechanism. This resulted in high latency and elevated error rates, causing cascading issues with app synchronization and the ability to load the editor. The impact occurred across two distinct windows, initially affecting users in the EMEA region, and later expanding to include a partial section of the AMER region.

Read the full incident report →