UiPath Outage History

UiPath is up right now

UiPath had 165 outages in the last 2 years totaling 60h 47m of downtime — averaging 6.8 incidents per month.

There were 165 UiPath outages since February 23, 2026 totaling 60h 47m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.uipath.com

Notice October 6, 2026

UAE - Automation Cloud Services - Degraded performance

Detected by Pingoru
Oct 06, 2026, 12:38 PM UTC
Resolved
Oct 06, 2026, 05:09 PM UTC
Duration
4h 31m
Affected: Automation CloudOrchestratorAutomation HubAppsAutomation OpsInsightsTest ManagerServerless RobotsStudio WebContext GroundingAutopilot for EveryoneAutopilot (Plugins)AgentsCloud Robots - VMContext GroundingIntegration ServiceAction CenterAgentic OrchestrationAutopilot for DevelopersData ServiceDocument UnderstandingSolutions ManagementTest ManagerNotifications
Timeline · 8 updates
  1. identified Oct 06, 2026, 12:38 PM UTC

    We are observing degraded performance for services in UAE

  2. investigating Oct 06, 2026, 12:43 PM UTC

    We are currently investigating this issue.

  3. identified Oct 06, 2026, 02:01 PM UTC

    We have identified the issue as a network routing problem with a third-party service provider, affecting connectivity for our services hosted in the UAE. We are working with our upstream provider on resolution and will update progress here.

  4. identified Oct 06, 2026, 02:22 PM UTC

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

  5. monitoring Oct 06, 2026, 02:51 PM UTC

    We are monitoring connectivity and will update this page once stability is confirmed.

  6. monitoring Oct 06, 2026, 03:07 PM UTC

    We are continuing to monitor for any further issues.

  7. monitoring Oct 06, 2026, 03:09 PM UTC

    We are continuing to monitor for any further issues.

  8. resolved Oct 06, 2026, 05:09 PM UTC

    The incident has been resolved.

Read the full incident report →

Minor October 2, 2026

Delays starting jobs on Cloud Robots in the US region

Detected by Pingoru
Oct 02, 2026, 04:23 PM UTC
Resolved
Oct 02, 2026, 05:03 PM UTC
Duration
39m
Affected: OrchestratorOrchestratorCloud Robots - VMCloud Robots - VM
Timeline · 4 updates
  1. investigating Oct 02, 2026, 04:23 PM UTC

    Since about 15:05 UTC, some customers in the US region may see jobs that run on Cloud Robots take longer than usual to start, or stay in the Pending state. Jobs on your own robots are not affected, and neither are other regions. We've found the likely cause and are working to restore normal job processing. Jobs that are already queued are not lost and will be processed once the issue is resolved. We'll post another update within 60 minutes.

  2. monitoring Oct 02, 2026, 04:34 PM UTC

    We've applied a fix for the issue that delayed jobs on Cloud Robots in the US region, and jobs are starting normally again. Jobs that were delayed are now being processed. We're monitoring to make sure the service stays stable and will post another update within 60 minutes.

  3. monitoring Oct 02, 2026, 04:51 PM UTC

    After further work on the issue, jobs on Cloud Robots in the US region are now starting normally. Jobs that were delayed earlier are being processed. We're continuing to monitor the service and will post another update once the issue is resolved.

  4. resolved Oct 02, 2026, 05:03 PM UTC

    This issue has been resolved. Between 15:05 and 16:39 UTC, jobs on Cloud Robots in the US region were slow to start or stayed in the Pending state. Jobs have been starting normally since 16:39 UTC, and jobs that were delayed during this time have now been processed. We apologize for the disruption.

Read the full incident report →

Major September 18, 2026

Service disruption for Maestro Flow in South Korea region

Detected by Pingoru
Sep 18, 2026, 06:03 PM UTC
Resolved
Sep 18, 2026, 06:03 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Sep 18, 2026, 06:03 PM UTC

    During the General Availability (GA) rollout of Maestro Flow, an issue was identified in the South Korea region where one of the scale units had not been deployed, causing the flow to fail.

Read the full incident report →