Horizon Cloud Service Next-Gen: Azure Redis latency issues with Virtual desktop provisioning in the Japan Region

Incident Report for Omnissa Workspace ONE

Resolved

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.
Posted Sep 22, 2025 - 17:22 UTC

Monitoring

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.
Posted Sep 22, 2025 - 16:59 UTC

Update

Horizon Cloud Service Next-Gen continues to experience latency issues with Virtual desktop provisioning in the Japan Region.

The Horizon Cloud Service team is continuing to work closely with the Microsoft Azure team. Horizon Cloud Service Team has taken additional measures to minimize the issue's impact to reduce server load. We will provide an update in one hour or as soon 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. Thank You.
Posted Sep 22, 2025 - 16:35 UTC

Identified

Horizon Cloud Service Next-Gen continues to experience latency issues with Virtual desktop provisioning in the Japan Region.

An issue has been identified with Azure Cache for Redis Instance Scaling in the Japan Region. The Horizon Cloud Service team is working closely with the Microsoft Azure team. Microsoft Azure has recovered the cache from the scaling state and is continuing to investigate the Azure Redis latency.

The Horizon Cloud Service team will provide you with an update as soon as Microsoft Azure shares further information.

Service reliability is a top priority at Horizon Cloud Service, and we are making continuous improvements to better our systems. Thank You.
Posted Sep 22, 2025 - 15:14 UTC
This incident affected: Horizon Cloud Service Next-Gen (Horizon Cloud Service Next-Gen - Japan).