No impact incident

UiPath: UAE - Automation Cloud Services - Degraded performance

Affected: Automation Cloud, Automation Hub, Apps, Automation Ops, Autopilot (Plugins), Agents, Action Center, Agentic Orchestration

Current status of UiPath: Partial outage — live UiPath status

Timeline

1. Oct 6, 2026, 12:38 UTC
   identified
   We are observing degraded performance for services in UAE
2. Oct 6, 2026, 12:43 UTC
   investigating
   We are currently investigating this issue.
3. Oct 6, 2026, 14:01 UTC
   identified
   We have identified the issue as a network routing problem with a third-party service provider, affecting connectivity for our services hosted in the UAE. We are working with our upstream provider on resolution and will update progress here.
4. Oct 6, 2026, 14:22 UTC
   identified
   We are continuing to work on a fix for this issue.
5. Oct 6, 2026, 14:51 UTC
   monitoring
   We are monitoring connectivity and will update this page once stability is confirmed.
6. Oct 6, 2026, 15:07 UTC
   monitoring
   We are continuing to monitor for any further issues.
7. Oct 6, 2026, 15:09 UTC
   monitoring
   We are continuing to monitor for any further issues.
8. Oct 6, 2026, 17:09 UTC
   resolved
   The incident has been resolved.
9. Oct 21, 2026, 05:36 UTC
   postmortem
   ## Customer impact Between 12:38 PM UTC and 2:51 PM UTC, a subset of customers in the UAE region experienced failures when accessing UiPath cloud services. The incident lasted approximately 2 hours and 13 minutes. Affected services included access to **cloud.uipath.com**, **account.uipath.com** Services hosted in UAE. Customers may have encountered timeouts, failed authentication, reset connections, or server errors. ## Root cause The root cause was a regional network routing failure at a third-party infrastructure provider. A subset of outbound network paths from the UAN region to specific external networks — including the content delivery network serving **cloud.uipath.com** and **account.uipath.com** — stopped delivering traffic. New outbound connection attempts from affected services did not receive responses, causing requests to time out. Our engineering team ruled out UiPath service configuration, application-level policy, and outbound connection capacity as causes. The infrastructure provider acknowledged a known issue affecting multiple customers on the same network path. ## Detection The issue was detected through automated monitoring. By approximately 12:40 pm UTC — roughly two minutes after the failure began — investigation confirmed that new connections from affected UAN region services to key UiPath endpoints were failing. ## Response By 1:20 pm UTC, our engineering team confirmed that the failure was limited to specific outbound network paths, while other destinations remained reachable. Validation ruled out UiPath-side routing changes, content delivery configuration changes, application-level policy, and outbound connection capacity issues. A high-severity support case was opened with the third-party infrastructure provider. At 1:50 pm UTC, the provider acknowledged a known issue affecting multiple customers. Our team continued monitoring recovery from the affected network paths and verifying service health as traffic returned. At 2:51 pm UTC, recovery checks confirmed that UiPath traffic through the affected content delivery paths had returned to normal levels. Automated health checks and service metrics confirmed recovery, and Services in UAN were operational. ## Follow up 1. We are pursuing the infrastructure provider's confirmed corrective action and root cause analysis for the regional routing failure. 2. We are reviewing outbound service dependencies in the affected region to strengthen resilience against similar third-party network disruptions.

Updates as published by UiPath (original).