UiPath Status

Resolved: We observed increased latency affecting Maestro workflow executions in the Europe region between June 12, 2026, 20:00 UTC and June 24, 2026, 15:00 UTC.

Impact: Some Maestro workflows experienced slower-than-normal execution times during this period. No other services were impacted.

The issue was isolated to Maestro workflow execution in the Europe region. Our team has taken corrective actions to restore normal performance and continues to monitor the service to ensure stability.

We apologize for any inconvenience this may have caused.

Monitoring: We observed increased latency affecting Maestro workflow executions in the Europe region between June 12, 2026, 20:00 UTC and June 24, 2026, 15:00 UTC.

Impact: Some Maestro workflows experienced slower-than-normal execution times during this period. No other services were impacted.

The issue was isolated to Maestro workflow execution in the Europe region. Our team has taken corrective actions to restore normal performance and continues to monitor the service to ensure stability.

We apologize for any inconvenience this may have caused.

Resolved: The issue has been resolved and Maestro workflow performance has returned to expected levels after degraded performance impacted Maestro workflow in US. Impact: No ongoing user impact. Agent executions that failed will have to be retried manually.

Monitoring: We have resolved the situation that was causing the degraded performance for Maestro workflows. Impact: Users may still experience degraded performance, but this should continue to improve. We are monitoring closely to ensure stability.

Monitoring: We have resolved the situation that was causing the degraded performance for Maestro workflows. 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 [impacted functionality / user symptom] in Maestro across US. Impact: Users may still experience degraded perfornance but this should continue to improve. We are monitoring closely to ensure stability.

Monitoring: We have resolved the situation that was causing the degraded performance for Maestro workflows.

We had to scale up the capacity for the underlying services. We are actively monitoring the backlog of requests for latencies and will take the action as needed.

Monitoring: We have resolved the situation that was causing the degraded performance for Maestro workflows.

We had to scale up the capacity for the underlying services. We are actively monitoring the backlog of requests for latencies and will take the action as needed.

Investigating: We are investigating reports of degraded performance impacting workflows for Maestro in east US. Impact: Users may experience intermittent failures or stuck workflows. Our teams are working to identify the cause and will share more details as the investigation progresses.

Resolved: The issue has been resolved and Maestro workflow performance has returned to expected levels after degraded performance impacted Maestro workflow in US. Impact: No ongoing user impact. Agent executions that failed will have to be retried manually.

Monitoring: We have resolved the situation that was causing the degraded performance for Maestro workflows. Impact: Users may still experience degraded performance, but this should continue to improve. We are monitoring closely to ensure stability.

Monitoring: We have resolved the situation that was causing the degraded performance for Maestro workflows. 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 [impacted functionality / user symptom] in Maestro across US. Impact: Users may still experience degraded perfornance but this should continue to improve. We are monitoring closely to ensure stability.

Monitoring: We have resolved the situation that was causing the degraded performance for Maestro workflows.

We had to scale up the capacity for the underlying services. We are actively monitoring the backlog of requests for latencies and will take the action as needed.

Monitoring: We have resolved the situation that was causing the degraded performance for Maestro workflows.

We had to scale up the capacity for the underlying services. We are actively monitoring the backlog of requests for latencies and will take the action as needed.

Investigating: We are investigating reports of degraded performance impacting workflows for Maestro in east US. Impact: Users may experience intermittent failures or stuck workflows. Our teams are working to identify the cause and will share more details as the investigation progresses.

Resolved: The issue has been fully resolved, and all operations are now functioning normally. All affected workflows have been processed successfully

Monitoring: Operations have been stabilized for new workflows. We are now actively working through workflows that became pending as a result of the incident.

Investigating: Recovery in TaaS East US began at approximately 12:45 PM PST. The service is currently stable, and we will continue monitoring to ensure sustained recovery.

Investigating: We have scaled up and applied a fix and are seeing positive trends. We will continue to investigate and monitor

Investigating: We are investigating reports of degraded performance impacting workflows for Maestro in east US. Impact: Users may experience intermittent failures or stuck workflows. Our teams are working to identify the cause and will share more details as the investigation progresses.

Investigating: We are investigating reports of degraded performance impacting workflows for Maestro in east US. Impact: Users may experience intermittent failures or stuck workflows. Our teams are working to identify the cause and will share more details as the investigation progresses.

Investigating: We are investigating reports of degraded performance impacting [impacted functionality / user symptom] for [Service] in [Region]. Impact: Users may experience [describe impacted functionality]. Our teams are working to identify the cause and will share more details as the investigation progresses.

Resolved: The issue has been resolved and Maestro workflow performance has returned to expected levels after degraded performance impacted Maestro workflow in US. Impact: No ongoing user impact. Agent executions that failed will have to be retried manually.

Monitoring: We have resolved the situation that was causing the degraded performance for Maestro workflows. Impact: Users may still experience degraded performance, but this should continue to improve. We are monitoring closely to ensure stability.

Monitoring: We have resolved the situation that was causing the degraded performance for Maestro workflows. 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 [impacted functionality / user symptom] in Maestro across US. Impact: Users may still experience degraded perfornance but this should continue to improve. We are monitoring closely to ensure stability.

Monitoring: We have resolved the situation that was causing the degraded performance for Maestro workflows.

We had to scale up the capacity for the underlying services. We are actively monitoring the backlog of requests for latencies and will take the action as needed.

Monitoring: We have resolved the situation that was causing the degraded performance for Maestro workflows.

We had to scale up the capacity for the underlying services. We are actively monitoring the backlog of requests for latencies and will take the action as needed.

Investigating: We are investigating reports of degraded performance impacting workflows for Maestro in east US. Impact: Users may experience intermittent failures or stuck workflows. Our teams are working to identify the cause and will share more details as the investigation progresses.