UiPath Status

Postmortem: ## Customer Impact

On April 17, 2026, the UiPath Insights portal and Provisioning service experienced an outage affecting customers in the UAE region following a scheduled deployment. During this period, users were unable to access any of the data in Insights dashboards. The impact began at approximately 12:00 UTC on April 17 and was fully resolved by 23:38 UTC on April 21, 2026, resulting in a total service disruption of approximately 4 days and 11 hours.

Root Cause

The outage was triggered by an issue in our deployment process for the UAE region. During a recent service deployment, a required step in our deployment workflow failed silently, which prevented the new version of the Insights portal from being fully activated in UAE. Over time, the older version that remained in service began referencing files that had since been removed as part of routine maintenance, causing the portal to become inaccessible to customers_._

Detection

The issue was discovered through UiPath Insights internal alerts and automated availability monitoring in the UAE region. These signals indicated portal unavailability, prompting the engineering team to investigate the deployment pipeline and identify the root cause_._

Response

Upon detecting the outage, the engineering team investigated the deployment pipeline and identified that a re-deployment was needed to restore service. However, the team encountered two additional issues that had to be resolved first: an outdated infrastructure component introduced a pipeline failure, and a misconfigured integration setting — left over from the initial UAE region setup — had been silently blocking deployments.

On April 21, 2026 at approximately 20:30 UTC, both issues were resolved, allowing a successful re-deployment that fully restored the Insights portal in UAE by 23:38 UTC on April 21.

Follow-Up

To prevent similar incidents in the future, we are taking the following steps:

• Establish a mandatory verification checklist for new region deployments to ensure all configuration settings are correctly applied before going live.
• Ensure any incomplete deployment steps are treated as active incidents and fully resolved before proceeding with subsequent releases.
• Strengthen monitoring and alerting coverage for recently launched regions to ensure issues are detected and escalated promptly, regardless of region maturity.

Resolved: The outage has been resolved and Insights dashboard in UAE is fully operational. Impact: No ongoing user impact.

Identified: The cause of the outage impacting Dashboard for Insights in UAE has been identified and are working on a fix. Impact: Users may be unable to access the Insights dashboard Next update: Our focus is on restoring service as quickly as possible.

Identified: We have identified the cause of the outage impacting Dashboard for Insights in UAE and are working on a fix. Impact: Users may be unable to access the Insights dashboard Next update: Our focus is on restoring service as quickly as possible.

Postmortem: ## Customer Impact

‌

Between approximately 6:00 pm UTC and 7:14 pm UTC on April 20, 2026, customers using the Autopilot for Everyone service in the United States Delayed region were unable to sign in or send chat messages. All attempts to access the service returned errors, rendering the service effectively unavailable. Customers with cached credentials were also unable to send messages, and no workaround was available during the outage.

Scope: The impact was limited to customers accessing Autopilot for Everyone via Portal > AI Trust Layer and those using the Autopilot for Everyone via Assistant in the United States Delayed region.

Root Cause

‌

A service update deployed to the Autopilot for Everyone service on April 20, 2026 triggered an unexpected modification to the traffic routing configuration in the United States Delayed infrastructure. The routing rules that direct incoming customer requests were altered to an unsupported configuration. This mismatch meant that the routing layer could not match incoming requests to any valid destination, resulting in HTTP 404 errors for all service traffic.

Recovery was achieved by manually patching the routing configuration to include both the original correct address and the modified address, allowing incoming customer requests to be properly routed and restoring service availability.

The exact mechanism by which the infrastructure-level process introduced the incorrect routing address has been determined and we are working on a long-term fix.

Detection

‌

The incident was first detected at 6:02 pm UTC on April 20, 2026, when automated monitoring reported failures in the Autopilot for Everyone service. Multiple alerts were triggered simultaneously, including service availability checks and automated browser-based tests targeting the affected region, all indicating that the service was unreachable. Engineers observed HTTP 404 errors on all service endpoints, including health checks, along with routing-level "no route" errors confirming that traffic could not reach the service.

Response

The service update that triggered the issue completed at approximately 6:00 pm UTC. The engineering team attempted to revert the change, but the rollback did not resolve the issue. Approximately 43 minutes elapsed between the deployment and attempted rollback. The persistent errors after the revert prompted the team to escalate, formally declare an incident, and begin a coordinated response.

Upon detection, our engineering team began investigating the routing configuration and identified that it referenced an incorrect internal address that did not match the address used by incoming customer traffic. A revert of the service update had already been attempted but did not resolve the issue.

To confirm the diagnosis, the team performed targeted tests against both the incorrect and correct addresses. Requests sent to the incorrect address returned successfully, while requests using the expected address failed — confirming that the routing configuration was functional but pointing to an unsupported destination.

