OneTrust experienced a major incident on March 17, 2026, lasting 17m. The incident has been resolved; the full update timeline is below.
Update timeline
- resolved Mar 17, 2026, 01:35 PM UTC
Between 13:16 and 13:35 UTC, we experienced a temporary service disruption in our APAC environment that impacted multiple services, including consent-related functionality. During the incident timeframe, customers may have observed the following behaviours: Module Impact Consent Management Failure in one of the following areas will occur: Inability to create preference center Failed authentication token requests, rendering customers unable to use any of the main application APIs Inability to verify the status of recent transactions for receipts Non-functional endpoint for /api/consentmanager/v1/datasubjects Non-functional endpoint for /api/consentmanager/v1/datasubjects/profiles VRM Vendor, Engagement and Contract Screens cannot not be accessed. Automation rules/Workflow rules related to Vendor, Engagement and Contract objects will not be working. Assessments involving Vendor, Engagement, and Contract objects cannot be responded/ approved. Public API involving Vendor, Engagement, and Contract objects will fail Policy & Notice Management Policy & Notice : Locations of privacy-notices cannot be tracked Enterprise-Policy : Private share link won't work All admin pages in Policy Management will be impacted Data Mapping Customers may be unable to access or update inventory items, including assets, processing activities, vendors, and legal entities. Submission of assessments related to inventory may be affected. Ongoing bulk import jobs for inventory data might experience disruptions. Core Services Gateway failures, Notifications (emails) delivery delays/failures, Missing Translations, scheduled events not triggered, exports/uploads/download of documents failing Unable to access environment 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- 1432 . Root cause analysis investigations have been initiated, and an RCA will be provided.