OneTrust incident
IM-1472 - Privacy Rights Automation Dashboards Service Degradation
OneTrust experienced a minor incident on April 15, 2026, lasting 1d 13h. The incident has been resolved; the full update timeline is below.
Update timeline
- investigating Apr 15, 2026, 03:06 PM UTC
We’ve identified an issue where users may observe stale and inaccurate reporting data within Privacy Rights Automation dashboards and reports, where sync indicators suggest data is current, but the underlying records may not be refreshed correctly. This results in missing or outdated request information, inaccurate request counts, and report outputs that do not reflect the current state of requests in the platform. Impact is limited to users accessing the service through the APP- environment. We're evaluating the corrective measures required to mitigate the impact and will provide an update as soon as possible.
- identified Apr 15, 2026, 05:11 PM UTC
We have confirmed the underlying cause of the reporting issue. A significant processing backlog is preventing dashboard and report data from updating as expected, which means customers may continue to see stale, incomplete, or inaccurate reporting until the backlog has been cleared. Configuration changes are being applied to address the contributing conditions, and engineering is actively working to reduce the backlog and restore normal reporting behaviour. Based on the current processing rate, full recovery may take up to approximately 72 hours, although work is underway to improve throughput and shorten that recovery window. We will continue to provide updates as progress is made.
- investigating Apr 16, 2026, 05:30 AM UTC
Configuration changes are being applied to address the current situation, and our engineering teams are actively working to reduce the backlog and restore normal reporting behaviour. We have also scaled up our infrastructure and are implementing backend changes to help accelerate backlog clearance. Based on the improved processing rate, full recovery is now expected within approximately 24 hours, with continued efforts underway to further optimize and shorten the recovery window. We will continue to provide updates as progress is made.
- resolved Apr 17, 2026, 04:30 AM UTC
Corrective actions have been deployed, and after a period of monitoring, we've confirmed that the processing backlog has decreased to nominal levels, and the incident has been resolved. If you are still experiencing issues, please contact our support teams quoting IM -1472. Root cause analysis investigations have been initiated, and an RCA will be provided.