UiPath experienced a notice incident on July 16, 2026 affecting Apps and Apps and 1 more component, lasting 1h 42m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 16, 2026, 05:03 PM UTC
We are currently investigating an issue affecting Coded Apps. Initial findings indicate the issue may be related to our cloud provider's services. We will provide updates as more information becomes available.
- monitoring Jul 16, 2026, 06:00 PM UTC
The issue with the cloud service provider has recovered. We are continuing to monitor the service for any further issues.
- resolved Jul 16, 2026, 06:45 PM UTC
The issue is now resolved and no new errors since last 30 minutes. Coded Apps across all geo's are loading as expected.
- postmortem Jul 23, 2026, 06:34 AM UTC
## Customer impact Between approximately **July 16, 2026 at 4:39 pm UTC and July 16, 2026 at 6:00 pm UTC**, some customers experienced issues loading their UiPath Coded Apps hosted on `*.uipath.host` domain. ## Root cause The issue was caused by a service disruption at one of our cloud infrastructure providers, which caused a component UiPath Coded Apps depends on to become temporarily unavailable. Affected users could not load their apps during the disruption. Service recovered automatically once the provider's service was restored. ## Detection The issue was detected through automated service availability alerts for UiPath Coded Apps. ## Response After detecting the alert at 4:39 pm UTC on July 16, 2026, our team identified the root cause as an external outage at our cloud infrastructure provider. We updated the public status page as investigation progressed \(investigating at 5:03 pm UTC\). Since the root cause was external to UiPath and required recovery on the provider side, our response focused on monitoring the provider's recovery and communicating clearly to affected customers. At 6:00 pm UTC on July 16, 2026, the provider's service recovered and Coded Apps were observed to be loading normally again. The public status page was updated to monitoring at that time. At 6:45 pm UTC, the incident was marked resolved after no new errors had been observed for the prior 30 minutes. The final status update confirmed that Coded Apps across all geographies were loading as expected. ## Follow-up To reduce the chance of a similar issue and to improve our resilience to provider-side disruptions, we are evaluating architectural changes to Coded Apps so that a service disruption at any single infrastructure provider does not cause the same class of failure. This includes reviewing alternative storage approaches, fallback strategies, and consistency trade-offs.