UiPath Status

Postmortem: ## 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.

Resolved: The issue is now resolved and no new errors since last 30 minutes. Coded Apps across all geo's are loading as expected.

Monitoring: The issue with the cloud service provider has recovered. We are continuing to monitor the service for any further issues.

Investigating: 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.

Postmortem: ## Customer impact

Between July 20, 2026 at 4:28 pm UTC and 7:32 pm UTC, a subset of customers experienced degraded Orchestrator Jobs performance in the U.S. region, with delays in job processing during that window.

Root cause

The incident was triggered by a routine product deployment to Orchestrator that included a schema change to an existing column on a core Orchestrator database table. Specifically, a change to the column's size. The large size of the Jobs table made this schema change operation significantly more resource-intensive and longer-running than anticipated, causing it to still be in progress once normal U.S. traffic picked up, an overlap that had not been anticipated. The combination of the ongoing schema change and concurrent production traffic generated increased database load, which caused latency and delays in job processing. As the change rolled out, the affected databases were impacted progressively rather than all at once.

The script had been reviewed and tested prior to rollout. However, the resource impact observed here did not reproduce during pre-deployment testing, as it depended on production-scale traffic conditions that were not present in the test environment.

Detection

Our automated monitoring identified the issue at 4:28 pm UTC on July 20, 2026, and the alert was acknowledged immediately. As the extent of the customer impact became clear, the incident was formally declared customer-impacting at 7:12 pm UTC.

Response

As the schema change progressed, the resulting database load increased progressively across the affected databases rather than all at once. The team mitigated the issue in two stages: a first round of database capacity increases around 5:00–5:30 pm UTC addressed the databases affected at that point, and as impact continued to build on the remaining databases, a second round of capacity increases around 7:00–7:30 pm UTC was applied, fully resolving the elevated load.

At 7:19 pm UTC, a public status update confirmed the cause had been identified: degraded performance affecting Orchestrator Jobs in the U.S. region, with users potentially seeing delays when executing jobs. Mitigation actions were already under way at that point.

The database schema change script was stopped, and database capacity was increased as a mitigation measure. During the response call, the engineering team monitored database utilization, which was observed dropping and then stabilizing. By the end of the call, all databases were underutilized and the issue was confirmed mitigated. At 7:32 pm UTC, the incident was marked resolved, and the public status page confirmed that Orchestrator performance had returned to expected levels

Follow-up

Several actions will be taken following this incident:

• We are building a safer, more automated process for running database schema changes that reliably schedules resource-intensive changes outside of peak traffic hours, rather than relying on manual timing.
• We are extending our monitoring systems to more accurately include customer-visible slowdowns in parts of the platform that rely on Orchestrator (Maestro, Agents).

Resolved: The issue has been resolved and Orchestratorperformance has returned to expected levels after degraded performance impacted jobs in US. Impact: No ongoing user impact.

Identified: The issue causing degraded performance impacting Jobs for Orchestrator in US has been identified, and corrective actions are underway. Impact: Users may continue to see delays when executing jobs. We will provide further updates as mitigation progresses.

Identified: We have identified the cause of the degraded performance impacting [impacted functionality / user symptom] for [Service] in [Region] and are working on mitigation. Impact: Users may experience [describe ongoing impact, if any]. Additional updates will be provided as we move toward resolution.

Resolved: Our mitigation efforts are completed and impacted services are fully stable now. We will post a detailed summary of incident soon.

Identified: We are continuing mitigation activities and the impacted regions are showing improvements.

Identified: We are continuing mitigation activities, the delayed US region is showing improvements.

Identified: We are continuing mitigation activities, the delayed US region is showing improvements.

Identified: We are continuing mitigation activities, the delayed US region is showing improvements.

Identified: We are continuing mitigation activities, the delayed US region is showing improvements.

Identified: We are continuing mitigation activities, the delayed US region is showing improvements.

Identified: We are continuing mitigation activities, the delayed US region is showing improvements.

Identified: We are continuing mitigation activities, the delayed US region is showing improvements.

Identified: We are continuing mitigation activities, the delayed US region is showing improvements.

Identified: We have identified impact in the US Delayed environment as well, and are continuing mitigation activities.

Identified: We have identified and applied new mitigation and recovery is estimated to take several more hours.

Identified: We have identified and applied new mitigation and recovery is estimated to take several more hours.

Identified: We have identified and applied new mitigation and recovery is estimated to take several more hours.

Investigating: We are still investigating the reports of delayed ingestion of robot logs. Our teams are working to identify the cause and will share more details as the investigation progresses.

Monitoring: Mitigation has been applied. We are monitoring closely to ensure stability.

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.

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.

Postmortem: ## 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.

Resolved: The issue is now resolved and no new errors since last 30 minutes. Coded Apps across all geo's are loading as expected.

Monitoring: The issue with the cloud service provider has recovered. We are continuing to monitor the service for any further issues.

Investigating: 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.

Postmortem: ## 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.

Resolved: The issue is now resolved and no new errors since last 30 minutes. Coded Apps across all geo's are loading as expected.

Monitoring: The issue with the cloud service provider has recovered. We are continuing to monitor the service for any further issues.

Investigating: 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.

Postmortem: ## 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.

Resolved: The issue is now resolved and no new errors since last 30 minutes. Coded Apps across all geo's are loading as expected.

Monitoring: The issue with the cloud service provider has recovered. We are continuing to monitor the service for any further issues.

Investigating: 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.

Resolved: This incident has been resolved. Job execution performance for Serverless Robots in India has returned to normal levels and remained stable through the monitoring period.

Monitoring: A fix has been applied and we are now monitoring the results. Job execution performance for Serverless Robots in India has returned to normal levels. We will continue to monitor the situation

Identified: We have identified the issue and our teams has started working on applying the fix.

Investigating: We are Investigating the cause of the degraded performance impacting Job Execution for Serverless Robots in India. Impact: Users may experience slow job execution. Additional updates will be provided as we move toward resolution.

Resolved: We have identified and resolved the cause of the degraded performance affecting Agent Evaluations in the India region. Impact: Users may have experienced timeouts when running evaluations. This incident is now resolved. No further updates will be provided.

Monitoring: We have identified the cause of the degraded performance impacting Evalutions for Agents in India region and we have applied a mitigation and are monitoring the situation.

Impact: Users may experience timeouts when running evaluations.

Additional updates will be provided We have identified the cause of the degraded performance affecting evaluations for agents in the India region. We have implemented mitigation measures and are monitoring the situation. Impact: Users may experience timeouts when running evaluations. We will provide additional updates as we work toward a resolution.as we move toward resolution.

Postmortem: ## 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.

Resolved: The issue is now resolved and no new errors since last 30 minutes. Coded Apps across all geo's are loading as expected.

Monitoring: The issue with the cloud service provider has recovered. We are continuing to monitor the service for any further issues.

Investigating: 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.

Postmortem: ## 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.

Resolved: The issue is now resolved and no new errors since last 30 minutes. Coded Apps across all geo's are loading as expected.

Monitoring: The issue with the cloud service provider has recovered. We are continuing to monitor the service for any further issues.

Investigating: 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.