Live / UiPath / Incident
UiPath: Degraded performance in Orchestrator and Action Center – US region
UiPath · uipath.comMinor incidentResolved2026-10-01 19:03 UTC
Public — what happened
Summary
UiPath reported slower than normal performance in its Orchestrator service for customers in the US region beginning at 13:21 UTC on October 1, 2026, and later said Action Center in the same region was also affected. The company did not publicly describe a cause, but said at 14:06 UTC that it was rolling out a fix, and by 14:24 UTC it reported the fix was in place. UiPath kept watching performance over the following hours, and the incident was marked resolved at 19:03 the same day.
Timeline
- Started — 2026-10-01 13:21 UTC
- Investigating — 2026-10-01 13:21 UTC
- Identified — 2026-10-01 14:06 UTC
- Monitoring — 2026-10-01 14:24 UTC (4 updates)
- Resolved — 2026-10-01 19:03 UTC · 5h 42m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach UiPath against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for UiPath: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the UiPath report →
More from UiPath
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.