By 7:06 pm UTC, the team had formulated a plan to manually patch the routing configuration by adding the correct address alongside the existing incorrect entry. This additive approach was chosen as a safe, non-destructive fix that would restore service without risking disruption to any processes that might depend on the existing configuration.

At 7:11 pm UTC, the routing configuration was patched. Health checks immediately returned successful responses, and automated service monitoring confirmed that the service was recovering. By 7:14 pm UTC, the incident was marked as mitigated and normal functionality was restored. The team continued monitoring the service for approximately one hour, confirming a full recovery with no further failures. The incident was marked as fully resolved at 8:14 pm UTC.

Follow-up

‌

To prevent similar incidents in the future, we are implementing the following improvements:

• Infrastructure process investigation: We have identified why an infrastructure-level process modified the routing configuration. We will follow up with safeguards to ensure that modifications are backwards-compatible with deployments running older releases.

We are committed to making our systems more resilient and transparent. These improvements will help us detect configuration issues earlier, reduce recovery times, and deliver a more reliable experience for all customers.

Resolved: We have applied a mitigation and are seeing traffic return to normal. We will continue to monitor the situation as it improves

Monitoring: We have applied a mitigation and are seeing traffic return to normal. We will continue to monitor the situation as it improves

Investigating: Users may be unable to sign-in to Autopilot for Everyone, and may be unable to send messages even if already logged in.

Resolved: The issue has been resolved

Monitoring: We are continuing to follow the cloud provider's outage until it is fully resolved.

Monitoring: We are continuing to follow the cloud provider's outage until it is fully resolved.

Monitoring: While we are not seeing any more impact on Cloud Robot VMs, we are continuing to follow the cloud provider's outage until it is fully resolved.

Monitoring: We are seeing the remaining VMs recover, we will monitor to ensure there is no regression

Monitoring: The cloud service provider is still actively working on completing their mitigation efforts

Monitoring: Some VMs have still not recovered, and the cloud service provider is still actively working on completing their mitigation efforts

Monitoring: The cloud service provider has applied mitigations and is starting to see improvements from their end. We are monitoring our services to ensure they are recovering as well.

Identified: The cloud service provider has identified the issue and started applying a mitigation, we are continuing to follow up with them for more updates. We do not have an ETA for when the mitigation will be completed yet.

Identified: We are still awaiting further details from the cloud service provider. We are exploring failover options as well

Identified: The upstream Cloud provider has confirmed an outage impacting VMs for Cloud Robots VM in the US and Delayed US regions Impact: Users may be unable to start robots Next update: We are working with the provider to understand mitigation timelines.

Resolved: The issue has been resolved

Monitoring: The mitigation has been rolled out, and we are validating that it has resolved the issue

Identified: We have identified a mitigation and validated it in a lower environment. We are rolling out the mitigation to all affected regions.

Identified: 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

Identified: We are continuing to develop and validate a mitigation for this issue

Identified: We have a mitigation and are validating it prior to deploying it to production

Identified: We are still working on a mitigation for this issue

Identified: We are validating the reversion of the improper configuration in a lower environment, and will begin deploying it to production regions shortly

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.

Investigating: 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.

Investigating: We are continuing to investigate the cause of the issues, we will provide an update as soon as we begin working on a mitigation

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.

Resolved: The issue is resolved and Tenant Creation in Canada is operating as expected. Impact: All user facing functionality is available.

Identified: We have identified the cause of the outage impacting Tenant creation for Orchestrator in Canada and are working on a fix. Impact: Users may continue to be unable to Create tenants in Canada region Next update: Our focus is on restoring service as quickly as possible.

Investigating: We continue to investigate the cause of the issue impacting Tenant Creation for Orchestrator in Canada and are working on a fix. Impact: Users may continue to be unable to Create tenants. Next update: Our focus is on restoring service as quickly as possible.

Investigating: We are continuing to investigate the cause of the outage impacting Tenant Creation for Orchestrator in Canada and are working on a fix. Impact: Users may continue to be unable to Create tenants. Next update: Our focus is on restoring service as quickly as possible.

Investigating: We are investigating reports of an outage impacting Tenant Creation for Orchestrator in Canada. Impact: Users may be unable to Create tenants in Canada Next update: Our teams are working to understand the cause and scope and will share updates as available.

Resolved: In the GXP US region, between 13:28:33 UTC and 13:52:42 UTC on April 22, 2026, customers experienced HTTP 404 errors when retrieving extractions for IXP UCD models, resulting in a full outage of runtime extractions during that period. The issue also impacted CM predictions, with additional 404 errors observed . This issue has since been resolved.

Monitoring: We identified an issue that caused some IXP models to be unavailable or incorrectly shown as “not found.” A fix has been deployed, and we are continuing to monitor the situation closely. We will share a detailed root cause analysis for this incident at a later time.