UiPath experienced a critical incident on May 28, 2026 affecting IXP, lasting 16m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 28, 2026, 03:08 PM UTC
We are investigating an issue impacting IXP and Communication Mining caused by a database outage. Our team is actively working to restore service and will provide updates as they become available.
- monitoring May 28, 2026, 03:20 PM UTC
The database issue impacting IXP and Communication Mining has been resolved, and services are recovering normally. Our team is monitoring the systems closely to ensure continued stability.
- resolved May 28, 2026, 03:25 PM UTC
The issue has been fully resolved, and all systems are operating normally.
- postmortem Jun 05, 2026, 03:37 PM UTC
## Customer impact Between May 28, 2026 at 2:48 pm UTC and May 28, 2026 at 3:25 pm UTC, a database outage impacted the IXP and Communications Mining services. Affected customers may have experienced errors, degraded availability, or inability to use features that depend on those services. The impact was limited to a subset of customers in the U.S. region. The total incident duration was 37 minutes. ## Root cause The root cause was an outage of the database used by IXP. IXP services depend on the affected database and so they were unable to operate normally whilst it was unavailable. The relevant database servers had run out of storage space due to organic growth requiring a manual scale-up of the storage volumes. ## Detection The issue was detected through an automated alert at 2:48 pm UTC on May 28, 2026. The alert was triggered and acknowledged within seconds. A public status update was posted at 3:08 pm UTC confirming that our engineering team was investigating a database outage impacting the affected services. ## Response At 2:48 pm UTC, the alert was acknowledged and our engineering team began coordinating the response. At 3:08 pm UTC, the public status page was updated to indicate that we were investigating an issue impacting IXP and Communications Mining services caused by a database outage. By 3:20 pm UTC, the database issue had been resolved by scaling up storage, and services were recovering normally. The incident was marked mitigated at 3:20 pm UTC while our team monitored the affected systems for stability. At 3:25 pm UTC, the incident was marked resolved and the public status page was updated to confirm that all systems were operating normally. ## Follow up 1. Alerts that would have given early warning of database storage filling up had not yet been implemented in the relevant environment. They are now being progressed urgently.