VMware Workspace ONE Outage History

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

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.

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.

Omni observed reports of errors while getting response from chat interface specific to knowledge search. The issues has been resolved. Service reliability is a top priority at Omnissa and we are making continuous improvements to better our systems.

Microsoft has confirmed that 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.

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.

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.

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.

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.

Description: We are experiencing an issue with Workspace users beginning on Thursday, 2026-04-09 19:08 PDT. Our engineering team continues to investigate the issue. We will provide an update by Friday, 2026-04-10 04:00 PDT with current details. We apologize to all who are affected by the disruption. Customer symptoms: Google Workspace users using Google IdP are unable to sign into their accounts using security keys and hardware based passkeys. Workaround: Below steps should be performed by Admin as the workaround: - Admin should revoke the key. - Admin to create the verification code to sign-in. - The user should sign-in using Backup verification code and then re-enrolls the security key.

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

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.

Description: Beginning on Wednesday, 2026-04-08 14:05 PDT, we are experiencing an issue with AppSheet that caused users to be erroneously redirected to the asia-southeast region. Our engineers have identified the cause was due to a recent change and have reverted. Our internal telemetry shows the signs of recovery and are currently monitoring the recovery status. We expect full service recovery within an hour. We will provide an update by Wednesday, 2026-04-08 16:30 PDT with current details Customer symptoms: Users are automatically redirected to asia-southeast.appsheet.com, which may cause "Forbidden" or 403 errors when attempting to access their apps. Workaround: None at this time.

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

Description: We are aware of an issue with Gmail users experiencing delays in receiving and sending emails beginning at Wednesday, 2026-04-08 06:30 PDT. 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 Wednesday, 2026-04-08 12:00 PDT with current details. Symptoms: Customers may experience delays in receiving and sending emails. Workaround: None at this time.

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

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

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

Description: The issue began on Friday, 2026-03-20 15:30 US/Pacific. Our engineering team is aware of the situation and is actively implementing mitigations. We do not have any ETA at the moment. We will provide the next update by Friday, 2026-03-20 21:00 US/Pacific. Customer symptoms: Impacted users may encounter connection timeouts or error pages (such as 502 Bad Gateway) when attempting to reach keep.google.com via a web browser. The Google Keep mobile applications are currently unaffected and remain operational. Workaround: Users are able to use Google Keep via the Android or iOS mobile app.

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

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

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.

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

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.

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.