Resolved after 25 minutes, affecting Orchestrator, on October 15, 2026.
## Customer impact Between approximately October 15, 2026 at 11:20 pm UTC and approximately October 15, 2026 at 11:45 pm UTC, some customers in the US East region experienced delays in robot log ingestion in UiPath Orchestrator. Robot logs were not up to date during the affected period. The impact lasted approximately 20 minutes. ## Root cause During the incident, 2 of the 13 service instances handling robot log ingestion were observed failing to connect to the event ingestion service. Only requests to the event ingestion service were failing, and only on those two instances. This caused some robot log ingestion requests to not complete successfully, resulting in delayed log data for affected customers. The root cause of why only those two instances lost connectivity to the event ingestion service was not determined during the incident. The team committed to a post-incident review of logs from the affected instances to identify the underlying cause. We believe it to be an unreported infrastructure issue from our cloud provider. ## Detection The issue was detected through an automated alert at approximately 11:33 pm UTC on October 15, 2026, and confirmed through telemetry showing exceptions from the two affected service instances. ## Response After detection, telemetry confirmed that only two service instances were generating exceptions. Responders removed those two unhealthy instances from service, and replacement instances started automatically. Within approximately 20 minutes of the first alert — by approximately 11:53 pm UTC — telemetry indicated recovery and synthetic monitoring checks were passing. A broader restart of all service instances was considered but not performed, as the team determined it should not proceed without first understanding the root cause. ## Follow up 1. A post-incident review of logs from the affected service instances revealed the issue was infrastructure related, and we are following up with out cloud infrastructure provider for more details. 2. An update will be posted if the investigation yields further findings.
Affected components
Update timeline
- resolved Oct 15, 2026, 12:03 PM UTC
Some customers in the US region experienced delays in robot log ingestion, with increased activity observed between approximately 11:20 and 11:45 UTC. The issue has been resolved, and log ingestion has returned to normal. Thank you for your patience.
- postmortem Oct 22, 2026, 10:13 AM UTC
## Customer impact Between approximately October 15, 2026 at 11:20 pm UTC and approximately October 15, 2026 at 11:45 pm UTC, some customers in the US East region experienced delays in robot log ingestion in UiPath Orchestrator. Robot logs were not up to date during the affected period. The impact lasted approximately 20 minutes. ## Root cause During the incident, 2 of the 13 service instances handling robot log ingestion were observed failing to connect to the event ingestion service. Only requests to the event ingestion service were failing, and only on those two instances. This caused some robot log ingestion requests to not complete successfully, resulting in delayed log data for affected customers. The root cause of why only those two instances lost connectivity to the event ingestion service was not determined during the incident. The team committed to a post-incident review of logs from the affected instances to identify the underlying cause. We believe it to be an unreported infrastructure issue from our cloud provider. ## Detection The issue was detected through an automated alert at approximately 11:33 pm UTC on October 15, 2026, and confirmed through telemetry showing exceptions from the two affected service instances. ## Response After detection, telemetry confirmed that only two service instances were generating exceptions. Responders removed those two unhealthy instances from service, and replacement instances started automatically. Within approximately 20 minutes of the first alert — by approximately 11:53 pm UTC — telemetry indicated recovery and synthetic monitoring checks were passing. A broader restart of all service instances was considered but not performed, as the team determined it should not proceed without first understanding the root cause. ## Follow up 1. A post-incident review of logs from the affected service instances revealed the issue was infrastructure related, and we are following up with out cloud infrastructure provider for more details. 2. An update will be posted if the investigation yields further findings.
Your product runs on more than UiPath
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services