UiPath Status

Resolved: The issue has been successfully resolved, and the service is now fully operationa

Monitoring: Identified the issue and rolled a fix for resolution. we are actively monitoring.

Investigating: Users are unable to create Integration Service connections in US region

Investigating: We are currently investigating an issue affecting the creation of Integration Service connections. Further updates will be provided shortly.

Postmortem: ## Customer Impact

Following a deployment, some customers experienced issues where the Agent Builder frontend failed to load.

• 8 organizations encountered the issue multiple times
• 65 organizations experienced the issue exactly once

The issue was self-resolving upon clearing browser cache and refreshing the page. No further occurrences were observed after mitigation, and the status page was updated and resolved.

Root Cause

The incident was caused by browser caching of a stale remote entry file (remoteEntry.js) following a deployment.

After the deployment, the remote entry file was updated on the server, but browsers continued to serve the previously cached version. The stale cached file referenced assets that no longer existed on the server, resulting in 404 errors when the browser attempted to load them, causing the Agent Builder frontend to fail to load.

The cache was not properly invalidated upon deployment, meaning the problem only appeared immediately after a deployment and resolved itself as browser caches expired.

Detection

The issue was reported by a customer. The failed requests returned 404 status codes, which did not trigger any existing alerts on our side.

This represents a monitoring gap: 404 errors on frontend asset requests were not covered by our alerting rules, meaning the issue went undetected until a customer reported it.

Response

Upon detection:

1. The engineering team identified the root cause as stale browser caching of the remoteEntry.js file after the deployment.
2. Immediate mitigation was communicated: affected customers could resolve the issue by disabling cache and refreshing the page.
3. Deployments were paused to prevent further occurrences until a fix was merged into the release branch.
4. The status page was updated and resolved once the root cause was confirmed and mitigation verified.

Follow-Up

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

• Deployment process improvement: Ensuring that future deployments properly invalidate cached frontend assets to prevent stale file references.

Resolved: The issue has been resolved.

Identified: We are testing the fix and will share another update once the fix is ready to ship.

Identified: We are actively working on a fix to ensure the cache is properly invalidated upon deployment. We'll share another update once the fix is ready to ship.

Investigating: Agent Builder might not load for some customers. Impact is seen in multiple regions. The current workaround is to disable cache in the browser and refresh the page, while we are investigating the root cause.

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

Resolved: The issue has been resolved.

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Identified: We are actively working on a fix and taking steps to minimize the impact. We will continue to share updates as they become available.

Identified: We’ve identified the issue and are continuing to deploy mitigation. Work is ongoing, and we’re closely monitoring progress toward full resolution.

Identified: We identified the issue and are working deploying the mitigation.

Investigating: We are investigating the incident.

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

Resolved: The issue has been resolved.

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Identified: We are actively working on a fix and taking steps to minimize the impact. We will continue to share updates as they become available.

Identified: We’ve identified the issue and are continuing to deploy mitigation. Work is ongoing, and we’re closely monitoring progress toward full resolution.

Identified: We identified the issue and are working deploying the mitigation.

Investigating: We are investigating the incident.

Resolved: The issue has been successfully resolved, and the service is now fully operationa

Monitoring: Identified the issue and rolled a fix for resolution. we are actively monitoring.

Investigating: Users are unable to create Integration Service connections in US region

Investigating: We are currently investigating an issue affecting the creation of Integration Service connections. Further updates will be provided shortly.

Resolved: The issue has been successfully resolved, and the service is now fully operationa

Monitoring: Identified the issue and rolled a fix for resolution. we are actively monitoring.

Investigating: Users are unable to create Integration Service connections in US region

Investigating: We are currently investigating an issue affecting the creation of Integration Service connections. Further updates will be provided shortly.

Postmortem: ## Customer Impact

Following a deployment, some customers experienced issues where the Agent Builder frontend failed to load.

• 8 organizations encountered the issue multiple times
• 65 organizations experienced the issue exactly once

The issue was self-resolving upon clearing browser cache and refreshing the page. No further occurrences were observed after mitigation, and the status page was updated and resolved.

Root Cause

The incident was caused by browser caching of a stale remote entry file (remoteEntry.js) following a deployment.

