Multiple Regions - Cloud Robots- VM - Creation/Editing of VPN Gateway in UiPath Cloud Administration is currently failing. Existing VPN Gateways are not impacted.

Customer Impact

Between March 18, 2026 at 7:54 pm UTC and March 23, 2026 at 10:10 pm UTC, a subset of customers were unable to create or edit VPN Gateways within the UiPath Automation Cloud Administration portal. Attempts to perform these actions returned errors, preventing any configuration changes to VPN Gateways. Existing VPN Gateways continued to function normally throughout, while create and edit operations were affected.

This issue impacted customers across all commercial cloud regions. Our regulated (GXP) environment was confirmed unaffected at any point during the incident.

Root Cause

A recent update to the VPN Gateway management service introduced a change in the data structures used for creation and editing operations. There was a deployment misalignment between front-end services and back-end services, and as a result, any attempt to create or edit a VPN Gateway failed with an error, while existing VPN Gateways continued to operate normally. Recovery required deploying updated back-end services to all regions.

Detection

The incident was detected on March 23, 2026 at 3:05 pm UTC, and within minutes of onset, our engineering team assembled via a dedicated incident bridge to begin an investigation. The incident was formally declared as a critical, customer-impacting event at 3:21 pm UTC, and a public impact statement was posted to our status page by 3:28 pm UTC.

Response

Upon detection, our engineering team convened immediately to investigate the root cause. Initial analysis confirmed that VPN Gateway creation and editing were consistently failing across all commercial cloud regions, while existing connections remained operational. The team reviewed recent changes to the VPN Gateway management service and identified the front-end changes as the likely cause. A proposed fix was prepared by 3:09 pm UTC, and a corrective build was initiated by 4:04 pm UTC. The fix rollout began at 5:28 pm UTC. However, by 7:15 pm UTC, the team determined that this initial fix did not resolve the issue as expected. The team immediately pivoted to an alternative approach, estimating approximately one hour to build and validate the new solution. A status page update was posted at 7:19 pm UTC to inform customers that the root cause had been identified and a fix remained in progress. The alternative fix was validated in the India region at approximately 8:41 pm UTC and confirmed to be effective. Rollout to all remaining regions began at 9:02 pm UTC and proceeded in a controlled manner. By 10:10 pm UTC, the corrected version was deployed globally, and all affected VPN Gateway creation and editing functionality was fully restored. The incident was formally marked as mitigated at 10:20 pm UTC. Status page updates were posted at key milestones throughout the incident to keep customers informed, and we are taking steps to improve our communication cadence during extended incidents (see Follow-Up below).

Follow-Up

To prevent similar incidents in the future, we are implementing several targeted improvements to address the underlying issue of unsynchronized changes between frontend and backend components:

1. We are enforcing feature flags into our release process for the VPN Gateway management service, allowing frontend and backend validation changes to be deployed in a coordinated manner and enabled only when both components are fully aligned, while also ensuring these changes are thoroughly tested against a comprehensive set of configuration scenarios before reaching production.
2. We are introducing new integration tests that ensure frontend and backend changes are validated together before release.
3. We are enhancing our monitoring to include dedicated alerts for failed configuration operations, enabling faster detection of issues that may arise from mismatches between client-side and server-side validation.