Degraded performance in Orchestrator and Action Center – US region

Final update

## Customer impact Between approximately 11:00 UTC and 13:40 UTC on October 1, 2026, customers in the US region observed slower Orchestrator response times and intermittent timeouts. Robots took longer to start jobs, process queue items and read assets, and some of these requests failed. Other UiPath services that rely on Orchestrator were also affected while Orchestrator was degraded, and may have seen slower responses or errors. ## Root cause An Orchestrator fix deployment included a change to how computing capacity is reserved and scaled for our services. The change was meant to use our infrastructure more efficiently, but it lowered the processing capacity available to Orchestrator. During busy periods our automatic scaling did not add capacity as expected, so the service could not keep up with demand. ## Detection Our internal monitoring detected the slowdown after the update. Our first plan was to release a corrected update through our standard release process, which takes several hours. When customer reports began coming in, we opened an incident and moved to a faster fix. ## Response Our engineering team applied the previous capacity settings directly to the affected servic

1. Postmortem · Oct 5, 06:40 UTC
   ## Customer impact Between approximately 11:00 UTC and 13:40 UTC on October 1, 2026, customers in the US region observed slower Orchestrator response times and intermittent timeouts. Robots took longer to start jobs, process queue items and read assets, and some of these requests failed. Other UiPath services that rely on Orchestrator were also affected while Orchestrator was degraded, and may have seen slower responses or errors. ## Root cause An Orchestrator fix deployment included a change to how computing capacity is reserved and scaled for our services. The change was meant to use our infrastructure more efficiently, but it lowered the processing capacity available to Orchestrator. During busy periods our automatic scaling did not add capacity as expected, so the service could not keep up with demand. ## Detection Our internal monitoring detected the slowdown after the update. Our first plan was to release a corrected update through our standard release process, which takes several hours. When customer reports began coming in, we opened an incident and moved to a faster fix. ## Response Our engineering team applied the previous capacity settings directly to the affected services, without waiting for the corrected update. Response times returned to normal at approximately 13:40 UTC, and we continued monitoring to confirm the service was stable. ## Follow up To prevent this from happening again, we are: - Permanently restoring the previous capacity settings, and reviewing
2. Resolved · Oct 1, 19:03 UTC
   The degraded performance affecting Orchestrator and Action Center in the US region has been resolved. System performance has remained stable following the implemented fix, and we will continue standard monitoring.
3. Monitoring · Oct 1, 17:58 UTC
   A fix has been implemented for the degraded performance affecting Orchestrator and Action Center in the US region. We are continuing to monitor system performance and stability to confirm the issue is fully resolved. Further updates will be provided as more information becomes available.
4. Monitoring · Oct 1, 16:46 UTC
   A fix has been implemented for the degraded performance affecting Orchestrator and Action Center in the US region. We are continuing to monitor system performance and stability to confirm the issue is fully resolved. Further updates will be provided as more information becomes available.
5. Monitoring · Oct 1, 15:34 UTC
   A fix has been implemented for the degraded performance affecting Orchestrator and Action Center in the US region. We are continuing to monitor system performance and stability to confirm the issue is fully resolved. Further updates will be provided as more information becomes available.
6. Monitoring · Oct 1, 14:24 UTC
   A fix has been implemented for the degraded performance affecting Orchestrator and Action Center in the US region. Our team is actively monitoring the results to confirm the issue is fully resolved.
7. Identified · Oct 1, 14:06 UTC
   A fix is currently being deployed for the degraded performance affecting Orchestrator and Action Center in the US region. Further updates will follow.
8. Investigating · Oct 1, 13:21 UTC
   Our team is actively working on a fix for the degraded performance affecting Orchestrator in the US region. We will share updates as progress is made.