Multiple Uipath services outage in Europe Region

Final update

## Customer impact Between August 6, 2026 at 7:40 am UTC and August 6, 2026 at 7:50 am UTC, a subset of customers in the Europe region experienced failures when using multiple UiPath services. The impact lasted approximately 10 minutes. Affected services included Action Center, Orchestrator, and other dependent services. Customers may have seen requests fail with server errors during the affected window. ## Root cause An underlying infrastructure update triggered a change in Location Services capacity beyond disruption budget, rendering it in a bad state. Because several UiPath services depend on Location Service, requests through those dependent services returned server errors until the issue was resolved. ## Detection An automated alert fired at 7:45 am UTC on August 6, 2026 and multiple teams were already involved in assessing the situation. ## Response Traffic was automatically diverted to a healthy instance of Location Services and affected services self recovered by 7:50 am UTC on August 6, 2026, ending customer impact. ## Follow up Following this incident, we will improve Location Service resiliency by increasing the headroom available in case of workload shifts and redefine

1. Postmortem · Aug 11, 02:32 UTC
   ## Customer impact Between August 6, 2026 at 7:40 am UTC and August 6, 2026 at 7:50 am UTC, a subset of customers in the Europe region experienced failures when using multiple UiPath services. The impact lasted approximately 10 minutes. Affected services included Action Center, Orchestrator, and other dependent services. Customers may have seen requests fail with server errors during the affected window. ## Root cause An underlying infrastructure update triggered a change in Location Services capacity beyond disruption budget, rendering it in a bad state. Because several UiPath services depend on Location Service, requests through those dependent services returned server errors until the issue was resolved. ## Detection An automated alert fired at 7:45 am UTC on August 6, 2026 and multiple teams were already involved in assessing the situation. ## Response Traffic was automatically diverted to a healthy instance of Location Services and affected services self recovered by 7:50 am UTC on August 6, 2026, ending customer impact. ## Follow up Following this incident, we will improve Location Service resiliency by increasing the headroom available in case of workload shifts and redefine restart strategies.
2. Resolved · Aug 5, 19:30 UTC
   On 06/08/2026 between 07:40 AM UTC - 07:50 AM UTC Multiple Uipath services faced an outage due to a downstream service went into bad state. Team was able to fix the issue.