Multiple Regions - Multiple Services - Agent runtime errors

Update timeline

1. investigating Apr 23, 2026, 03:24 PM UTC

   We are investigating reports of an outage impacting Agents in US and Europe Regions. Impact: Users may be unable to start Agents. Next update: Our teams are working to understand the cause and scope and will share updates as available.

2. investigating Apr 23, 2026, 04:17 PM UTC

   We are continuing to investigate the cause of the issues, we will provide an update as soon as we begin working on a mitigation

3. investigating Apr 23, 2026, 04:44 PM UTC

   Further investigation has revealed that this issue is affecting all regions, so customers may experience Agents failing to start across all UiPath Automation Cloud regions. We are continuing to investigate the root cause of the issue and will be working to mitigate it promptly.

4. identified Apr 23, 2026, 05:21 PM UTC

   We have identified a defect in a recent deployment, which is causing the issue. We are preparing to roll back the change, which will return Agents to full functionality for all customers.

5. identified Apr 23, 2026, 06:18 PM UTC

   We are validating the reversion of the improper configuration in a lower environment, and will begin deploying it to production regions shortly

6. identified Apr 23, 2026, 07:16 PM UTC

   We are still working on a mitigation for this issue

7. identified Apr 23, 2026, 08:14 PM UTC

   We have a mitigation and are validating it prior to deploying it to production

8. identified Apr 23, 2026, 09:06 PM UTC

   We are continuing to develop and validate a mitigation for this issue

9. identified Apr 23, 2026, 09:29 PM UTC

   We are still working on a mitigation. As a temporary workaround: The issue appears to be related to the IP Restriction security setting, as internal testing has shown that disabling it mitigates the issue. We understand that disabling this feature may not be possible for all customers, but we wish to provide it as an option. In order to apply this mitigation: navigate to Admin -> Security Settings -> IP Restriction

10. identified Apr 23, 2026, 09:54 PM UTC

    We have identified a mitigation and validated it in a lower environment. We are rolling out the mitigation to all affected regions.

11. monitoring Apr 23, 2026, 10:49 PM UTC

    The mitigation has been rolled out, and we are validating that it has resolved the issue

12. resolved Apr 23, 2026, 11:36 PM UTC

    The issue has been resolved