UiPath logo

UiPath Status Page

Automation & Integration · monitored by Alert24

uipath.com ↗
All Systems Operational

Is UiPath down right now?

No — UiPath is up. All systems operational as of Oct 12, 4:54 AM UTC.

Current Status

All Systems Operational

View UiPath status page ↗

Components

Automation Cloud
Operational
Automation Cloud
Operational
Automation Cloud
Operational
Automation Cloud
Operational
Automation Cloud
Operational
Automation Cloud
Operational
Automation Cloud
Operational
Automation Cloud
Operational
Automation Cloud
Operational
Automation Cloud
Operational
Automation Cloud
Operational
Automation Cloud
Operational
Action Center
Operational
Orchestrator
Operational
Orchestrator
Operational
Orchestrator
Operational
Orchestrator
Operational
Orchestrator
Operational
Orchestrator
Operational
Orchestrator
Operational

Recent Incidents

US - Maestro - HITL task creation failures within Maestros with HITL task SLA timers configured

major

Oct 7, 2026 · resolved Oct 8

The fix for the issue impacting HITL task creation for Maestro with HITL task SLA timers configured in US has been fully rolled out. HITL task creation has returned to normal.

US - Orchestrator - Intermittent errors and degraded performance in Orchestrator

minor

Oct 7, 2026 · resolved Oct 7

We have the issue in the East US region and error rates and latency returned to normal levels.

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

major

Oct 6, 2026 · resolved Oct 6

## Customer impact On , between approximately 15:45 UTC and 18:45 UTC, customers hosted in the Europe, Australia and Japan regions were unable to see recent robot logs in Orchestrator. Logs written during the impact window did not appear in the Jobs and Logs views or through the Robot Logs API, and logs older than approximately 03:00 UTC that day were available only intermittently. The impact window differed per region: - Australia: approximately 15:45 UTC to 18:35 UTC - Europe: approximately 16:35 UTC to 18:00 UTC - Japan: approximately 16:45 UTC to 18:30 UTC Job execution, queues, triggers and all other Orchestrator functionality were not affected. No robot logs were lost. Logs produced during the impact window continued to be collected and became visible again once the issue was mitigated. ## Root cause We were performing a scheduled upgrade of the Elasticsearch service that stores Orchestrator robot logs. The upgrade uses a blue/green approach: a new cluster is created alongside the existing one, the data is restored into it from a backup, the pipeline that ingests new logs is started on it, and only then is traffic switched over. In the affected regions, the traffic switch was approved by the engineer running the upgrade before the data restore and the ingestion catch-up had completed, which is a deviation from our upgrade procedure. This was a human error. As a result, Orchestrator was reading robot logs from a cluster that did not yet contain recent data, while new logs continued to be collected but were not yet indexed on the cluster serving requests. The error was not caught because our deployment tooling relies on the operator to verify data completeness and does not enforce the order between the data restore and the traffic switch. ## Detection Our synthetic monitoring, which continuously runs test jobs and verifies that their logs are returned, detected missing logs in the affected regions and raised alerts. Our engineering team correlated the alerts with the in-progress upgrade, declared an incident and published a status page notification. ## Response Our engineering team reverted the traffic to the previous Elasticsearch clusters in all three regions, which immediately restored access to all robot logs, including those produced during the impact window. We confirmed recovery through synthetic monitoring in every affected region and continued monitoring before marking the incident resolved at approximately 18:45 UTC. The upgrade of the new clusters continues in the background. Traffic will be moved to them only after the data restore is complete and ingestion is confirmed to be up to date. ## Follow up To prevent this from happening again, we are: - Changing the deployment pipeline so that the traffic switch cannot run until the data restore and log ingestion on the new cluster are verified as complete. - Adding an automated rollback step to the pipeline, so traffic can be returned to the previous cluster within minutes if a problem is detected after a switch.

UAE - Automation Cloud Services - Degraded performance

none

Oct 6, 2026 · resolved Oct 6

The incident has been resolved.

Delays starting jobs on Cloud Robots in the US region

minor

Oct 2, 2026 · resolved Oct 2

This issue has been resolved. Between 15:05 and 16:39 UTC, jobs on Cloud Robots in the US region were slow to start or stayed in the Pending state. Jobs have been starting normally since 16:39 UTC, and jobs that were delayed during this time have now been processed. We apologize for the disruption.

Get alerted when UiPath goes down

Alert24 monitors UiPath and 3,700+ other cloud and SaaS providers. When an outage is detected, it updates your status page automatically and pages your on-call team. No manual updates at 2 AM.

Start free — no credit card

UiPath status — frequently asked questions

Is UiPath down right now?

No — UiPath is up. All systems operational as of Oct 12, 4:54 AM UTC.

What is UiPath's current status?

UiPath: All Systems Operational. Alert24 checks UiPath's status page continuously and can notify you the moment it changes.

How do I get alerted when UiPath goes down?

Alert24 monitors UiPath and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.

More Automation & Integration status pages