Minor incident

UiPath: Multiple Region - User unable to sign-up to cloud.uipath.com

Affected: Automation Cloud, Automation Cloud, Automation Cloud, Automation Cloud, Automation Cloud, Automation Cloud, Automation Cloud, Automation Cloud, Automation Cloud, Automation Cloud, Automation Cloud, Automation Cloud, Automation Cloud

Current status of UiPath: Operational — live UiPath status

Timeline

1. Nov 2, 2026, 07:23 UTC
   investigating
   We have identified an issue affecting user sign-ups at cloud.uipath.com across multiple regions. Corrective actions are underway. Impact: Users may be unable to create/add new accounts at cloud.uipath.com. We will provide further updates as mitigation progresses.
2. Nov 2, 2026, 08:03 UTC
   monitoring
   A fix has been implemented and user sign-ups at cloud.uipath.com have been restored across the affected regions. We are monitoring to confirm continued stability. We will provide further updates as mitigation progresses.
3. Nov 2, 2026, 08:16 UTC
   resolved
   Issue is resolved now.
4. Nov 5, 2026, 21:38 UTC
   postmortem
   ## Customer impact Between 30 October 2026 08:04 UTC and 2 November 2026 07:57 UTC, new users could not create a UiPath account with a username and password, including sign-ups through UiPath Academy. Users accepting an invitation who did not yet have a UiPath account were also affected. They saw the error "Basic Authentication is disabled for this user. Sign in with single sign-on." Existing users, and sign-in with social accounts or SSO, were not affected. ## Root cause A configuration value shared by our portal and our sign-up service was updated on 28 October. On 30 October, a routine portal release started using the new value before the sign-up service had been updated with it. Because the two no longer matched, every new sign-up was rejected. ## Detection Our monitoring did not detect these failures. We became aware on 2 November through customer reports, about three days after the issue started. We recognize that this delayed our response. ## Response The incident team engaged at 06:46 UTC on 2 November and identified the mismatch. An additional configuration issue in the deployment of the sign-up service delayed the fix. The team resolved it, and the updated configuration was deployed at 07:58 UTC. Sign-ups recovered immediately, and we confirmed this with test accounts and with an affected customer. ## Follow up - Change the sign-up check so updates to this value no longer depend on which system is updated first. - Update our procedure for changing this value, to avoid future issues. - Expand our automated alerting to cover these failures.

Updates as published by UiPath (original).