Customers will observe latency with the new data in insights in US region

Update timeline

1. identified Jun 02, 2026, 05:20 PM UTC

   We have identified the cause of the degraded performance. Impact: Users may experience latency with the new data from orchestrator in insights in US region Additional updates will be provided as we move toward resolution.

2. identified Jun 02, 2026, 05:23 PM UTC

   We have identified the cause of the degraded performance. We are working on the resolution

3. resolved Jun 02, 2026, 06:13 PM UTC

   Issue is resolved now.

4. postmortem Jul 15, 2026, 07:10 AM UTC

   ## Customer Impact Between **June 1, 2026** and **June 2, 2026 at approximately 19:23 UTC \(3:23 PM ET\)**, customers using **UiPath Insights in the U.S. region** experienced delays in the availability of new data in Insights dashboards and reports. The impact was limited to the U.S. region; all other regions continued to operate normally. During the incident, newly generated robot, job, queue, and licensing data was not reflected in Insights. Previously available dashboards, reports, and historical data remained fully accessible throughout the event. No customer data was lost, modified, or exposed. The issue delayed the processing of new data, and all delayed data was successfully backfilled after service was restored. ## Root Cause The incident was caused by the expiration of a security credential used by UiPath Insights to access cloud storage for data ingestion in the U.S. region. Although the credential had been renewed in advance, the updated credential was not successfully applied, allowing the original credential to expire. As a result, data ingestion pipelines were unable to process new data until the credential was replaced. ## Detection * The interruption was detected by automated monitoring on June 1, 2026. * Initial signals were consistent with a transient condition that typically self-recovers, which delayed identification of the underlying cause. * On June 2, after confirming the interruption was persistent, the team identified the expired credential as the cause and began remediation immediately. ## Response Following confirmation of the persistent issue, a dedicated incident response was initiated on **June 2, 2026**, and the UiPath Status Page was updated to keep customers informed. Engineering generated and applied a new credential with a valid long-term expiration, restarted the affected data ingestion pipelines, and validated that delayed data was successfully backfilled. Service was confirmed fully restored by **19:23 UTC \(3:23 pm ET\)**. ## Follow-Up ### **Completed** * Replaced the expired credential with a new long-term credential. * Restarted and validated all affected data ingestion pipelines. * Confirmed successful backfill of all delayed customer data. ### **Planned** * **Improve credential rotation validation:** Add automated verification to confirm that renewed credentials are successfully applied, have the expected expiration, and can access required storage resources before the rotation process is considered complete. * **Strengthen monitoring:** Enhance alerting to detect credential-related failures earlier and more clearly distinguish persistent failures from transient conditions.