Omnissa Access Outage History

Omnissa Workspace ONE UEM experienced availability issues affecting SaaS environments in a partial region of the United States for 45 minutes. The incident impacted customer access to their Workspace ONE environments, with affected customers identified through the Omnissa Cloud Services portal. The service was restored through partial recovery followed by complete resolution, with operations teams continuing to monitor system performance.

Omnissa Access and Workspace ONE Hub Services experienced intermittent app launch issues affecting the Germany region (vmwareidentity.de/de.wss.workspaceone.com) for 1.4 hours. The service team implemented remediation actions and monitored the recovery to ensure complete restoration. The incident was fully resolved with normal service operations restored.

Omnissa Access and Workspace ONE Hub Services experienced intermittent login and launch errors affecting tenants with URLs in the *.workspaceoneaccess.com format in the United States partial region. The incident lasted 1.6 hours and has been resolved. Users reported difficulties accessing and launching services during this period.

Omnissa Workspace ONE UEM experienced availability issues affecting the Shared SaaS system CN2744 in the Singapore region for 35 minutes. The performance problems impacted customers using the shared SaaS infrastructure in that partial region. The issue was resolved and operations teams continued monitoring while investigating the root cause.

Omnissa Access experienced a major incident affecting Horizon Cloud Service First-Gen Console Access login functionality in the US and Japan regions for 1.8 hours. Users were unable to access the Horizon Cloud Admin Console during this period. The operations team identified and resolved the underlying issue, with service fully restored after monitoring confirmed complete recovery.

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.