Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

UiPath Outage History

Every past UiPath outage tracked by IsDown, with detection times, duration, and resolution details.

There were 517 UiPath outages since August 2020. The 176 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Major March 30, 2026

March 2026: Multiple Regions - Agents - Newly deployed Agents experiencing startup issues

Detected Mar 30, 2026 6:12 AM EDT · Resolved Mar 30, 2026 2:28 PM EDT · Duration about 8 hours

UiPath experienced a major incident where newly deployed Agents in Canada, Japan, and USA would not start unless a serverless machine template was assigned to the folder. The issue affected agent startup functionality across multiple regions for 8.3 hours. UiPath resolved the problem while providing customers a manual workaround of adding a serverless machine template to the folder during the outage.

Major March 25, 2026

March 2026: Multiple Regions - Agents - Agent Builder might not load for some customers.

Detected Mar 25, 2026 2:27 PM EDT · Resolved Mar 25, 2026 11:46 PM EDT · Duration about 9 hours

UiPath's Agent Builder service experienced a major outage lasting 9.3 hours across multiple regions, preventing some customers from loading the application due to browser caching issues. Customers could work around the problem by disabling browser cache and refreshing the page while UiPath investigated and developed a fix to properly invalidate cache upon deployment. The issue was fully resolved after UiPath implemented and tested their cache invalidation fix.

Major March 25, 2026

March 2026: Integration services - connection-creation-failing-for-some-tenants

Detected Mar 25, 2026 1:23 PM EDT · Resolved Mar 25, 2026 2:12 PM EDT · Duration about 1 hour

UiPath's Agent Builder service experienced loading issues for some customers across multiple regions, preventing users from accessing the application. The incident was classified as major and affected the Agent Builder functionality specifically. A temporary workaround was provided requiring users to disable browser cache and refresh the page while the root cause was investigated, with the issue resolved within 5 minutes.

Major March 23, 2026

March 2026: Multiple Regions - Cloud Robots- VM - Creation/Editing of VPN Gateway in UiPath Cloud Administration is currently failing. Existing VPN Gateways are not impacted.

Detected Mar 23, 2026 11:27 AM EDT · Resolved Mar 23, 2026 7:29 PM EDT · Duration about 8 hours

UiPath Cloud Administration experienced a major incident where users were unable to create or edit VPN Gateways for Cloud Robots across multiple regions, though existing VPN Gateways continued to function normally. The service team identified the root cause and deployed mitigation measures to resolve the issue. The incident lasted 8 hours and was fully resolved after a monitoring period to ensure system stability.

Major March 23, 2026

March 2026: Europe - Integration Service - New connection creation is failing

Detected Mar 23, 2026 7:42 AM EDT · Resolved Mar 23, 2026 8:37 AM EDT · Duration about 1 hour

UiPath's Integration Service in the Europe region experienced a major outage where new connection creation was failing for 55 minutes. Existing connections and running automations remained unaffected during the incident. The team deployed a fix and monitored the system until full resolution was confirmed.

Major March 20, 2026

March 2026: Multiple Regions - Integration Service - Partial Outage

Detected Mar 20, 2026 3:28 AM EDT · Resolved Mar 20, 2026 3:59 AM EDT · Duration 31 minutes

UiPath's Integration Service experienced a partial outage across multiple regions for 31 minutes, preventing users from viewing existing connections in Orchestrator and creating new connections. The service was restored after a fix was deployed and monitored for stability.

Major March 18, 2026

March 2026: Multiple Regions - Agents - Partial Outage

Detected Mar 18, 2026 3:52 PM EDT · Resolved Mar 18, 2026 6:38 PM EDT · Duration about 3 hours

UiPath experienced a 2.8-hour outage affecting coded agents across multiple regions, where agents failed during the "Prepare Python environment" step when Python 3.12 or higher was specified in pyproject.toml files. Users could work around the issue by lowering their Python version requirement to 3.11 or below until UiPath deployed a permanent fix.

Major March 17, 2026

March 2026: US - IXP - Degraded Performance

Detected Mar 17, 2026 4:01 AM EDT · Resolved Mar 17, 2026 6:54 AM EDT · Duration about 3 hours

UiPath's IXP service in the US region experienced degraded performance for 2.9 hours, causing automations to suffer from increased latency and some requests to return HTTP 503 errors. The engineering team deployed a fix and restored full service after monitoring confirmed the resolution.

Major March 17, 2026

March 2026: Multiple Regions - Customer Portal — Degraded Service

Detected Mar 17, 2026 1:08 AM EDT · Resolved Mar 17, 2026 9:22 AM EDT · Duration about 8 hours

UiPath's Customer Portal experienced degraded service for 8.2 hours due to an upstream dependency disruption, affecting customer support infrastructure, case viewing, account data loading, and file downloads while login and non-support features remained functional. The upstream provider identified and deployed a fix, with system recovery progressing gradually until full service restoration was confirmed. All Customer Portal services returned to normal operation after the upstream dependency issue was fully resolved.

Major March 15, 2026

March 2026: Multiple Regions - Agents and RPA - Web Search Outage

Detected Mar 15, 2026 4:43 PM EDT · Resolved Mar 15, 2026 5:00 PM EDT · Duration 17 minutes

UiPath experienced a 17-minute outage affecting the Web Search tool used in RPA workflows and Agents across multiple regions. Users were unable to run RPA workflows or debug Agents that relied on the Web Search functionality, causing automation failures. The issue was identified and resolved, with services returning to normal operation.