UiPath experienced a notice incident on April 22, 2026, lasting —. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved Apr 22, 2026, 01:20 PM UTC
From approximately 09:52 UTC to 10:21 UTC, customers in the Japan region may have been unable to access the App Service. This was due to an issue in our deployment pipeline that temporarily affected cluster availability, which has been mitigated. A detailed Root Cause Analysis will be shared separately.
- postmortem May 26, 2026, 07:35 AM UTC
## Customer Impact The App Service in the Japan region was inaccessible for approximately 29 minutes \(09:52 AM – 10:21 AM GMT\). Users relying on the Japan cluster experienced temporary service disruptions during this period. ## Root Cause The incident was caused by a flaw in the deployment pipeline script. While using a new centralized deployment template, Japan \(configured in Ring 2\) was temporarily targeted to unblock progression to a later deployment ring. Although the deployment was not intended to proceed beyond the approval stage, the script triggered unintended behavior during initiation, causing the Japan cluster to become inaccessible. ## Detection The issue was identified when the Japan cluster became unreachable during the deployment process. The pipeline did not halt safely at the expected approval stage, revealing an environment-specific or intermittent issue that had not been observed in lower environments. ## Response The team mitigated the issue by manually rolling back the pods to the previously stable version, restoring service. As follow-up actions, the deployment script will be fixed to prevent similar issues, and the Japan region will be moved from Ring 2 to the final deployment ring to avoid unintended impact during future rollouts. ## Follow Up Script fix \(completed\): The deployment pipeline script has been corrected. The fix was validated through dry runs in lower environments and reviewed by the platform engineering team. Ring reassignment**:** The Japan cluster will be moved from Ring 2 to the final deployment ring, ensuring future rollouts reach Japan only after validation across all earlier rings.