Major incident

UiPath: Uipath Apps is facing outage in Delayed US region

Affected: Apps

Current status of UiPath: Partial outage — live UiPath status

Timeline

1. Aug 8, 2026, 11:54 UTC
   identified
   We have identified the cause of the outage impacting Uipath Apps is facing outage in Delayed US region and are working on a fix. Impact: Users may continue to be unable to access Uipath Apps and solutions dependent on Uipath Apps. Team is working on service restoration.
2. Aug 8, 2026, 13:01 UTC
   identified
   Team is working on service restoration. We will update the status once mitigation is completed.
3. Aug 8, 2026, 14:14 UTC
   identified
   Team has identified an issue with an underlying resource and is actively working to restore service.
4. Aug 8, 2026, 15:30 UTC
   identified
   Team has made progress to fix underlying resource issue and is actively working to restore service.
5. Aug 8, 2026, 15:32 UTC
   monitoring
   Mitigation has been applied and performance is improving for the issue. We are monitoring closely to ensure stability.
6. Aug 8, 2026, 16:01 UTC
   resolved
   The mitigation has remained stable, and performance has returned to expected levels. We have confirmed service restoration for UiPath Apps in the Delayed US region and are marking this incident as resolved.
7. Aug 12, 2026, 10:14 UTC
   postmortem
   ## Customer impact Between 11:20 am UTC and 2:54 pm UTC on August 8, 2026, a subset of customers in the Delayed US region experienced failures accessing UiPath Apps and solutions that depend on UiPath Apps. Customers may have seen UiPath Apps unavailable or intermittent request failures. The impact lasted approximately 3 hours and 34 minutes. ## Root cause The incident was caused by database connection saturation following scheduled maintenance performed by our database provider. As application services scaled up, they created additional database connections, which caused new connection attempts to fail and resulted in connection reset errors in UiPath Apps. ## Detection Automated alerts detected the issue at 11:24 am UTC on August 8, 2026. Application telemetry showed failures beginning at approximately 11:20 am UTC. ## Response At 11:00 am UTC, scheduled maintenance began automatically. At 11:20 am UTC, requests began failing. At 11:24 am UTC, automated alerts were triggered, and the team began investigating. At 12:24 pm UTC, database capacity was scaled up as a mitigation. At 1:13 pm UTC, application services were restarted to reduce saturated connection usage and refresh database connections. Connection levels remained elevated, and the database automatically scaled at 1:22 pm UTC and at 2:36 pm UTC. Following these mitigation efforts, request failures stopped at 2:54 pm UTC. At 3:33 pm UTC, the mitigation was confirmed to be stable, and performance was improving. Full recovery was confirmed at 4:01 pm UTC after performance returned to expected levels. ## Follow up 1. Obtain and review the database provider's root cause analysis explaining what caused the connection issue following their maintenance activity. 2. Implement an application-side limit on database connection creation to prevent connection saturation. 3. We are reviewing the automatic scaling behavior that amplified connection volume during the incident and address any contributing factors.

Updates as published by UiPath (original).