UiPath Status

Postmortem: ## Customer Impact

Between Feb 25, 2026 5:12PM UTC to Feb 25, 2026 8:40PM UTC, Conversational Agents Service was experiencing performance degradation in multiple regions. Customers experienced increased latency on all actions related to conversational agents, including any existing and new chats. Customers in the EU region experienced the highest amount of latency in this period.

Root Cause

The team made a change in the previous week to fix buggy behavior with cached requests from our database. This removal, however, hurt performance across all our environments (development, pre-production and production), and was apparent for some of our more heavy computational queries.

Detection

Monitoring alerts for the database quickly detected the issue because of the high usage, alerting Engineering staff to increased DTU% averaging and reaching a maximum of between 95-100%.

Response

The team began investigating the issue, noting that they were seeing higher than average latency and dug deeper to understand possible reasons this was impacting Europe first. Originally it was only a handful of orgs experiencing this, but we saw that number was slowly increasing.

We later saw a pattern that other regions were also impacted, even though those regions didn’t fire any alerts. That’s when we proceeded with reverting the original change made in the previous week. We monitored the performance in each region until it was fully observed latency had dropped.

Follow-Up

We will update alerts in pre-production and production environments with a lower threshold so that we can catch this earlier.

Resolved: Issue has been resolved.

Monitoring: We have deployed fix in all regions and seeing improvements..

Identified: We are seeing improvements in performance with the conversational Agents. We are active working on fixing it.

Identified: We have identified the issue. We are working on fixing it.

Investigating: Customers using conversational agent service will experience latency or performance degradation in multiple regions.  We are investigating the issue"

Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• India
• UK
• Switzerland

Resolved: Starting at 2/26/2026 1:30 PM UTC to 2/27/2026 3:40 PM UTC

We experienced an incident affecting Integration Service connectors used by the AI Trust Layer “Bring Your Own” (BYO) feature.

Customers using BYO LLM/LLM Configurations to power Agents, GenAI Activities, or other agentic products may have encountered workflow failures during the impacted period.

The issue occurred because we were unable to retrieve required connection details at runtime, resulting in failed requests to customer-configured external models.

The issue has been identified and resolved. Service is fully restored, though workflows that failed during the incident window may need to be re-run. We continue to monitor the system to ensure stability.

Monitoring: Starting at 2/26/2026 1:30 PM UTC to 2/27/2026 3:40 PM UTC

We experienced an incident affecting Integration Service connectors used by the AI Trust Layer “Bring Your Own” (BYO) feature.

Customers using BYO LLM/LLM Configurations to power Agents, GenAI Activities, or other agentic products may have encountered workflow failures during the impacted period.

The issue occurred because we were unable to retrieve required connection details at runtime, resulting in failed requests to customer-configured external models.

The issue has been identified and resolved. Service is fully restored, though workflows that failed during the incident window may need to be re-run. We continue to monitor the system to ensure stability.

Resolved: The incident has been fully resolved. We identified that a recent update unintentionally caused some previously available connections to not appear. The issue has been corrected, and all connections are now restored. There was no data loss or long-term impact. Thank you for your patience.

Monitoring: A fix has been implemented and we are monitoring the results.

Identified: We have completed validation of the fix in our testing environments and will begin rolling it out shortly.

Identified: We are continuing to validate the fix in our testing environments. We will provide further updates as progress is made.

Identified: We have identified a fix and are actively validating it in our testing environments. We will continue to provide updates as we make progress.

Identified: We are continuing to work on a fix for this issue.

Identified: We have identified the scope of the issue. The impact is limited to the Create VDO Entity preview feature. This action is currently not functioning as expected for a subset of connectors.

Identified: We have identified the scope of the issue. The impact is limited to the Create Entity preview feature. This action is currently not functioning as expected for a subset of connectors.

Affected connectors: • SAP C4C • Oracle NetSuite • Zendesk • HubSpot CRM • BambooHR • Zoho Desk • UiPath Data Fabric • QuickBooks Online • FreshDesk • DocuSign

