UiPath Status

Resolved: The incident has been resolved.

Monitoring: All regions have recovered, we will monitor to ensure stability

Monitoring: The mitigation is taking effect, and we are seeing performance return to normal

Monitoring: The mitigation is taking effect, and we are seeing performance return to normal

Identified: We have a mitigation available, and are beginning to roll it out to affected regions.

We will provide more updates as the mitigation takes effect

Identified: We have identified the cause of the degraded performance impacting the GetJobs Activity for Orchestrator in Europe, Switzerland, Canada, India, Australia and UAE. We are actively working on a mitigation, which will be applied shortly

Additional updates will be provided as we move toward resolution.

Resolved: This incident has been resolved.

Monitoring: Fix is now live in all regions. Early metrics from monitoring look stable. We'll keep a close eye on everything for the next 30 minutes before declaring full resolution.

Identified: The fix has now been successfully deployed to the UK. As a result, the following regions are now operational: UK, India, UAE, Canada, EU, Australia, Japan, US and Switzerland

Identified: Services have been restored to operational status in India, UAE, Canada, EU, Australia, Japan, US, Switzerland. Validation for the remaining regions (UK, Singapore) is underway.

Identified: Services have been restored to operational status in the EU, Australia, Japan, US and Switzerland. Validation for the remaining regions is underway.

Identified: Deployment and validation for the remaining regions are underway. We will share further updates as soon as they become available.

Identified: The fix is live and working as expected in the US and Japan. We've started deploying it to the remaining affected regions.

Identified: The fix is now live in the US and Japan, and we are monitoring stability in those regions. Concurrently, the team is focused on mitigating the issue across all remaining environments.

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

Identified: We have identified the cause of the degraded performance impacting Orchestrator's 'configured execution settings for API trigger job ignored' in US and we are working on mitigation.

Impact: customers might see configured execution settings for API trigger job ignored in orchestrator.

Investigating: We have identified the issue and currently working on a fix.

Resolved: The issue has been resolved. The mitigation has been effective, and Maestro workflow executions have returned to normal.

Monitoring: We have applied a mitigation and seeing significant performance improvements in Maestro workflow executions. We will continue to monitor to ensure the situation has stabilized.

Investigating: Increased latency affecting Maestro workflow executions in the North Europe

Resolved: The issue remains quiet and has not resurfaced. We are implementing our active monitoring and rapid-response guardrails in place while the engineering team continues investigating the root cause.

Monitoring: The immediate issue has been mitigated. However, because this specific failure mode develops gradually over time, we have additional monitoring in place and collecting more diagnostic data to prevent a recurrence.

Identified: This issue is causing degraded performance impacting maestro instances and team is currently investigating the issue. Impact: Workflows may experience slowness or get stuck.

Resolved: The regional outage has been resolved and all services in US are fully operational. Impact: No ongoing user impact.

Monitoring: The issue has been mitigated and Orchestrator performance has returned to expected levels after degraded performance impacted US.

Impact: No ongoing user impact.

Monitoring: Performance has continued to improve for the issue impacting Orchestrator in the US, and latency has decreased.

Impact: Some users may still experience intermittent degraded performance while we continue to investigate.

We are monitoring closely to ensure stability.

Monitoring: Mitigation has been applied and performance is improving for the issue that impacted Orchestrator in US. Impact: Users may still experience degraded performance, but this should continue to improve. We are monitoring closely to ensure stability.

Monitoring: Mitigation has been applied and performance is improving for the issue that impacted Orchestrator in US. Impact: Users may still experience degraded performance, but this should continue to improve. We are monitoring closely to ensure stability.

Investigating: Increased latency and degraded performance in US, Investigation is in progress.

Investigating: Increased latency and degraded performance in US, Investigation is in progress.

Resolved: This incident has been resolved.

Monitoring: Fix is now live in all regions. Early metrics from monitoring look stable. We'll keep a close eye on everything for the next 30 minutes before declaring full resolution.

Identified: The fix has now been successfully deployed to the UK. As a result, the following regions are now operational: UK, India, UAE, Canada, EU, Australia, Japan, US and Switzerland

Identified: Services have been restored to operational status in India, UAE, Canada, EU, Australia, Japan, US, Switzerland. Validation for the remaining regions (UK, Singapore) is underway.

Identified: Services have been restored to operational status in the EU, Australia, Japan, US and Switzerland. Validation for the remaining regions is underway.

Identified: Deployment and validation for the remaining regions are underway. We will share further updates as soon as they become available.

Identified: The fix is live and working as expected in the US and Japan. We've started deploying it to the remaining affected regions.

Identified: The fix is now live in the US and Japan, and we are monitoring stability in those regions. Concurrently, the team is focused on mitigating the issue across all remaining environments.

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

Identified: We have identified the cause of the degraded performance impacting Orchestrator's 'configured execution settings for API trigger job ignored' in US and we are working on mitigation.

Impact: customers might see configured execution settings for API trigger job ignored in orchestrator.

Investigating: We have identified the issue and currently working on a fix.

Resolved: The issue has been resolved and we are actively monitoring the service.

