OneTrust incident

IM-1417 - UAT & UAT-DE Consent & Cookie Aggregation Failure

Notice Resolved View vendor source →

OneTrust experienced a notice incident on February 25, 2026, lasting 5d 17h. The incident has been resolved; the full update timeline is below.

Started
Feb 25, 2026, 02:51 PM UTC
Resolved
Mar 03, 2026, 08:00 AM UTC
Duration
5d 17h
Detected by Pingoru
Feb 25, 2026, 02:51 PM UTC

Update timeline

  1. investigating Feb 25, 2026, 02:51 PM UTC

    We're investigating an issue where the daily and monthly Dashboards for Consent and Cookies are not updating as expected. Users may notice that no new data is appearing since Monday 22nd February. The issue was identified following a recent platform deployment. Our engineering team has made a configuration change to the deployment to prevent other environments from being impacted. Work is ongoing to implement a fix for the affected environment. We will provide further updates as progress continues.

  2. identified Feb 26, 2026, 08:54 AM UTC

    We have identified the root cause of the issue impacting the Cookie Consent Dashboards, where data has not been updating since Monday, 22 February. Our engineering team is actively working on implementing a fix for the affected environment. The corrective changes are currently in progress. We will provide confirmed deployment timelines once the fix has been finalised and approved for release. Further updates will follow as progress continues.

  3. identified Feb 26, 2026, 09:59 PM UTC

    Our engineering team has successfully implemented corrective changes in the affected lower‑level environments. Validation and monitoring activities are ongoing to confirm expected behavior. Confirmed deployment timelines will be shared once the fix has been fully validated and approved for release. Further updates will follow as progress continues.

  4. monitoring Mar 03, 2026, 06:00 AM UTC

    We've finished implementing the fix within the affected environments . We're monitoring the affected environment to confirm that our actions have successfully resolved the issue. We'll provide an update on confirmation of this.

  5. resolved Mar 03, 2026, 08:00 AM UTC

    Corrective actions have been deployed, and after a period of monitoring, we've confirmed resolution of this incident. If you are still experiencing issues, please contact our support teams quoting IM -1417. Root cause analysis investigations have been initiated and an RCA will be provided.