UiPath Status

Resolved: The fix has been successfully deployed across all regions, and we have validated that the issue is resolved. The service is operating as expected.

Identified: The fix is currently being applied. We will provide another update shortly once the deployment has been completed across all affected regions.

Identified: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround. Additional updates will be provided as we move toward resolution.

Monitoring: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround.Additional updates will be provided as we move toward resolution.

Identified: The issue has been identified, and the team is actively working on deploying a fix. We expect the deployment to begin in the coming hours.

Resolved: The issue has been resolved and logs are populating as expected.

Monitoring: Logs are now populating as expected in real time and we will continue monitoring the application.

Identified: We identified that robot logs ingestion was delayed. Robot logs are catching up to live data and we are monitoring recovery.

Investigating: We are investigating reports of missing robot logs in the US region. Our teams are working to identify the cause and will share more details as the investigation progresses.

Resolved: The fix has been successfully deployed across all regions, and we have validated that the issue is resolved. The service is operating as expected.

Identified: The fix is currently being applied. We will provide another update shortly once the deployment has been completed across all affected regions.

Identified: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround. Additional updates will be provided as we move toward resolution.

Monitoring: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround.Additional updates will be provided as we move toward resolution.

Identified: The issue has been identified, and the team is actively working on deploying a fix. We expect the deployment to begin in the coming hours.

Resolved: The issue has been mitigated, and the service is currently operational. We will continue to closely monitor the service health and take further action if needed.

Monitoring: The issue has been mitigated, and the service is currently operational. We will continue to closely monitor the service health and take further action if needed.

Identified: We have identified the issue and implemented the necessary fix

Investigating: We are currently investigation the issue.

Resolved: The fix has been successfully deployed across all regions, and we have validated that the issue is resolved. The service is operating as expected.

Identified: The fix is currently being applied. We will provide another update shortly once the deployment has been completed across all affected regions.

Identified: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround. Additional updates will be provided as we move toward resolution.

Monitoring: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround.Additional updates will be provided as we move toward resolution.

Identified: The issue has been identified, and the team is actively working on deploying a fix. We expect the deployment to begin in the coming hours.

Resolved: The issue has been resolved, and Solution Deployment in Studio Web is operating as expected in the Japan region. No further impact has been observed.

Monitoring: The fix has been successfully deployed in the Japan region, and the issue has been mitigated. We are closely monitoring the service to ensure Solution Deployment continues to operate as expected and will provide further updates as needed.

Identified: We have identified an issue affecting the Solution Deployment feature in Studio Web in the Japan region, where solution deployments may fail. A fix has been prepared and will be rolled out shortly. We will provide further updates as more information becomes available.

Resolved: The fix has been successfully deployed across all regions, and we have validated that the issue is resolved. The service is operating as expected.

Identified: The fix is currently being applied. We will provide another update shortly once the deployment has been completed across all affected regions.

Identified: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround. Additional updates will be provided as we move toward resolution.

Monitoring: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround.Additional updates will be provided as we move toward resolution.

Identified: The issue has been identified, and the team is actively working on deploying a fix. We expect the deployment to begin in the coming hours.

Resolved: The fix has been successfully deployed across all regions, and we have validated that the issue is resolved. The service is operating as expected.

Identified: The fix is currently being applied. We will provide another update shortly once the deployment has been completed across all affected regions.

Identified: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround. Additional updates will be provided as we move toward resolution.

Monitoring: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround.Additional updates will be provided as we move toward resolution.

Identified: The issue has been identified, and the team is actively working on deploying a fix. We expect the deployment to begin in the coming hours.

Postmortem: ## Customer impact

On August 25, 2026, Extended OCR requests in the Document Understanding service failed with 500 status code in the Singapore region for approximately 33 minutes, between 03:08 and 03:41 UTC. The cause was a Microsoft regional service disruption in Singapore. All other Document Understanding functionality was unaffected, and no other region was impacted.

Root cause

The failure was attributed to a regional Microsoft service disruption in Singapore affecting resources used by the Extended OCR capability. No changes had been made on our side, and Microsoft subsequently updated their own status page to reflect a Singapore regional issue. A formal root cause analysis has been requested from Microsoft.

Detection

An automated alert for the Document Understanding service fired on August 25, 2026 at 3:13 am UTC. The alert was acknowledged promptly, and the incident was declared customer-impacting within minutes.

Response

The on-call engineer scoped the impact to the Singapore region. Responders ruled out a recent service update as the cause, as the same update had been deployed to other regions with no comparable impact, which pointed to a regional dependency failure outside our infrastructure.

Because the failure originated in an upstream Microsoft service, no mitigating action was available or required on the UiPath side. Requests began succeeding again at 03:41 UTC as the Microsoft dependency recovered. Responders held the incident open to verify sustained recovery: ten minutes of clean traffic were confirmed at 03:51 UTC, the incident moved to Monitoring at 04:04 UTC, and it was resolved at 04:59 UTC after continued stability with no further failures.

Follow up

1. Requested a root cause analysis from Microsoft for the Singapore regional disruption affecting Extended OCR dependencies, including how recurrence can be prevented.

Resolved: The issue has been resolved, and the service is operating as expected. No further impact has been observed.

Monitoring: The issue has been mitigated, and we are closely monitoring the service to ensure it continues to operate as expected. We will provide further updates as more information becomes available.

Investigating: We are investigating an issue affecting customers using the Extended OCR functionality in the Document Understanding service in the Singapore region. Our teams are working to identify the root cause and will provide further updates as more information becomes available.

Resolved: The issue has been resolved, and the Insights service in the Singapore region is operating as expected. No further impact has been observed.

Monitoring: The issue has been mitigated, and we are closely monitoring the Insights service in the Singapore region to ensure dashboards continue to load as expected.

Investigating: We are investigating an issue affecting customers using Insights in the Singapore region, where dashboards may fail to load and display timeout errors. Our teams are working to identify the root cause and will provide further updates as more information becomes available.

Resolved: The fix has been successfully deployed across all regions, and we have validated that the issue is resolved. The service is operating as expected.

Identified: The fix is currently being applied. We will provide another update shortly once the deployment has been completed across all affected regions.

Identified: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround. Additional updates will be provided as we move toward resolution.

Monitoring: We have identified the root cause of the degraded performance and we are in the process of deploying a fix in the coming hours. It affects linked queries where the user does not have access to the original folder. API surface is unaffected. Export via CSV can be used as a workaround.Additional updates will be provided as we move toward resolution.

Identified: The issue has been identified, and the team is actively working on deploying a fix. We expect the deployment to begin in the coming hours.