Is OneTrust down?

We identified a service interruption affecting multiple OneTrust modules within the APP environment between 14:08 UTC and 14:35 UTC on 23 October 2026 . During this period, customers may have experienced intermittent connectivity and temporary difficulties accessing the platform or performing actions within affected modules.   Assessment Automation: Customers may have experienced degraded performance or temporary inability to access Assessment Automation and associated APIs. Awareness Training: Customers may have been unable to access courses, complete training, or perform new enrolments. Cookie Consent: 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. Consent Management: Customers may have experienced failures creating Preference Centres, requesting authentication tokens, checking recent receipt transactions, or using affected Consent APIs. Core Services: 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.  Data Discovery: 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.  Data Mapping: Customers may have been unable to access or update inventory items, submit inventory-related assessments, or complete ongoing bulk imports.  Privacy Rights Automation (DSAR): Customers may have experienced failures or delays submitting requests, creating submitted requests, or accessing Data Subject Portal and webform functionality. Governance, Risk and Compliance (GRC): Customers may have experienced failures accessing the Risk Register or Controls, or creating and updating risks.  Preference Centre: Customers may have been temporarily unable to load their Preference Centre portal. Incident & Breach: Customers may have experienced failures accessing linked incidents, completing incident-type assessments, running related Automation Rules, or logging into Incident Management. Integrations: Customers may have experienced delays processing events or errors when calling Webhook APIs. Login / Access Management: Customers may have experienced login failures or API calls failing to validate credentials. Policy & Notice Management: Customers may have experienced disruption across Policy Management administration pages, privacy-notice location tracking, and private share links.  Reporting / Insights & Dashboards: 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. Third-Party Risk Management (VRM): 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.   Corrective actions were deployed, and we confirmed that the customer impact was mitigated. This incident is resolved. If you have any questions or need further assistance, please create a support case by visiting the Get Help section of my.onetrust.com, quoting incident reference IM-1733 .

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

Our investigation has identified a backlog affecting the processing of cookie scan results. As a result, some customers may continue to observe website scans remaining in a Pending or Queued status for longer than expected. Our Engineering teams have developed a fix to address the processing issue, which is currently undergoing validation prior to deployment. We will provide a further update as remediation progresses. We apologize for the continued inconvenience and appreciate your patience.

Regression testing of the fix is nearing completion, with deployment planned within the next 24 hours. Following deployment, our teams will validate cookie scan processing to ensure normal processing has been restored and the issue is resolved. We will provide a further update once post-deployment validation is complete.

The previously communicated fix has now been deployed. Following deployment, we have observed an improvement in the processing of the backlog; however, some customers may continue to experience website scans remaining in a Pending or Queued status for longer than expected. Our Engineering teams are actively exploring additional remediation options to increase processing throughput and reduce the remaining backlog more quickly. We apologize for the continued inconvenience and appreciate your patience. We continue to closely monitor progress and will provide further updates as key remediation milestones are reached.

Our Engineering teams are actively working on the deployment of an additional hotfix to improve backlog processing and accelerate the reduction of the remaining backlog. We continue to closely monitor the situation and will keep you updated on the progress of the hotfix deployment and subsequent recovery. We apologize for the continued inconvenience and appreciate your patience.

The additional hotfix has been successfully deployed, and following a period of monitoring, we have confirmed that backlog processing has recovered and the incident is now resolved.   If you are still experiencing issues, please contact our support teams, quoting IM -1732. Root cause analysis investigations have been initiated and an RCA will be provided.

We will be carrying out emergency maintenance on the DataGuidance platform. The maintenance will begin at 17:00 UTC, and is expected to take approximately four hours, during which the module will be temporarily unavailable. During the maintenance window, DataGuidance will be unavailable, and customers attempting to access the module may receive a 403 error. If you have any questions or need further assistance, please create a support case by visiting the 'Get Help' section of my.onetrust.com ,  quoting the reference IM-1730. We apologise for any inconvenience caused.

