Live  /  UiPath  /  Incident

UiPath: [Europe, Japan, Australia] - [Orchestrator] - [Delays for ingestion of robot logs and search or display of the logs]

UiPath · uipath.comMajor incidentResolved2026-10-06 18:44 UTC
Public — what happened

Summary

UiPath reported a major incident on October 6, 2026 affecting its Orchestrator product, with the title listing Europe, Japan and Australia while the updates themselves mentioned only Europe. Starting at 17:50 UTC, the company said customers could see slowdowns in robot logs being taken in, as well as delays when searching for or viewing those logs, though it stated no log data would be lost. UiPath said at 18:02 UTC that it had found the cause, but it did not say what that cause was. The incident was marked resolved at 18:44.

Affected

Orchestrator, Orchestrator, Orchestrator

As listed on UiPath’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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.

The full archive is on the UiPath status & history page.

Related: UiPath status & history. SquidGrid is not affiliated with UiPath.