Customer impact

Between October 1, 2026 at 2:23 pm UTC and 4:04 pm UTC, a subset of customers experienced 404 Not Found errors for some UiPath Automation Cloud requests in the Australia region. The incident lasted 1 hour and 41 minutes.

Affected requests included delete operations and some Robot connection checks. Services affected included Orchestrator, Document Understanding, AI Center, and Data Service. Robot jobs that called Orchestrator may have failed, and customers may need to rerun any Robot jobs that failed during this window. All other operations were not affected.

Root cause

A routing configuration change was applied to the Australia region with an incomplete set of supported operations due to a timeout in the release pipeline. Delete operations were missing from the configuration, so those requests were rejected at the routing layer with 404 Not Found before reaching the underlying services.

Detection

Automated end-to-end monitoring detected the issue by alerting on failures for Document Understanding service checks. Our engineering team then used internal monitoring data to confirm the broader pattern of failures across affected services.

Response

During investigation, monitoring data showed that requests routed through the Australia region were returning 404 Not Found errors, while requests routed through other regions were unaffected. Analysis identified that the start time of 404 Not Found response increase was correlated with the time when the routing configuration came in effect.

The team reverted the routing configuration to the prior working version. After the revert, monitoring showed error counts dropping within approximately three minutes, and the service was fully restored by October 1, 2026 at 4:04 pm UTC.

Follow up

1. Improve routing layer alerts on 4xx baseline changes
2. Detect partially applied routing configurations before having them take effect