Is UiPath Down?

This issue has been resolved. Some users were unable to publish projects from Studio Web. The fix is fully deployed and publishing is working normally again. We apologize for the inconvenience. --- [2026-11-09T17:03:07.889Z] (identified) We have identified the cause of the issue preventing some users from publishing projects from Studio Web, and we are rolling out a fix. Publishing may keep failing until the fix is fully deployed. --- [2026-11-09T16:45:06.070Z] (investigating) We are investigating an issue where some users can't publish projects from Studio Web. Other actions in Studio Web don't appear to be affected. The issue started at about 16:30 UTC on November 9, 2026, and our engineering teams are working to find the cause.

The issue affecting Google Sheets and Google Docs connections in Integration Service across multiple regions has been fully resolved, and all affected functionality is operating normally. --- [2026-11-09T12:44:26.121Z] (identified) A fix is being rolled out for the authentication failures affecting Google Sheets and Google Docs connections in Integration Service across multiple regions. --- [2026-11-09T11:44:07.893Z] (identified) We have identified the cause of the issue impacting Google Sheets and Google Docs connections failing in Integration Service for Multi-region and are working on mitigation. Impact: Users may experience Authentication failures for Google docs and sheets. Additional updates will be provided as we move toward resolution.

**Customer impact** On 26 October 2026, from 19:08 UTC, some users in the Automation Hub Canada region could not sign in, and some Automation Hub Open API calls failed with a "Database Connection Error". Service was fully restored at 00:24 UTC on 27 October. Other regions were not affected. Your Automation Hub data was not affected. Failed requests were rejected before they reached any tenant's data, and no data was lost or changed. **Root cause** UiPath was responding to a security event in its internal corporate environment. As part of that response, access for internal service accounts was reviewed and removed as a precaution. At 15:39 UTC, the service account that Automation Hub uses to read its tenant database credentials lost access to the store that holds them. Automation Hub keeps a cached copy of each tenant's credential for up to 14 days, so service continued normally at first. From 19:08 UTC, tenants in Canada whose cached copy had expired could no longer connect to their database. This is the "Database Connection Error" that some customers saw. Tenants whose cached copy was still valid were not affected. Our investigation found no evidence that the unauthorized party accessed Automation Hub or customer data. The outage was caused by our precautionary actions, not by the security event itself. **Detection** Our engineers saw the failures on our availability monitoring at 19:23 UTC, 15 minutes after they began in Canada, and identified the cause at 19:34 UTC. **Response** - 19:47 UTC: we escalated to the team running the security response. - 20:21 UTC: as a precaution, it was decided to replace Automation Hub's credential before restoring its access. - 23:11 UTC: the new credential was created. - 00:24 UTC on 27 October: access was restored, and Canada recovered with no restart needed. **Follow up** - Build tooling to identify all the production services that use a service account, before its access is changed. - Alert our engineers as soon as Automation Hub loses access to its credential store, rather than when failures start after cached credentials expire. - Prepare and pre-approve the steps to replace Automation Hub's production credentials, so access can be restored faster during a security response. --- [2026-11-05T17:09:52.304Z] (resolved) Due to an expired credential configuration, some customers were unable to access Automation Hub in the Canada region on 2026-10-26. The credential was rotated shortly after the failures were detected, and all logins were succeeding again after 2026-10-27:01:00:00z.

We will be updating the IP addresses used by Automation Cloud in the Canada region on Nov 11, 2026, from 10:00 AM to 1:00 PM UTC, as part of an infrastructure update. These IP ranges were shared in our previous notifications, which asked customers to allow them by September 16, 2026. The ranges are listed in <a href="https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/configuring-the-firewall-for-cloud">Configuring the firewall for Automation Cloud</a>. Action required: If you have already allowed these IP ranges, no action is needed. Otherwise, please add them to your firewall configuration before the maintenance window to avoid disruptions. Expected impact: Some requests may experience brief, intermittent failures during the maintenance window. Contact our support team if you need assistance.

We will be updating the IP addresses used by Automation Cloud in the Canada region on 11/11/2026 , 10:00 AM UTC- 1:00 PM UTC, as part of an infrastructure update. These IP ranges were shared in our previous notifications and are listed on Configuring the firewall for Automation Cloud (https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/configuring-the-firewall-for-cloud), which asked customers to allow them by September 16, 2026. If you have already allowed these IP ranges, no action is needed. Otherwise, please add them to your firewall configuration before the maintenance window to avoid disruptions. Some requests may see brief intermittent failures during the window. Contact our support team if you need assistance. --- [2026-11-04T11:57:54.944Z] (scheduled) We will be updating the IP addresses used by Automation Cloud in the Canada region on 11/11/2026 , 10:00 AM UTC- 1:00 PM UTC, as part of an infrastructure update. These IP ranges were shared in our previous notifications and are listed on Configuring the firewall for Automation Cloud (https://docs.uipath.com/automation-cloud/automation-cloud/latest/admin-guide/configuring-the-firewall-for-cloud), which asked customers to allow them by September 16, 2026. If you have already allowed these IP ranges, no action is needed. Otherwise, please add them to your firewall configuration before the maintenance window to avoid disruptions. Some requests may see brief intermittent failures during the window. Contact our support team if you need assistance.