Omnissa Access Outage History

Omnissa Workspace ONE UEM experienced performance issues affecting SaaS environments in a partial region of the United States due to vendor infrastructure problems. Production SaaS environments were restored first, followed by UAT environments which remained affected for a longer period. The incident was fully resolved after 3.4 hours with operations teams continuing to monitor system performance.

Omnissa Workspace ONE UEM experienced availability issues in Germany due to database infrastructure problems, affecting SaaS environments in the partial region. The operations team identified and actively worked to resolve the database-related issue. The incident was resolved after 14 minutes with system performance being monitored for stability.

Omnissa Access and Workspace ONE Hub Services experienced login issues affecting users in the United States (partial region) and Canada (full region) for 2.6 hours. The outage prevented users from accessing these services, with Canada experiencing more widespread impact than the US. Operations teams identified and resolved the underlying issue, restoring full service availability.

The Horizon Cloud Service experienced an 11-hour outage in the Azure East US region where customers could not launch virtual desktops or applications due to an underlying Microsoft Azure infrastructure issue. The problem was caused by an Azure outage affecting multiple availability zones, with recovery completed progressively across zones 01, 02, and 03. Microsoft resolved the underlying Azure issue and Horizon Cloud Service was fully restored, with customers advised to open service requests if experiencing any residual effects.

Omnissa Workspace ONE experienced a major outage affecting UAT SaaS environments in the Germany datacenter for 49 minutes. The incident impacted customers using on-premise integration modules including Cloud Connector, Tunnel, Mobile Access Gateway, and Secure Email Gateway. The issue was resolved, though customers were advised to restart affected integration modules to address any residual connectivity problems.

Omnissa Workspace ONE UEM experienced performance issues affecting SaaS environments in Germany, specifically impacting data loading on device lists, application lists, event logs, and deployment tracking pages. The incident lasted 3.3 hours with a gradual recovery process where missing data was progressively restored. The issue has been fully resolved with operations teams continuing to monitor system performance and investigate the root cause.

Omnissa Access experienced a major incident affecting VM provisioning in the Japan region, causing delays and failures when customers attempted to create, delete, or update Desktop Pools. The issue lasted 2.6 hours before the Horizon Cloud team completed remediation actions and restored normal service functionality. The incident was fully resolved with continued monitoring to ensure complete recovery.

Omnissa Workspace ONE experienced a 51.9-hour outage caused by DNS issues with *.uemauth.vmwservices.com domains, which caused integrations using UEM API with OAuth tokens to fail, including automations, custom scripts, and third-party integrations like ServiceNow. The issue was resolved by correcting the top-level DNS for vmwservices.com, with customers able to use an alternative *.uemauth.workspaceone.com domain as a workaround during the DNS propagation period.

Omnissa Access and Workspace ONE Hub Services experienced login issues affecting access.gc.workspaceone-gov.com in the GovCloud partial region for 39 minutes. The operations team completed remediation actions and confirmed service availability. The incident was fully resolved after monitoring confirmed complete recovery.

Omnissa Workspace ONE UEM experienced a major availability outage in Germany lasting 1.1 hours, caused by network infrastructure issues that persisted after standard remediation protocols. The incident affected SaaS environments and customers using on-premise integration modules including Cloud Connector, Tunnel, Mobile Access Gateway, and Secure Email Gateway. The issue was resolved, though customers were advised to restart affected integration modules to address any residual problems.