UiPath Status

Postmortem: ## Customer Impact

During scheduled maintenance and deployment beginning at 07:00 UTC on 2026-02-11, customers in the Singapore region began experiencing failures when creating new connections. Existing connections and all read operations remained fully functional, and no data loss occurred.

At approximately 08:15 UTC, following a corrective rollout, new connection creation functionality was fully restored.

Root Cause

As part of the DB maintenance rollout in the Singapore region, a configuration mismatch occurred. The application continued referencing legacy database connections that had been transitioned to read-only mode during maintenance. Because creating new connections requires write access, these requests failed when routed through the read-only configuration.

Detection

The issue was not detected by internal monitoring or alerting systems and was initially reported by customers. It was subsequently reproduced internally and confirmed to be isolated to the Singapore region.

Response

The issue was reported by customers, quickly reproduced internally, and confirmed to be isolated to the Singapore region. A corrective configuration update was deployed, fully restoring the new connection creation functionality.

Follow-Up

• Introduce automated minutely validation tests that create mock connections as part of the deployment and post-deployment process to proactively detect write failures.
• Improve monitoring and alerting to specifically detect and notify on write-operation failures (e.g., connection creation errors).

Resolved: The issue was caused by a configuration error introduced during database maintenance. A corrective code rollout was done, which has fully mitigated the problem.

Investigating: Due to the recent Database maintenance activity, we have started seeing connection creation failures specifically in the Singapore region. Our team is actively investigating the issue.

Resolved: The issue has been mitigated, but customers may continue to experience intermittent ingestion delays until our cloud service provider provides a full resolution.

Monitoring: This issue has been mitigated but the team is still investigating with underlying cloud service provider and will look to provide more information once available.

Identified: Our investigation shows that the issue is related to our cloud service provider. We have escalated this with them and are actively monitoring progress, the resolution may take some time. We will share updates as soon as we have more definitive information

Investigating: We are investigating an issue causing delayed ingestion of Queue Item data in Insights for customers in the US region.