Investigating: We are currently investigating the issue Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Resolved: Our team has not observed errors in the last 30 minutes, we will continue monitoring.

Monitoring: Our team has not observed errors in the last 30 minutes, we will continue monitoring.

Investigating: We are investigating an outage affecting Document Understanding in East US. Impact: Users may be unable to Classify and/or Extract documents.

Resolved: This incident has been resolved. The issue has been mitigated and services are now operating normally. Thank you for your patience and understanding

Identified: We have confirmed the root cause of the outage impacting Traces UI for Orchestrator in Multiple Regions. Impact: Users may still be unable to view traces.

Users impacted by this issue can view traces from the Agents page.

Identified: We have confirmed the root cause of the outage impacting Traces UI for Orchestrator in Multiple Regions. Impact: Users may still be unable to view traces. Users impacted by this issue can view traces from the Agents page.

Identified: We have confirmed the root cause of the outage impacting Traces UI for Orchestrator in Multiple Regions. Impact: Users may still be unable to view traces.

Identified: We have confirmed the root cause of the outage impacting Traces UI for Orchestrator in Multiple Regions. Impact: Users may still be unable to view traces.

Identified: We have confirmed the root cause of the outage impacting Traces UI for Orchestrator in Multiple Regions. Impact: Users may still be unable to view traces. Next update: Restoration efforts are in progress.

Identified: We are investigating reports that Traces UI for Orchestrator is unavailable in Multiple Regions. Impact: Users may be unable to view Traces UI. Next update: We are actively investigating the issue.

Investigating: We are investigating reports that Traces UI for Orchestrator is unavailable in Multiple Regions. Impact: Users may be unable to view Traces UI. Next update: We are actively investigating the issue.

Resolved: This incident has been resolved. We experienced a service disruption in Canada that affected document classification and extraction. The issue was caused by temporary performance limits in our system. A fix has been implemented, and the service is now fully operational. Thank you for your patience.

Monitoring: A fix has been implemented and we are monitoring the results.

Investigating: We are investigating an outage affecting Document Understanding in Canada. Impact: Users may be unable to Classify and/or Extract documents. Next update: Diagnostic data is being collected to determine next steps.

Investigating: We are investigating an outage affecting Document Understanding in Canada. Impact: Users may be unable to Classify and/or Extract documents. Next update: Diagnostic data is being collected to determine next steps.

Resolved: DU Metering errors have not recurred in the past 3 hours. We are continuing to monitor for any further occurrences before closing this incident.

Monitoring: DU Metering errors have not recurred in the past 3 hours. We are continuing to monitor for any further occurrences before closing this incident.

Monitoring: DU Metering errors have not recurred in the past 3 hours. We are continuing to monitor for any further occurrences before closing this incident.

Monitoring: DU Metering errors have not recurred in the past hour. We are continuing to monitor for any further occurrences before closing this incident.

Monitoring: DU Metering errors have not recurred in the past hour. We are continuing to monitor for any further occurrences before closing this incident.

Investigating: We are continuing to investigate an outage affecting DU Metering for Document Understanding in Canada. Impact: Users may be unable to access DU Metering. Next update: Diagnostic data is being collected to determine next steps.

Investigating: We are investigating an outage affecting DU Metering for Document Understanding in Canada. Impact: Users may be unable to access DU Metering. Next update: Diagnostic data is being collected to determine next steps.

Resolved: Our cloud service provider has confirmed that the issue on their end has been fully resolved. Our service has fully recovered and is stable.

Monitoring: We are currently not observing new errors related to this issue, and service performance appears to be stabilizing. However, the underlying root cause has not yet been fully confirmed by our cloud service provider. We continue to work closely with them to validate the cause and ensure a complete and sustained resolution.

We will share further updates as more information becomes available.

Identified: Customers using Anthropic Sonnet 3.5v1 may experience issues with the Agents service. The issue has been identified with our cloud service provider, and we are actively working with them to resolve it as quickly as possible.