Is OneTrust Down?

<p></p> <div> <p>We are investigating an issue affecting the HA Profiles API that may impact some customers. Engineering is actively working to determine the cause and scope of impact.</p> <p>We have engaged our cloud service provider and are working with them toward resolution. We will provide another update when additional information becomes available.</p> </div> <p>&nbsp;</p>

<p></p> <div> <p>We identified a service interruption affecting multiple OneTrust modules within the APP environment between <strong>14:08 UTC and 14:35 UTC on 23 October 2026</strong>. During this period, customers may have experienced intermittent connectivity and temporary difficulties accessing the platform or performing actions within affected modules.</p> <p>&nbsp;</p> </div> <ul> <li><strong>Assessment Automation:</strong> Customers may have experienced degraded performance or temporary inability to access Assessment Automation and associated APIs.</li> <li><strong>Awareness Training:</strong> Customers may have been unable to access courses, complete training, or perform new enrolments.</li> </ul> <ul> <li><strong>Cookie Consent:</strong> Customers may have been unable to add new sites for scanning, view scan progress, manage cookies or services, publish domains, or perform actions on templates and frameworks.</li> </ul> <ul> <li><strong>Consent Management:</strong> Customers may have experienced failures creating Preference Centres, requesting authentication tokens, checking recent receipt transactions, or using affected Consent APIs.</li> </ul> <ul> <li><strong>Core Services:</strong> Customers may have experienced temporary difficulty accessing the environment, alongside potential gateway failures, notification delays or failures, missing translations, scheduled-event disruption, or failed document exports, uploads, and downloads.&nbsp;</li> </ul> <ul> <li><strong>Data Discovery:</strong> Customers may have been unable to initiate new scans, while existing scan ingestion, term/tag assignments, and Policy and Automation Rules may have been affected.&nbsp;</li> </ul> <ul> <li><strong>Data Mapping:</strong> Customers may have been unable to access or update inventory items, submit inventory-related assessments, or complete ongoing bulk imports.&nbsp;</li> </ul> <ul> <li><strong>Privacy Rights Automation (DSAR):</strong> Customers may have experienced failures or delays submitting requests, creating submitted requests, or accessing Data Subject Portal and webform functionality.</li> </ul> <ul> <li><strong>Governance, Risk and Compliance (GRC):</strong> Customers may have experienced failures accessing the Risk Register or Controls, or creating and updating risks.&nbsp;</li> </ul> <ul> <li><strong>Preference Centre:</strong> Customers may have been temporarily unable to load their Preference Centre portal.</li> </ul> <ul> <li><strong>Incident &amp; Breach:</strong> Customers may have experienced failures accessing linked incidents, completing incident-type assessments, running related Automation Rules, or logging into Incident Management.</li> </ul> <ul> <li><strong>Integrations:</strong> Customers may have experienced delays processing events or errors when calling Webhook APIs.</li> </ul> <ul> <li><strong>Login / Access Management:</strong> Customers may have experienced login failures or API calls failing to validate credentials.</li> </ul> <ul> <li><strong>Policy &amp; Notice Management:</strong> Customers may have experienced disruption across Policy Management administration pages, privacy-notice location tracking, and private share links.&nbsp;</li> </ul> <ul> <li><strong>Reporting / Insights &amp; Dashboards:</strong> Customers may have been unable to access reports or dashboards, experienced failures exporting scheduled reports, or seen delays in data being reflected in reports and dashboards.</li> </ul> <ul> <li><strong>Third-Party Risk Management (VRM):</strong> Customers may have been unable to access Vendor, Engagement, and Contract screens, use associated APIs and automation/workflow rules, or respond to and approve related assessments.</li> </ul> <p>&nbsp;</p> <p>Corrective actions were deployed, and we confirmed that the customer impact was mitigated. This incident is resolved.</p> <p>If you have any questions or need further assistance, please create a support case by visiting the <strong>Get Help</strong> section of my.onetrust.com, quoting incident reference <strong>IM-1733</strong>.</p> <p>&nbsp;</p>

<p></p> <div> <p>We are investigating an issue affecting cookie scan processing in the APP environment.<br/><br/>Customers may observe scheduled or manually initiated cookie scans remaining in a <strong>Pending</strong> or <strong>Queued</strong> status and not progressing as expected.</p> <p>Our teams are actively investigating the cause and working to restore normal scan processing.</p> <p>We will provide further updates as additional information becomes available.</p> </div> <p>&nbsp;</p>