UiPath Status

Resolved: The incident has been resolved, and our monitoring systems confirm that services are operating normally. Initial investigation indicates that users in the United Kingdom were most affected, followed by South Africa. The primary impacted service was Orchestrator

Monitoring: We’re seeing a reduction in errors. We continue to closely monitor system performance through our monitoring platform and will provide another update shortly

Investigating: Multiple services are experiencing intermittent availability issues across multiple regions, resulting in occasional 503 errors for some requests

Resolved: The incident has been resolved, and our monitoring systems confirm that marketplace website operating normally.

Monitoring: Marketplace team has applied the fix and we are currently monitoring.

Investigating: We are currently investigating an issue causing degraded performance and timeouts on the marketplace website.

Postmortem: ## Customer Impact

Between 09:41 UTC and 13:24 UTC, customers using IXP in the U.S. experienced generally poor performance in the form of slow API requests.

In addition, these specific actions had increased error rates:

• Consuming stream
• Uploading documents

For a small number of specific clients, streams were unable to be consumed entirely during this time.

Root Cause

An IXP database migration took place in the U.S. region at 09:41 UTC on February 3, 2026.

This migration changed the underlying database queries used by several of our API routes. One of these database queries was poorly optimized, leading to bad performance when executed against the high volume of data present in the U.S. region. This database query was used by the streams and document upload routes.

Detection

Our engineering team was closely monitoring the migration, and observed an increase in stream response times. In addition, automated alerts picked up on the increased error rates and automatically alerted us while an investigation was underway.

Response

The team worked to find and fix the problem with the database query. At 13:04 UTC, a hotfix was deployed. By 13:24 UTC, API response times and IXP performance had returned to normal.

Follow-Up

We recognize how disruptive this incident was for our customers, especially those relying on timely document processing and stream analytics. The IXP team will ensure that in future, similar migrations:

• Have better performance testing
• Have faster rollback capabilities

Resolved: The incident has been resolved and system performance has returned to normal. A postmortem will be shared soon with additional details.

Monitoring: The fix has been applied and we are seeing improvements in system performance through our monitoring systems. We will continue to closely monitor performance for some time before marking the incident as resolved.

Identified: Our hotfix deployment is currently in progress. We will provide an update once the deployment is complete and we begin monitoring system behavior to ensure performance is fully restored

Identified: Our engineering team has identified a fix and is actively working on rolling it out to restore normal performance.

Investigating: We have identified the issue our engineering team is actively working on a fix to restore normal performance. Our investigation also indicates that the issue is affecting overall IXP performance in the US region, and is not limited to Streams

Investigating: We are currently investigating an issue causing performance degradation and increased latency for Streams in the US region. Some customers may experience slow response times (exceeding 5 minutes) and request timeouts when calling Streams

Postmortem: ## Customer Impact

On January 30, for 57 minutes, from 13:20 to 14:17 UTC, Maestro workflow and agent executions experienced a partial outage in UiPath Europe Community region. During this window, Maestro workflow and agent executions would have stopped.

Root Cause

A planned configuration change was made to ensure proper IP address assignment from our service. This caused a security measure to unintentionally activate, which resulted in a loss of database connectivity from our workflow engine.

Detection

We were alerted of the issue soon after the configuration change took place and the workflow engine started experiencing downtime.

Response

As soon as we were alerted of the issue, we began diagnosing the issue and quickly determined that the IP address configuration change was the likely culprit.

Before any additional action could be taken, another internal system reconciled the configuration change with the activated security measure and automatically resolved the problem.
The IP configuration change rollout was halted until this analysis could be completed.

Follow-Up

We are working to create a rollout process that takes these systems into account. The new process will be attempted in non-production environments before continuing with production environments.

Resolved: This incident has been resolved.

Investigating: We are currently investigating this issue.

Postmortem: ## Customer Impact

On January 30, for 57 minutes, from 13:20 to 14:17 UTC, Maestro workflow and agent executions experienced a partial outage in UiPath Europe Community region. During this window, Maestro workflow and agent executions would have stopped.

Root Cause

A planned configuration change was made to ensure proper IP address assignment from our service. This caused a security measure to unintentionally activate, which resulted in a loss of database connectivity from our workflow engine.

Detection

We were alerted of the issue soon after the configuration change took place and the workflow engine started experiencing downtime.

Response

As soon as we were alerted of the issue, we began diagnosing the issue and quickly determined that the IP address configuration change was the likely culprit.

Before any additional action could be taken, another internal system reconciled the configuration change with the activated security measure and automatically resolved the problem.
The IP configuration change rollout was halted until this analysis could be completed.

Follow-Up

We are working to create a rollout process that takes these systems into account. The new process will be attempted in non-production environments before continuing with production environments.

Resolved: This incident has been resolved.

Investigating: We are currently investigating this issue.