Customer Impact

Between June 11, 2026 at 2:23 pm UTC and June 12, 2026 at 6:15 am UTC, customers in the Australia region were unable to create, authenticate, or delete connections through the UiPath Integration Service. During this window, new connection requests failed with an error when attempting to set up, authenticate, or remove a connection.

Retrieving existing connections, running workflows, and all previously established connections continued to function normally throughout the incident. Only operations that required establishing, authenticating, or deleting a connection were affected, including requests originating from UiPath Studio Web.

Service was restored at approximately 6:15 am UTC on June 12, 2026 once the prior version of the service was redeployed.

Root Cause

A routine deployment to the Integration Service in the Australia region on June 11, 2026 triggered two pre-existing issues that had not previously been encountered together. As a result, the deployment did not complete as expected, causing connection creation, authentication, and deletion requests to fail. Read operations and existing connections were not affected.

Detection

Our monitoring systems detected an elevated error rate on the Integration Service in the Australia region shortly after the disruption began. Around the same time, we received customer reports that connection creation was failing, which corroborated the alert. Our on-call engineering team began investigating.

Response

Our team correlated the onset of failures with the deployment that had completed earlier and confirmed that the deployment had not completed as expected.

We decided to roll the service back to the previously stable version. The rollback was performed on June 12, 2026 at approximately 5:48 am UTC and completed cleanly within minutes. New connection creation, authentication, and deletion operations returned to normal at approximately 6:15 am UTC.

Following the rollback, our team resolved the underlying issue that had prevented the deployment from completing, to ensure future deployments would not be affected.

Follow-Up

We are making the following changes to prevent this class of incident from recurring:

• We have updated our release process to ensure no new version goes live until all required background steps have been fully completed.
• Our deployment tooling now automatically detects and resolves internal blockers that could prevent future deployments from completing successfully.
• We are auditing configurations across all regions to identify and address similar risks.
• We have improved alert routing across all regions, including overnight hours, to ensure faster detection.
• We have added deeper monitoring to reduce detection and response time for future incidents.