About This Site

Welcome to our status page. If you are looking for help, please check our documentation guides or contact us on our community forum. All products listed below have a target availability of 99.9%.

Current UiPath Status

All Systems Operational

Component Status Overview

Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
— Not available
Loading component status...

Uptime over the past 90 days. View historical uptime.

Multiple Regions - Multiple Services - Agent runtime errors

Incident Report for UiPath

Postmortem

Customer Impact

On April 23, 2026, from 3:00 pm UTC to 11:42 pm UTC, some customers with IP restriction policies enabled experienced agent jobs remaining pending or failing to start. More than 150 jobs were affected across multiple regions.

Customers without IP restrictions and agents using the serverless execution path were not affected.

Root Cause

A messaging infrastructure update introduced a regression that prevented required IP restriction headers from being forwarded between internal services during agent job initiation.

Without these headers, downstream authorization checks rejected requests from organizations using IP restrictions. Serverless agents were unaffected because they use a separate execution path.

Detection and Response

The incident was detected through customer reports and monitoring of pending jobs. It was declared at 3:24 pm UTC, and the public status page was updated at 3:26 pm UTC.

The investigation established that:

  • Only organizations with IP restrictions enabled were affected.
  • Serverless agents were unaffected.
  • Temporarily disabling IP restrictions allowed an affected job to complete, confirming the connection to IP restriction handling.

At 5:26 pm UTC, the team identified the header propagation regression. A fix was validated and progressively deployed across production regions. Customers began confirming recovery by 11:00 pm UTC, and all regions were operational by 11:42 pm UTC.

Preventive Actions

We are taking the following actions:

  1. Add deployment checks that verify critical security headers are propagated across internal service calls.
  2. Expand integration tests to cover allowed and denied requests for organizations using IP restrictions.
  3. Introduce phased rollouts and environment-verification checks for messaging infrastructure changes.
  4. Improve monitoring and escalation for pending agent jobs, including failures associated with security configurations.

We apologize for the disruption and are strengthening our testing, deployment, and monitoring processes to reduce the risk of recurrence.

Posted Jul 29, 2026 - 22:47 UTC

Resolved

The issue has been resolved
Posted Apr 23, 2026 - 23:36 UTC

Monitoring

The mitigation has been rolled out, and we are validating that it has resolved the issue
Posted Apr 23, 2026 - 22:49 UTC

Update

We have identified a mitigation and validated it in a lower environment. We are rolling out the mitigation to all affected regions.
Posted Apr 23, 2026 - 21:54 UTC

Update

We are still working on a mitigation.

As a temporary workaround: The issue appears to be related to the IP Restriction security setting, as internal testing has shown that disabling it mitigates the issue. We understand that disabling this feature may not be possible for all customers, but we wish to provide it as an option.
In order to apply this mitigation: navigate to Admin -> Security Settings -> IP Restriction
Posted Apr 23, 2026 - 21:29 UTC

Update

We are continuing to develop and validate a mitigation for this issue
Posted Apr 23, 2026 - 21:06 UTC

Update

We have a mitigation and are validating it prior to deploying it to production
Posted Apr 23, 2026 - 20:14 UTC

Update

We are still working on a mitigation for this issue
Posted Apr 23, 2026 - 19:16 UTC

Update

We are validating the reversion of the improper configuration in a lower environment, and will begin deploying it to production regions shortly
Posted Apr 23, 2026 - 18:18 UTC

Identified

We have identified a defect in a recent deployment, which is causing the issue. We are preparing to roll back the change, which will return Agents to full functionality for all customers.
Posted Apr 23, 2026 - 17:21 UTC

Update

Further investigation has revealed that this issue is affecting all regions, so customers may experience Agents failing to start across all UiPath Automation Cloud regions.

We are continuing to investigate the root cause of the issue and will be working to mitigate it promptly.
Posted Apr 23, 2026 - 16:44 UTC

Update

We are continuing to investigate the cause of the issues, we will provide an update as soon as we begin working on a mitigation
Posted Apr 23, 2026 - 16:17 UTC

Investigating

We are investigating reports of an outage impacting Agents in US and Europe Regions.
Impact: Users may be unable to start Agents.
Next update: Our teams are working to understand the cause and scope and will share updates as available.
Posted Apr 23, 2026 - 15:24 UTC
This incident affected: UAE (Agents), European Union (Agents), United States (Agents), Japan (Agents), India (Agents), Singapore (Agents), Australia (Agents), Canada (Agents), UK (Agents), Switzerland (Agents), and Delayed US (Agents).