After the deployment, the remote entry file was updated on the server, but browsers continued to serve the previously cached version. The stale cached file referenced assets that no longer existed on the server, resulting in 404 errors when the browser attempted to load them, causing the Agent Builder frontend to fail to load.

The cache was not properly invalidated upon deployment, meaning the problem only appeared immediately after a deployment and resolved itself as browser caches expired.

Detection

The issue was reported by a customer. The failed requests returned 404 status codes, which did not trigger any existing alerts on our side.

This represents a monitoring gap: 404 errors on frontend asset requests were not covered by our alerting rules, meaning the issue went undetected until a customer reported it.

Response

Upon detection:

1. The engineering team identified the root cause as stale browser caching of the remoteEntry.js file after the deployment.
2. Immediate mitigation was communicated: affected customers could resolve the issue by disabling cache and refreshing the page.
3. Deployments were paused to prevent further occurrences until a fix was merged into the release branch.
4. The status page was updated and resolved once the root cause was confirmed and mitigation verified.

Follow-Up

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

• Deployment process improvement: Ensuring that future deployments properly invalidate cached frontend assets to prevent stale file references.

Resolved: The issue has been resolved.

Identified: We are testing the fix and will share another update once the fix is ready to ship.

Identified: We are actively working on a fix to ensure the cache is properly invalidated upon deployment. We'll share another update once the fix is ready to ship.

Investigating: Agent Builder might not load for some customers. Impact is seen in multiple regions. The current workaround is to disable cache in the browser and refresh the page, while we are investigating the root cause.

Identified: Team is making progress on a fix deployment, but in the meanwhile customers can manually mitigate this issue by adding a serverless machine template to the folder.

Identified: Team is working on a fix deployment, but in the meanwhile customers can manually mitigate this issue by adding a serverless machine template to the folder.

Investigating: Uipath Agents that are newly deployed in Canada, Japan and USA will not start unless a serverless machine template is assigned to the folder.

We are working on a fix, but in the meanwhile customers can manually mitigate this issue by adding a serverless machine template to the folder.

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

Resolved: The issue has been resolved.

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Identified: We are actively working on a fix and taking steps to minimize the impact. We will continue to share updates as they become available.

Identified: We’ve identified the issue and are continuing to deploy mitigation. Work is ongoing, and we’re closely monitoring progress toward full resolution.

Identified: We identified the issue and are working deploying the mitigation.

Investigating: We are investigating the incident.

Resolved: The issue has been successfully resolved, and the service is now fully operationa

Monitoring: Identified the issue and rolled a fix for resolution. we are actively monitoring.

Investigating: Users are unable to create Integration Service connections in US region

Investigating: We are currently investigating an issue affecting the creation of Integration Service connections. Further updates will be provided shortly.

Postmortem: ## Customer Impact

Following a deployment, some customers experienced issues where the Agent Builder frontend failed to load.

• 8 organizations encountered the issue multiple times
• 65 organizations experienced the issue exactly once

The issue was self-resolving upon clearing browser cache and refreshing the page. No further occurrences were observed after mitigation, and the status page was updated and resolved.

Root Cause

The incident was caused by browser caching of a stale remote entry file (remoteEntry.js) following a deployment.

After the deployment, the remote entry file was updated on the server, but browsers continued to serve the previously cached version. The stale cached file referenced assets that no longer existed on the server, resulting in 404 errors when the browser attempted to load them, causing the Agent Builder frontend to fail to load.

The cache was not properly invalidated upon deployment, meaning the problem only appeared immediately after a deployment and resolved itself as browser caches expired.

Detection

The issue was reported by a customer. The failed requests returned 404 status codes, which did not trigger any existing alerts on our side.

This represents a monitoring gap: 404 errors on frontend asset requests were not covered by our alerting rules, meaning the issue went undetected until a customer reported it.

Response

Upon detection:

1. The engineering team identified the root cause as stale browser caching of the remoteEntry.js file after the deployment.
2. Immediate mitigation was communicated: affected customers could resolve the issue by disabling cache and refreshing the page.
3. Deployments were paused to prevent further occurrences until a fix was merged into the release branch.
4. The status page was updated and resolved once the root cause was confirmed and mitigation verified.

