About This Site
Welcome to our status page. If you are looking for help, please check our documentation guides or contact us on our community forum. All products listed below have a target availability of 99.9%.
Current UiPath Status
Component Status Overview
Uptime over the past 90 days. View historical uptime.
US - Document Understanding - Partial Outage
Postmortem
Customer impact
Between August 21, 2026 at 11:05 am UTC and August 21, 2026 at 12:18 pm UTC, a subset of customers experienced failed Document Understanding operations, including document classification, extraction, and digitization. The estimated duration of the partial outage was 48 minutes. The impact was limited to customers using Document Understanding in the US region.
Root cause
The incident was caused by the Document Understanding storage database failover configuration entering a broken state during a preventive database scale-up operation. The scale-up was initiated after the database approached its storage limit. During the operation, the secondary database could not be scaled, the attempted removal from the failover configuration failed, and the database platform provider had to break the replication link. This left the failover configuration in a temporary unavailable state, causing the storage and runtime services that depend on that database to fail requests.
Detection
The incident was detected through an automated alert for the Document Understanding services, which was acknowledged on August 21, 2026 at 12:10 pm UTC.
Response
Before the customer-impacting incident was declared, the primary database scale-up was completed and support from the database platform provider was engaged for the secondary database issue. After the failover configuration became broken, we explored redirecting the service connection but could not identify a safe, immediate path to do so given the service's current configuration.
Service was restored by deleting the unhealthy secondary database and recreating the failover configuration. By August 21, 2026 at 12:37 pm UTC, the fix had been implemented and monitoring was in progress. At 1:36 pm UTC, monitoring confirmed the service was healthy, and the incident was marked resolved.
Follow up
- Request a root cause analysis from the database platform provider to determine why the secondary database could not be scaled and why the failover configuration remediation required breaking replication.
- Update database storage alerting thresholds and routing so alerts are assigned and acted on earlier, including a lower-severity warning at 75% usage and a higher-severity alert at 85% usage.