The emergency maintenance for DataGuidance has now been completed, and the service has been restored. Customers should now be able to access DataGuidance as normal. We apologise for the disruption and thank you for your patience while the maintenance was completed.

We are investigating a disruption affecting data processing services in the APP-IN, APP-EU, APP-CH, and APP-BR environments. Customers in these environments may experience stale or delayed data within Reports and Dashboards while data processing activities are impacted. Our investigation has determined that the issue is associated with a third-party service dependency that supports underlying data processing workloads. We are actively engaged with the third-party provider, who has identified the issue and is working on a remediation.   Customers may observe the following behaviors: Reports & Dashboards Reports displaying outdated or stale information. Dashboard metrics not reflecting the latest available data. Delays in scheduled data refreshes and analytics processing. Engineering teams are actively monitoring the situation and working alongside the third-party provider to restore normal operation. We will provide an additional update as more information becomes available.

Engineering has identified the issue and remediation efforts are progressing. Recovery activities remain ongoing as teams work to restore normal service across affected environments. We will provide an additional update as more information becomes available.

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 -1720. Root cause analysis investigations have been initiated and an RCA will be provided.

We are investigating an issue affecting multiple services within the APP-AE environment. Customers may experience service unavailability or failures when accessing affected modules and associated functionality. Our Engineering teams are actively investigating to determine the cause and restore normal service. We will provide a further update as more information becomes available.

We have identified that the current disruption is associated with connectivity to a third-party service used by the APP-AE environment. The connectivity issue is affecting multiple OneTrust services and resulting in service unavailability. We have escalated the issue directly with the provider, and our Cloud Operations and Engineering teams are working alongside them to restore normal service. Customers may observe the following behaviours: Login Login failures, API call failing to validate credentials Core Gateway failures, Notifications (emails) delivery delays/failures, Missing Translations, scheduled events not triggered, exports/uploads/download of documents failing Unable to access environment Cookies Unable to add new sites for scanning. Unable to view the progress of existing scans. Unable to add manual cookies. Unable to add or modify services. Unable to publish domains. Unable to perform any actions on the template or framework. DSAR Failures of request submission or delays in creating the submitted request Failures in accessing the data subject portal and webform GRC Risk Register won’t load as it depends on User/Org services for enriching user/org data. Create/Update risk will fail as we are validating/creating users set as risk approvers/owners. Controls could not be accessed as they depend on User/Org services for enriching user/org data. 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. VRM Vendor, Engagement and Contract Screens cannot 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 Privacy Portal The following Consent APIs will not function: /api/consent/V2/reciepts /api/consentmanager/V1/datasubjects/profiles/ /api/consentmanager/V2/linkedidentitygroups/ /api/consentmanager/V2/datasubjects /api/consentmanager/V1/linktokens /api/consentmanager/V1/preferencecenters/{preferenceCenterUUID}/datasubjects/preferences Data Discovery Customers won't be able to initiate new scans Existing scan ingestion will be impacted Term/Tag assignments will be impacted Disabled feature for Policy & Automation Rules

We are seeing recovery across the APP-AE environment, with the majority of affected services successfully reconnecting and returning to normal operation. Consent, DSAR and DSAR Webform services remain affected at this time. Our third-party service provider, Confluent, has confirmed that the disruption was caused by a server-side issue within their service. Our Engineering and Cloud Operations teams remain engaged with Confluent while we work to restore connectivity for the remaining affected services. We continue to closely monitor recovery and will provide a further update once all services have been restored.

The service disruption affecting multiple modules within the APP-AE environment has been resolved, and all affected services have returned to normal operation. Our investigation confirmed that the disruption resulted from a server-side issue affecting a third-party service provider used by the APP-AE environment. We worked directly with the provider to restore connectivity and have confirmed recovery across all affected services. We apologise for the disruption and appreciate your patience while we worked to restore service. A Root Cause Analysis (RCA) providing further details of the incident will be made available within 10 days.