Follow-Up

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

• Deployment process improvement: Ensuring that future deployments properly invalidate cached frontend assets to prevent stale file references.

Resolved: The issue has been resolved.

Identified: We are testing the fix and will share another update once the fix is ready to ship.

Identified: We are actively working on a fix to ensure the cache is properly invalidated upon deployment. We'll share another update once the fix is ready to ship.

Investigating: Agent Builder might not load for some customers. Impact is seen in multiple regions. The current workaround is to disable cache in the browser and refresh the page, while we are investigating the root cause.

Identified: Team is making progress on a fix deployment, but in the meanwhile customers can manually mitigate this issue by adding a serverless machine template to the folder.

Identified: Team is working on a fix deployment, but in the meanwhile customers can manually mitigate this issue by adding a serverless machine template to the folder.

Investigating: Uipath Agents that are newly deployed in Canada, Japan and USA will not start unless a serverless machine template is assigned to the folder.

We are working on a fix, but in the meanwhile customers can manually mitigate this issue by adding a serverless machine template to the folder.

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

Resolved: The issue has been resolved.

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Identified: We are actively working on a fix and taking steps to minimize the impact. We will continue to share updates as they become available.

Identified: We’ve identified the issue and are continuing to deploy mitigation. Work is ongoing, and we’re closely monitoring progress toward full resolution.

Identified: We identified the issue and are working deploying the mitigation.

Investigating: We are investigating the incident.

Resolved: The issue has been successfully resolved, and the service is now fully operationa

Monitoring: Identified the issue and rolled a fix for resolution. we are actively monitoring.

Investigating: Users are unable to create Integration Service connections in US region

Investigating: We are currently investigating an issue affecting the creation of Integration Service connections. Further updates will be provided shortly.

Postmortem: ## Customer Impact

Following a deployment, some customers experienced issues where the Agent Builder frontend failed to load.

• 8 organizations encountered the issue multiple times
• 65 organizations experienced the issue exactly once

The issue was self-resolving upon clearing browser cache and refreshing the page. No further occurrences were observed after mitigation, and the status page was updated and resolved.

Root Cause

The incident was caused by browser caching of a stale remote entry file (remoteEntry.js) following a deployment.

After the deployment, the remote entry file was updated on the server, but browsers continued to serve the previously cached version. The stale cached file referenced assets that no longer existed on the server, resulting in 404 errors when the browser attempted to load them, causing the Agent Builder frontend to fail to load.

The cache was not properly invalidated upon deployment, meaning the problem only appeared immediately after a deployment and resolved itself as browser caches expired.

Detection

The issue was reported by a customer. The failed requests returned 404 status codes, which did not trigger any existing alerts on our side.

This represents a monitoring gap: 404 errors on frontend asset requests were not covered by our alerting rules, meaning the issue went undetected until a customer reported it.

Response

Upon detection:

1. The engineering team identified the root cause as stale browser caching of the remoteEntry.js file after the deployment.
2. Immediate mitigation was communicated: affected customers could resolve the issue by disabling cache and refreshing the page.
3. Deployments were paused to prevent further occurrences until a fix was merged into the release branch.
4. The status page was updated and resolved once the root cause was confirmed and mitigation verified.

Follow-Up

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

• Deployment process improvement: Ensuring that future deployments properly invalidate cached frontend assets to prevent stale file references.

Resolved: The issue has been resolved.

Identified: We are testing the fix and will share another update once the fix is ready to ship.

Identified: We are actively working on a fix to ensure the cache is properly invalidated upon deployment. We'll share another update once the fix is ready to ship.

Investigating: Agent Builder might not load for some customers. Impact is seen in multiple regions. The current workaround is to disable cache in the browser and refresh the page, while we are investigating the root cause.

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

Resolved: The issue has been resolved.

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Monitoring: The issue has been resolved, and we are currently monitoring the system to ensure stabilit

Identified: We are actively working on a fix and taking steps to minimize the impact. We will continue to share updates as they become available.

Identified: We’ve identified the issue and are continuing to deploy mitigation. Work is ongoing, and we’re closely monitoring progress toward full resolution.

Identified: We identified the issue and are working deploying the mitigation.

Investigating: We are investigating the incident.