UiPath Outage History

UiPath is up right now

UiPath had 87 outages in the last 2 years totaling 57h 54m of downtime — averaging 3.6 incidents per month.

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

Source: https://status.uipath.com

Minor June 16, 2026

Intermittent AzureOpenAI failures on India (ongoing) and Europe (mitigated)

Detected by Pingoru
Jun 16, 2026, 08:58 AM UTC
Resolved
Jun 16, 2026, 01:38 PM UTC
Duration
4h 39m
Affected: Document UnderstandingIXP
Timeline · 3 updates
  1. identified Jun 16, 2026, 08:58 AM UTC

    We have identified the cause of the degraded performance impacting Azure OpenAI LLM models for Document Understanding in India and are working on mitigation. Mitigation already applied for Europe. Impact: Users may experience intermittent LLM model failures. Additional updates will be provided as we move toward resolution.

  2. identified Jun 16, 2026, 10:16 AM UTC

    We have identified the cause of the degraded performance impacting Azure OpenAI LLM models for Document Understanding in India and are working on mitigation. Mitigation already applied for Europe. Contacted and waiting for the LLM model provider (Azure OpenAI) mitigation to take place. Impact: Users may experience intermittent LLM model failures. Additional updates will be provided as we move toward resolution.

  3. resolved Jun 16, 2026, 01:38 PM UTC

    The issue has been resolved and availability has returned to expected levels. Impact: No ongoing user impact.

Read the full incident report →

Notice June 12, 2026

Integration Service New Connection Failures in the Australia Region

Detected by Pingoru
Jun 12, 2026, 06:27 AM UTC
Resolved
Jun 12, 2026, 04:30 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 12, 2026, 06:27 AM UTC

    UiPath Integration Service in the Australia region, where customers may have experience failures while creating new connections. The issue started at approximately 03:51 AM UTC, 12 June 2026 till 05:59AM UTC, 12 June 2026. Existing connections and running integrations are not impacted. The issue is resolved and service is healthy.

Read the full incident report →

Minor June 11, 2026

Degraded Login Performance in the United States Region

Detected by Pingoru
Jun 11, 2026, 10:43 PM UTC
Resolved
Jun 11, 2026, 11:49 PM UTC
Duration
1h 5m
Affected: OrchestratorIXP
Timeline · 3 updates
  1. investigating Jun 11, 2026, 10:43 PM UTC

    We are investigating reports of degraded performance impacting login functionality for IXP, Orchestrator, and potentially other services in the United States region. Impact: Users in the United States region may experience issues logging in to IXP, Orchestrator, and potentially other services. Our teams are working to identify the cause and will share more details as the investigation progresses.

  2. monitoring Jun 11, 2026, 11:38 PM UTC

    Mitigation has been applied and performance is improving for the issue that impacted login functionality in IXP, Orchestrator, and potentially other services across the United States region. We are monitoring closely to ensure stability.

  3. resolved Jun 11, 2026, 11:49 PM UTC

    The issue impacting login functionality for IXP and Orchestrator in the United States region has been resolved. Impact: Users should no longer experience issues logging in. We will continue to monitor service health as part of normal operations. We are monitoring closely to ensure stability.

Read the full incident report →

Notice June 10, 2026

Intermittent Latency Affecting Serverless Robots in the US Region

Detected by Pingoru
Jun 10, 2026, 03:36 PM UTC
Resolved
Jun 10, 2026, 11:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Jun 10, 2026, 03:36 PM UTC

    From 10 June 2026, 11:00 AM UTC to 2:20 PM UTC, Serverless Robots in the US region experienced intermittent latency due to temporary resource constraints. The issue was identified and mitigated by the engineering team, and service performance has since returned to normal.

Read the full incident report →

Minor June 2, 2026

Customers will observe latency with the new data in insights in US region

Detected by Pingoru
Jun 02, 2026, 05:20 PM UTC
Resolved
Jun 02, 2026, 06:13 PM UTC
Duration
53m
Affected: Insights
Timeline · 3 updates
  1. identified Jun 02, 2026, 05:20 PM UTC

    We have identified the cause of the degraded performance. Impact: Users may experience latency with the new data from orchestrator in insights in US region Additional updates will be provided as we move toward resolution.

  2. identified Jun 02, 2026, 05:23 PM UTC

    We have identified the cause of the degraded performance. We are working on the resolution

  3. resolved Jun 02, 2026, 06:13 PM UTC

    Issue is resolved now.

Read the full incident report →

Minor May 29, 2026

Service Degradation Affecting Document Understanding, Agents, IXP, and GenAI Activities

