UiPath Outage History

UiPath is up right now

UiPath had 163 outages in the last 2 years totaling 57h 32m of downtime — averaging 6.7 incidents per month.

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

Source: https://status.uipath.com

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 →

Minor October 1, 2026

Agent failures and model selection issues across all regions

Detected by Pingoru
Oct 01, 2026, 06:57 PM UTC
Resolved
Oct 01, 2026, 07:46 PM UTC
Duration
48m
Affected: AgentsAgentsAgentsAgentsAgentsAgentsAgentsAgentsAgentsAgentsAgentsAgents
Timeline · 3 updates
  1. investigating Oct 01, 2026, 06:57 PM UTC

    Starting October 1 at approximately 1:30 PM UTC, some Agents, including both low-code and coded agents, began experiencing failures across all regions when using gemini-3.1-pro-preview and gpt-4o-2024-05-13. These models may also be unavailable for selection during agent design. We are actively investigating and working on a fix.

  2. identified Oct 01, 2026, 07:05 PM UTC

    We have identified the issue and are deploying a fix. Agents using the affected models may continue to experience failures, and the models may remain unavailable for selection during agent design, while the deployment completes.

  3. resolved Oct 01, 2026, 07:46 PM UTC

    We have reverted the change that caused this issue and confirmed that the affected models are available again. Some agents may continue to experience intermittent failures while instances refresh. We are continuing to monitor agent design and execution for gemini-3.1-pro-preview and gpt-4o-2024-05-13.

Read the full incident report →

Minor October 1, 2026

Failures in low-code agents for community users in Europe

Detected by Pingoru
Oct 01, 2026, 06:17 PM UTC
Resolved
Oct 01, 2026, 08:08 PM UTC
Duration
1h 50m
Affected: Studio Web
Timeline · 3 updates
  1. investigating Oct 01, 2026, 06:17 PM UTC

    Starting October 1 at approximately 12:00 PM UTC, community users in Europe may experience failures in LowCode Agents that use solution-local Action Apps. We have confirmed the impact is limited to community users in Europe. We are actively investigating the issue, determining the extent of the failures, and working on a fix.

  2. identified Oct 01, 2026, 06:25 PM UTC

    We have identified the issue causing failures in low-code agents that use solution-local action apps for community users in Europe. We are rolling back the previous changes and continuing to monitor the recovery. We will provide another update once rollback is complete or if we have additional information to share.

  3. resolved Oct 01, 2026, 08:08 PM UTC

    We have confirmed that the rollback has completed and the issue affecting low-code agents that use solution-local action apps for community users in Europe has been resolved. Services have recovered, and we are closing this incident.

Read the full incident report →

Notice October 1, 2026

Delete requests failed for Australia cloud services

Detected by Pingoru
Oct 01, 2026, 02:00 PM UTC
Resolved
Oct 01, 2026, 02:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Oct 01, 2026, 04:32 PM UTC

    Between 14:23 and 16:04 UTC on 1 October 2026, some requests to delete items in UiPath Automation Cloud services in the Australia region failed with "404 Not Found" errors. Services affected included Orchestrator, Document Understanding, AI Center and Data Service. Other operations, such as viewing, creating and updating items, worked normally. The cause was a configuration change to our request routing. We rolled it back and the service is fully restored.

Read the full incident report →

Minor October 1, 2026

Multiple Regions - Multiple UiPath Services - Degraded Performance

Detected by Pingoru
Oct 01, 2026, 04:12 AM UTC
Resolved
Oct 01, 2026, 07:48 AM UTC
Duration
3h 36m
Affected: Integration ServiceIntegration ServiceIntegration ServiceIntegration ServiceIntegration ServiceIntegration ServiceAgentsIXPIXPContext GroundingAgentsAgentsAgentsAgentsAutopilot for DevelopersAgents
Timeline · 4 updates
  1. investigating Oct 01, 2026, 04:12 AM UTC

    We are investigating degraded performance impacting UiPath Service from LLM Gateway in Multiple Regions. Our teams are working to identify the cause and we will share more details as the investigation progresses.

  2. monitoring Oct 01, 2026, 05:42 AM UTC

    A fix has been implemented, and our team is actively monitoring the results to confirm the issue is fully resolved.

  3. monitoring Oct 01, 2026, 06:28 AM UTC

    We continue to monitor the results of the implemented fix to ensure the issue is fully resolved.

  4. resolved Oct 01, 2026, 07:48 AM UTC

    The issue has been resolved, and services are operating normally. We apologize for any inconvenience this may have caused.

Read the full incident report →

Notice September 24, 2026

Robot live stream issues in US region

Detected by Pingoru
Sep 24, 2026, 09:45 PM UTC
Resolved
Sep 24, 2026, 10:50 PM UTC
Duration
1h 4m
Timeline · 3 updates
  1. investigating Sep 24, 2026, 09:45 PM UTC

    We're investigating issues with robot live streaming in the US region. We'll share an update as soon as we have more information.

  2. monitoring Sep 24, 2026, 10:24 PM UTC

    We've identified the cause of the robot live streaming issues in the US region and applied a fix. We're actively monitoring to confirm the issue is fully resolved.

  3. resolved Sep 24, 2026, 10:50 PM UTC

    The issue affecting robot live streaming in the US region has been resolved. Live streaming is working as expected. We apologize for any inconvenience.

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 →