Monitoring: The issue has been mitigated and we are now monitoring the service currently. Please note that some functionality might take some time to recover as it catches up.

Investigating: We are currently observing a partial outage on IXP and team is investigating this issue.

Resolved: A fix has been deployed to all impacted regions.

Identified: A fix has been identified and we are working on deploying it. Please note that only instances where instance management operations were performed (Pause, resume, retry, goto, migrate, cancel, patchvariable) were impacted.

Identified: We are currently seeing some instance executions become stuck due to elevated error rates following a recent deployment. The root cause has been identified, and our team is actively working to resolve the issue.

Resolved: This incident has been resolved.

Monitoring: Fix is now live in all regions. Early metrics from monitoring look stable. We'll keep a close eye on everything for the next 30 minutes before declaring full resolution.

Identified: The fix has now been successfully deployed to the UK. As a result, the following regions are now operational: UK, India, UAE, Canada, EU, Australia, Japan, US and Switzerland

Identified: Services have been restored to operational status in India, UAE, Canada, EU, Australia, Japan, US, Switzerland. Validation for the remaining regions (UK, Singapore) is underway.

Identified: Services have been restored to operational status in the EU, Australia, Japan, US and Switzerland. Validation for the remaining regions is underway.

Identified: Deployment and validation for the remaining regions are underway. We will share further updates as soon as they become available.

Identified: The fix is live and working as expected in the US and Japan. We've started deploying it to the remaining affected regions.

Identified: The fix is now live in the US and Japan, and we are monitoring stability in those regions. Concurrently, the team is focused on mitigating the issue across all remaining environments.

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

Identified: We have identified the cause of the degraded performance impacting Orchestrator's 'configured execution settings for API trigger job ignored' in US and we are working on mitigation.

Impact: customers might see configured execution settings for API trigger job ignored in orchestrator.

Investigating: We have identified the issue and currently working on a fix.

Resolved: The incident has been resolved.

Monitoring: All regions have recovered, we will monitor to ensure stability

Monitoring: The mitigation is taking effect, and we are seeing performance return to normal

Monitoring: The mitigation is taking effect, and we are seeing performance return to normal

Identified: We have a mitigation available, and are beginning to roll it out to affected regions.

We will provide more updates as the mitigation takes effect

Identified: We have identified the cause of the degraded performance impacting the GetJobs Activity for Orchestrator in Europe, Switzerland, Canada, India, Australia and UAE. We are actively working on a mitigation, which will be applied shortly

Additional updates will be provided as we move toward resolution.

Resolved: This incident has been resolved.

Monitoring: Fix is now live in all regions. Early metrics from monitoring look stable. We'll keep a close eye on everything for the next 30 minutes before declaring full resolution.

Identified: The fix has now been successfully deployed to the UK. As a result, the following regions are now operational: UK, India, UAE, Canada, EU, Australia, Japan, US and Switzerland

Identified: Services have been restored to operational status in India, UAE, Canada, EU, Australia, Japan, US, Switzerland. Validation for the remaining regions (UK, Singapore) is underway.

Identified: Services have been restored to operational status in the EU, Australia, Japan, US and Switzerland. Validation for the remaining regions is underway.

Identified: Deployment and validation for the remaining regions are underway. We will share further updates as soon as they become available.

Identified: The fix is live and working as expected in the US and Japan. We've started deploying it to the remaining affected regions.

Identified: The fix is now live in the US and Japan, and we are monitoring stability in those regions. Concurrently, the team is focused on mitigating the issue across all remaining environments.

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

Identified: We have identified the cause of the degraded performance impacting Orchestrator's 'configured execution settings for API trigger job ignored' in US and we are working on mitigation.

Impact: customers might see configured execution settings for API trigger job ignored in orchestrator.

Investigating: We have identified the issue and currently working on a fix.

Resolved: This incident has been resolved.

Monitoring: Fix is now live in all regions. Early metrics from monitoring look stable. We'll keep a close eye on everything for the next 30 minutes before declaring full resolution.

Identified: The fix has now been successfully deployed to the UK. As a result, the following regions are now operational: UK, India, UAE, Canada, EU, Australia, Japan, US and Switzerland

Identified: Services have been restored to operational status in India, UAE, Canada, EU, Australia, Japan, US, Switzerland. Validation for the remaining regions (UK, Singapore) is underway.

Identified: Services have been restored to operational status in the EU, Australia, Japan, US and Switzerland. Validation for the remaining regions is underway.

Identified: Deployment and validation for the remaining regions are underway. We will share further updates as soon as they become available.

Identified: The fix is live and working as expected in the US and Japan. We've started deploying it to the remaining affected regions.

Identified: The fix is now live in the US and Japan, and we are monitoring stability in those regions. Concurrently, the team is focused on mitigating the issue across all remaining environments.

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

Identified: We have identified the cause of the degraded performance impacting Orchestrator's 'configured execution settings for API trigger job ignored' in US and we are working on mitigation.

Impact: customers might see configured execution settings for API trigger job ignored in orchestrator.

Investigating: We have identified the issue and currently working on a fix.