Customer Impact

On October 1, 2026, the UiPath Insights service in the UAE region was unavailable. From approximately 23:40 UTC on October 1 to 00:39 UTC on October 2, users could not load Insights dashboards: requests failed with an error after about 10 seconds. Requests to provision Insights for new tenants in the region also failed. The disruption lasted approximately 59 minutes. Other UiPath services in the UAE region, and Insights in all other regions, were not affected. No customer data was lost.

Root Cause

The outage was caused by a configuration change that shipped in a scheduled Insights release. The change raised the minimum TLS (Transport Layer Security) version on the Insights application endpoints in the UAE region from TLS 1.2 to TLS 1.3, as part of a security hardening effort.

The UiPath gateway that routes customer traffic to Insights connects to these endpoints over TLS 1.2. Once the endpoints stopped accepting TLS 1.2, the gateway could no longer open a secure connection to them. Customer requests timed out and returned errors, even though the Insights application itself stayed healthy. The change applied only to the UAE region, which is why no other region was affected.

Detection

The issue was detected by UiPath's automated synthetic monitoring, which continuously tests Insights availability from multiple locations. The first failed health check was recorded at 23:40 UTC. Automated alerts fired within minutes, and the on-call engineering team started investigating.

Response

The engineering team confirmed that the outage affected only Insights in the UAE region. The application was running normally, but no customer traffic was reaching it. The team traced the failure to the secure-connection step between the gateway and Insights, and linked it to the TLS setting applied by the release.

At approximately 00:38 UTC, the team restored the previous minimum TLS version (TLS 1.2) on the affected endpoints. Synthetic health checks began passing immediately, and by 00:41 UTC all Insights checks in the UAE region were healthy. The team kept monitoring to confirm full stability.

Follow-Up

To prevent similar incidents in the future, we are taking the following steps:

• Remove the TLS change from the release so that future deployments do not re-apply it, until the gateway supports TLS 1.3 end to end.
• Validate connection-security changes against the gateway in a pre-production environment before they are applied to production.