OneTrust incident

IM-1526 - Multiple Services down in UAT-HC

Major Resolved View vendor source →

OneTrust experienced a major incident on May 29, 2026, lasting 16h 52m. The incident has been resolved; the full update timeline is below.

Started
May 29, 2026, 04:58 AM UTC
Resolved
May 29, 2026, 09:50 PM UTC
Duration
16h 52m
Detected by Pingoru
May 29, 2026, 04:58 AM UTC

Update timeline

  1. investigating May 29, 2026, 04:58 AM UTC

    We are currently investigating a service disruption affecting the UAT-HC environment due to a third-party service outage. Our team is actively working with the provider to restore services as quickly as possible. We will continue to share updates as more information becomes available.

  2. investigating May 29, 2026, 08:30 AM UTC

    We’re continuing to work closely with our third-party service provider to investigate the outage and are monitoring the situation closely. Further updates will be shared as soon as more information becomes available.

  3. investigating May 29, 2026, 10:00 AM UTC

    We are continuing to investigate this issue with our third-party service provider. Based on the information available, the disruption was caused by a power event at their data center, resulting in a regional impact that is currently affecting OT services in the UAT-HC environment. Mitigation efforts are carried through to resolve this issue, and we are closely monitoring the situation. We will continue to share updates as more information becomes available.

  4. monitoring May 29, 2026, 12:00 PM UTC

    Our service provider continues to work on mitigation efforts, and we are closely monitoring the situation. Services in the UAT-HC environment remain impacted due to the ongoing outage. We will continue to share updates as more information becomes available.

  5. resolved May 29, 2026, 09:50 PM UTC

    We’ve received notice from our third-party provider stating that the outage has been mitigated. Our own monitoring has confirmed that their mitigation actions have been successful, resulting in this incident being considered as resolved. If you are still experiencing issues, please contact our support teams quoting IM-1526. Root cause analysis investigations have been initiated by our third-party, and an RCA will be provided.