Detected by Pingoru
May 29, 2026, 04:18 PM UTC
Resolved
May 29, 2026, 05:48 PM UTC
Duration
1h 30m
Affected: Document UnderstandingDocument UnderstandingAgentsIXPIXPAgentsAgents
Timeline · 3 updates
  1. investigating May 29, 2026, 04:18 PM UTC

    An issue with an upstream provider may be impacting GPT-4.0-powered functionality for Document Understanding, Agents, IXP, and GenAI Activities across multiple regions, and we are investigating. Impact: Users may experience request failures, increased error rates, or degraded performance when using GPT-4.0-powered features and workflows.

  2. identified May 29, 2026, 05:03 PM UTC

    An issue with an upstream provider may be impacting GPT-4.0-powered functionality for Document Understanding, Agents, IXP, and GenAI Activities across multiple regions, and we are investigating. Impact: Users may experience request failures, increased error rates, or degraded performance when using GPT-4.0-powered features and workflows. Our teams have identified a potential mitigation and are actively implementing it to reduce customer impact. We will continue to provide updates as progress is made.

  3. resolved May 29, 2026, 05:48 PM UTC

    The mitigation has been successfully implemented, and service has been restored. Impact has been resolved for Document Understanding, Agents, IXP, and GenAI Activities across all affected regions. Users should no longer experience request failures, elevated error rates, or degraded performance when using GPT-4.0-powered features and workflows. We will continue to monitor the services to ensure stability.

Read the full incident report →

Minor May 18, 2026

Multiple Regions - Integration Service & Action Center — Degraded service

Detected by Pingoru
May 18, 2026, 11:12 AM UTC
Resolved
May 18, 2026, 06:43 PM UTC
Duration
7h 30m
Affected: Action CenterAction CenterAction CenterAction CenterAction CenterAction CenterAction CenterAction CenterAction CenterAction CenterIntegration ServiceIntegration ServiceIntegration ServiceIntegration ServiceIntegration ServiceIntegration ServiceIntegration ServiceIntegration ServiceIntegration ServiceIntegration ServiceIntegration Service
Timeline · 7 updates
  1. investigating May 18, 2026, 11:12 AM UTC

    We are seeing issue with Microsoft team connecters. We will continue to provide updates as our investigation progresses.

  2. identified May 18, 2026, 12:30 PM UTC

    The issue has been identified and a fix is being implemented.

  3. identified May 18, 2026, 01:32 PM UTC

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

  4. identified May 18, 2026, 02:46 PM UTC

    We are currently applying a fix across all regions. Thank you for your patience.

  5. identified May 18, 2026, 04:21 PM UTC

    The rollout is ongoing but taking longer than expected. We will provide another update once the deployment is fully complete. Thank you for your patience.

  6. monitoring May 18, 2026, 06:26 PM UTC

    The fix has been deployed. We are monitoring the situation and will close this incident once full stability is confirmed.

  7. resolved May 18, 2026, 06:43 PM UTC

    We have confirmed that the issue is fully resolved and all services are functioning normally.

Read the full incident report →

Major May 1, 2026

Multiple Regions - Signing With Microsoft is momentarily impacted

Detected by Pingoru
May 01, 2026, 05:59 PM UTC
Resolved
May 01, 2026, 06:37 PM UTC
Duration
37m
Affected: Automation CloudAutomation CloudAutomation CloudAutomation CloudAutomation CloudAutomation CloudAutomation CloudAutomation CloudAutomation CloudAutomation CloudAutomation CloudAutomation CloudCustomer PortalCustomer PortalCustomer PortalCustomer PortalCustomer PortalCustomer PortalCustomer PortalCustomer PortalCustomer PortalCustomer PortalCustomer Portal
Timeline · 4 updates
  1. investigating May 01, 2026, 05:59 PM UTC

    Signing With Microsoft is momentarily impacted

  2. identified May 01, 2026, 06:10 PM UTC

    The issue has been identified, and the team is actively working on mitigation. Further updates will be shared as progress continues.

  3. monitoring May 01, 2026, 06:35 PM UTC

    The issue has been mitigated, and services are now operating normally. We will continue to monitor the situation.”

  4. resolved May 01, 2026, 06:37 PM UTC

    The issue has been mitigated, and services are now operating normally. We will continue to monitor the situation.”

Read the full incident report →

Critical April 30, 2026

Australia - Studio web & Orchestrator - Unable to access

Detected by Pingoru
Apr 30, 2026, 07:43 AM UTC
Resolved
Apr 30, 2026, 08:24 AM UTC
Duration
40m
Affected: OrchestratorStudio Web
Timeline · 4 updates
  1. investigating Apr 30, 2026, 07:43 AM UTC

    We are currently investigating an issue where users are unable to access Studio Web in the Australia region. Our team is actively working to identify the root cause and resolve it as quickly as possible.

  2. investigating Apr 30, 2026, 08:01 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Apr 30, 2026, 08:12 AM UTC

    A fix has been implemented for this issue. We are currently monitoring the service to ensure stability.

  4. resolved Apr 30, 2026, 08:24 AM UTC

    The issue has been resolved. Users should now be able to access the service normally.

Read the full incident report →