UiPath Status

Resolved: We are investigating reports of the Jobs page not loading Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Investigating: We are investigating reports of the Jobs page not loading Affected Regions:

• Europe
• US
• Japan
• Australia
• Canada
• Singapore
• Delayed US
• Delayed EU
• India
• UK
• Switzerland
• UAE

Resolved: This incident has been resolved; the issue was caused by an internal service communication problem and the impact was limited to Action Center, Agents, Apps, Orchestrator, Solutions Management, and Studio Web. Thank you for your patience.

Monitoring: A fix has been implemented and we are monitoring the results.

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

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved; the issue was caused by an internal service communication problem and the impact was limited to Action Center, Agents, Apps, Orchestrator, Solutions Management, and Studio Web. Thank you for your patience.

Monitoring: A fix has been implemented and we are monitoring the results.

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

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved; the issue was caused by an internal service communication problem and the impact was limited to Action Center, Agents, Apps, Orchestrator, Solutions Management, and Studio Web. Thank you for your patience.

Monitoring: A fix has been implemented and we are monitoring the results.

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

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Postmortem: ## Customer Impact

Between January 16 and January 20, 2026, customers in the Europe region experienced sporadic, intermittent errors in the Document Understanding Classification, Extraction, and Validation services. These errors led to failed requests and temporary disruptions in document processing workflows. The issue worsened on January 19 and was completely resolved by 17:43 UTC on January 20.

Root Cause

The root cause was identified as certain uploaded files containing unusual characters in their filenames, which triggered repeated crashes in a key service component.

Detection

On January 19, the issue was detected by our automated monitoring and later confirmed by customer reports. Previously, the issue reproduced with a lower frequency and was below alerting threshold.

Response

Our engineering team started investigating on January 19, but initially the extent of the impact was not apparent. On January 20 at 13:18 UTC, the UiPath status page was updated and we immediately started mitigating the problem. While a fix was being developed and deployed, we took steps to mitigate the issue. By 13:25 UTC, we had partially mitigated the issue and it was completely resolved by 17:43 UTC.

Follow-Up

To prevent similar issues, we are implementing improved input validation, strengthening error handling, enhancing monitoring for earlier detection, and refining our deployment and testing processes to address additional edge cases.

Resolved: Our team has implemented a fix, we are monitoring for further errors.

Monitoring: Our team has implemented a fix, we are monitoring for further errors.

Identified: We are continuing to work on a fix for this issue, the fix is in the process of rolling out.

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

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

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

Investigating: Intermittent 503 response code when performing Classification or Extraction. We are investigating

Resolved: Issue is resolved.

Investigating: Some customers will see issues performing IXP extraction from DU-framework in East Us region

Resolved: This incident has been resolved. Thank you for your patience.

Identified: The issue is now also affecting the US. A previous fix didn’t fully resolve the problem, so our engineering team is rolling back a recent change while investigating a full resolution. Thank you for your patience.

Monitoring: The fix has been deployed. We’re monitoring the system and seeing signs of recovery. Thanks for your patience.

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

Investigating: Investigating degraded Document Understanding predictions in Europe. Slower responses and higher failure rates observed.

Resolved: Issue is now resolved

Monitoring: We have deployed a fix and are monitoring.

Identified: We are continuing to work on a fix for this issue. Thank you for your patience.

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

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

Investigating: We are currently investigating this issue.

Resolved: We are continuing to monitor for any further issues. Thank you for yourpatience.

Monitoring: We are continuing to monitor for any further issues. Thank you for yourpatience.

Monitoring: We are continuing to monitor for any further issues. Thank you for your continued patience.

Monitoring: We are continuing to monitor for any further issues. Thank you for your patience.

Monitoring: We are continuing to monitor for any further issues.

Monitoring: A fix has been implemented and we are monitoring the results.

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

Identified: Automated background prediction services impacted in design time in US and Europe for IXP Unstructured & Complex Documents. Users can still upload documents and manually request predictions. Thank you for your patience.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved; the issue was caused by an internal service communication problem and the impact was limited to Action Center, Agents, Apps, Orchestrator, Solutions Management, and Studio Web. Thank you for your patience.

Monitoring: A fix has been implemented and we are monitoring the results.

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

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved; the issue was caused by an internal service communication problem and the impact was limited to Action Center, Agents, Apps, Orchestrator, Solutions Management, and Studio Web. Thank you for your patience.

Monitoring: A fix has been implemented and we are monitoring the results.

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

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.

Resolved: This incident has been resolved; the issue was caused by an internal service communication problem and the impact was limited to Action Center, Agents, Apps, Orchestrator, Solutions Management, and Studio Web. Thank you for your patience.

Monitoring: A fix has been implemented and we are monitoring the results.

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

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating this issue.