We understand how important reliable access to your integrations is, and we sincerely apologize for the disruption this incident caused to your work.
Between March 23, 2026 at 10:30 am UTC and March 23, 2026 at 11:45 am UTC (approximately 75 minutes), a subset of customers in the EU region were unable to create or authenticate connections through the UiPath Integration Service™.
During this window, the vast majority of new connection requests failed, returning errors when you attempted to set up or authenticate a connection. Retrieving existing connections, running workflows, and all previously established connections continued to function normally throughout the incident. Only operations that required establishing a new connection were affected, including requests originating from UiPath Studio™ and Studio Web.
Failures began gradually around 10:15 am UTC, escalated to a near-complete disruption by 10:30 am UTC, and persisted until approximately 11:45 am UTC when the service was restored to normal operation.
A scheduled maintenance activity was performed on the data layer supporting the Integration Service in the US region at approximately 10:20 am UTC on March 23, 2026. During this maintenance, the data service used by the EU region’s Integration Service was temporarily disrupted.
A configuration mismatch caused the EU region’s Integration Service deployment to reference a data service hosted in the US region rather than the correct regional service. When the maintenance activity disrupted that US-hosted service, all attempts to establish new connections in the EU region began failing—causing the service to return errors to users.
Because the connection creation and authentication flows depend on this data service, these operations also failed. The scope of impact was limited to establishing new connections; all other Integration Service operations—including retrieving existing connections and running active workflows—remained fully functional, as they did not rely on the affected service.
Our monitoring systems detected elevated error rates on the Integration Service in the EU region at approximately 10:30 am UTC on March 23, 2026—within minutes of the disruption beginning. Our engineering team was alerted and began investigating immediately.
Further analysis revealed a consistent error pattern across all failing connection requests, correlating directly with the timing of the scheduled maintenance activity in the US region. This correlation allowed our team to quickly narrow the investigation to the cross-region configuration mismatch.
Our team correlated the onset of failures at 10:30 am UTC with the scheduled maintenance in the US region. Investigation confirmed that the EU region’s Integration Service was incorrectly configured to reference a US-hosted data service.
Our investigation verified that every failing connection request encountered the same underlying error, confirming the cross-region configuration mismatch as the root cause.
The configuration for the EU region was corrected to reference the appropriate regional service. Service recovery was observed at approximately 11:45 am UTC, with new connection creation returning to normal operation. We confirmed that only new connection creation—and the dependent authentication flows—was affected throughout the incident.
We are introducing automated pre-deployment checks to validate that each regional deployment references the correct region-specific data service. These checks will run before every deployment, preventing cross-region configuration mismatches from reaching production. In parallel, we are updating our maintenance procedures to include a mandatory step that identifies and validates all services with dependencies on the target data service before initiating any maintenance activity.
To improve our detection speed, we are adding dedicated alerts for new connection failure rates per region, with thresholds that trigger immediate notification when the error rate exceeds 5% over a five-minute window. These alerts will ensure that any similar disruption is surfaced to our engineering team within minutes.
Finally, we are conducting a comprehensive audit of all production region configurations across Integration Service deployments to identify and remediate any remaining cross-region inconsistencies. We are committed to ensuring that your experience with the Integration Service remains reliable and that the safeguards we are putting in place prevent a recurrence of this type of incident.