UiPath incident
Degraded performance in Orchestrator and Action Center – US region
UiPath experienced a minor incident on October 1, 2026 affecting Orchestrator and Action Center, lasting 5h 42m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 01, 2026, 01:21 PM 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.
- identified Oct 01, 2026, 02:06 PM UTC
A fix is currently being deployed for the degraded performance affecting Orchestrator and Action Center in the US region. Further updates will follow.
- monitoring Oct 01, 2026, 02:24 PM 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.
- monitoring Oct 01, 2026, 03:34 PM 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.
- monitoring Oct 01, 2026, 04:46 PM 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.
- monitoring Oct 01, 2026, 05:58 PM 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.
- resolved Oct 01, 2026, 07:03 PM 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.
- postmortem Oct 05, 2026, 06:40 AM 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 any future capacity changes against production-level load before rollout. - Improving how we assess customer impact during degradations, so they are escalated to an incident earlier. - Making it faster to roll back capacity and configuration changes when they affect customers.