Japan – Multiple Services – Degraded Performance

Update timeline

1. resolved Jun 03, 2026, 12:34 PM UTC

   On 3rd June 2026, between 00:16 UTC and 02:17 UTC, customers in the Japan region may have experienced intermittent slowness while accessing the UiPath Platform. During a brief window near the end of this period — approximately 02:15 UTC to 02:17 UTC — the impact was more severe: a large majority of requests to the region failed for roughly two minutes before service automatically recovered. The issue has since been mitigated, and all services have returned to normal operation. A detailed Root Cause Analysis will be shared separately.

2. postmortem Jun 12, 2026, 12:37 PM UTC

   ## Customer impact Between June 3, 2026 at 12:30 am UTC and 2:22 am UTC, a subset of customers in the Japan region experienced increased latency and intermittent errors across the **UiPath Commercial Cloud**, most visibly in **Orchestrator**, **Studio Web**, and **Access Policy \(IP Restrictions\)** functionality. The impact lasted approximately 1 hour and 52 minutes. Service performance returned to normal once the underlying infrastructure issue was resolved. ## Root cause The incident was caused by an infrastructure issue within Microsoft Azure API Management in the Japan region. An underlying platform component experienced a failure that gradually degraded request processing and caused intermittent connection issues. This resulted in increased latency and errors for affected services. Service recovered automatically once the underlying platform component returned to normal operation. ## Detection The issue was detected through automated monitoring for elevated API gateway error rates on June 3, 2026 at 2:48 am UTC — approximately 32 minutes after the start of the observed customer-impact window. The alert created the incident response channel, and responders acknowledged the alert immediately. ## Response ‌ After the issue was detected, engineers investigated the increase in latency and errors affecting the Japan region. The investigation confirmed that the disruption originated from an underlying infrastructure issue within Azure API Management. Service performance had already returned to normal by the time the investigation began, and monitoring confirmed stable operation throughout the remainder of the incident review. ## Follow up 1. Microsoft has confirmed this was a rare infrastructure event caused by a failed VM restart on the APIM platform, and that no customer-side action was required to prevent or mitigate it. 2. We are evaluating additional regional synthetic availability checks for Japan to improve detection speed for similar short-lived APIM disruptions. 3. We are improving alert enrichment for regional APIM error spikes to include automatic blast-radius identification and faster customer-impact assessment.