Live / UiPath / Incident
UiPath: US- Orchestrator - Intermittent errors and degraded performance in Orchestrator
UiPath · uipath.comMinor incidentResolved2026-10-07 19:06 UTC
Public — what happened
Summary
UiPath reported a minor incident on October 7, 2026, beginning at 17:37 UTC, in which some organizations using Orchestrator in its East US Automation Cloud region experienced intermittent slowness and errors. According to the company, parts of the Orchestrator interface such as the Jobs page could fail to load, and robot tasks like queue transactions and session starts sometimes timed out. By 18:13 UTC, UiPath said it had added capacity to the database systems involved in that region and that error rates and response times were back to normal. The company marked the incident resolved at 19:06.
Affected
Orchestrator
Timeline
- Started — 2026-10-07 17:37 UTC
- Investigating — 2026-10-07 17:37 UTC
- Monitoring — 2026-10-07 18:13 UTC
- Resolved — 2026-10-07 19:06 UTC · 1h 29m 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 42, 2026, our weekly internet health report.