OneTrust Outage History

Started Oct 23, 2026, 01:11 PM UTC· resolved Oct 23, 2026, 01:33 PM UTC

1. resolved Oct 23, 2026, 01:33 PM UTC

   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 .

Read the full incident report →

Started Oct 22, 2026, 10:24 PM UTC· resolved Oct 26, 2026, 04:00 PM UTC

1. investigating Oct 22, 2026, 10:24 PM UTC

   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.

2. identified Oct 23, 2026, 11:55 AM UTC

   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.

3. identified Oct 23, 2026, 05:32 PM UTC

   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.

4. monitoring Oct 23, 2026, 09:59 PM UTC

   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.

5. identified Oct 26, 2026, 10:00 AM UTC

   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.

6. resolved Oct 26, 2026, 04:00 PM UTC

   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.

Read the full incident report →

Started Oct 21, 2026, 04:45 PM UTC· resolved Oct 21, 2026, 07:57 PM UTC

1. investigating Oct 21, 2026, 04:45 PM UTC

   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-1729. We apologise for any inconvenience caused.

2. resolved Oct 21, 2026, 07:57 PM UTC

   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.

Read the full incident report →

Started Oct 09, 2026, 12:11 PM UTC· resolved Oct 09, 2026, 10:40 PM UTC

1. investigating Oct 09, 2026, 12:54 PM UTC

   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.

2. investigating Oct 09, 2026, 04:02 PM UTC

   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.

3. resolved Oct 09, 2026, 10:40 PM 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 -1720. Root cause analysis investigations have been initiated and an RCA will be provided.

Read the full incident report →

Started Oct 06, 2026, 12:51 PM UTC· resolved Oct 06, 2026, 03:07 PM UTC

1. investigating Oct 06, 2026, 12:51 PM UTC

   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.

2. investigating Oct 06, 2026, 01:23 PM UTC

   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

3. identified Oct 06, 2026, 02:46 PM UTC

   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.

4. resolved Oct 06, 2026, 03:07 PM UTC

   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.

Read the full incident report →

Started Sep 16, 2026, 08:41 AM UTC· resolved Sep 16, 2026, 05:28 PM UTC

1. investigating Sep 16, 2026, 08:41 AM UTC

   We are aware of an issue affecting My.OneTrust , which is currently unavailable. Customers may be unable to access my.onetrust.com. The issue is associated with an interruption affecting Salesforce services. We are monitoring the situation and will provide further updates as service availability changes.

2. identified Sep 16, 2026, 10:01 AM UTC

   Customers may continue to experience intermittent issues accessing My.OneTrust and the Customer Support Portal. Salesforce has acknowledged an ongoing service incident affecting its services. We are closely monitoring their progress and will provide further updates as the situation develops.

3. identified Sep 16, 2026, 12:07 PM UTC

   Salesforce have confirmed that they have identified the root cause and are implementing corrective actions. The rollout is progressing region by region and they report seeing improvement. We don't currently have a confirmed time of completion. Customers may continue to experience severe delays, intermittent errors, and inability to access some services and support case creation

4. monitoring Sep 16, 2026, 04:04 PM UTC

   We are seeing continued improvement in the availability of My.OneTrust , with service currently appearing stable. Salesforce continues to address the remaining impact from its service incident, with recovery actions ongoing for a subset of affected instances. While conditions have improved, some customers may continue to experience intermittent access issues. We are continuing to monitor My.OneTrust closely and will provide a further update once service recovery has been confirmed.

5. resolved Sep 16, 2026, 05:28 PM UTC

   The intermittent access issues have been resolved, and the My.OneTrust portal is operating normally. The disruption was associated with a service incident affecting our third-party service provider, Salesforce. We will continue to monitor service availability following recovery. We apologise for any inconvenience this may have caused.

Read the full incident report →

Started Sep 11, 2026, 01:17 AM UTC· resolved Sep 11, 2026, 09:00 PM UTC

1. resolved Sep 11, 2026, 09:00 PM UTC

   On 11 September, from 01:17 UTC to 21:00 UTC, the Consent Receipts application experienced multiple intermittent outages lasting between 2 and 7 minutes each. The cumulative service disruption totaled 1 hour and 11 minutes. The issue was attributed to a service degradation within a third-party message broker infrastructure The intermittent outages were caused by a localized infrastructure degradation within a third-party message broker provider supporting the Consent Receipts service. The issue resulted in intermittent request failures affecting Consent Receipt API operations and related workflows. The provider implemented mitigation measures to stabilize the affected infrastructure and restore normal service operation. Following recovery, service performance returned to expected levels, and no further customer impact was observed.

Read the full incident report →

Started Sep 07, 2026, 06:03 AM UTC· resolved Sep 08, 2026, 07:00 AM UTC

1. identified Sep 07, 2026, 06:03 AM UTC

   We are aware of an issue reported by our third-party cloud provider that is affecting Reporting and Dashboard services. As a result, users may not see the latest data reflected in dashboards and reports across all modules. We are continuously engaged with our cloud provider and are actively monitoring the situation. At this time, only the Reporting and Dashboard services are impacted. We will continue to provide updates as the investigation progresses.

2. monitoring Sep 08, 2026, 05:00 AM UTC

   We have been actively engaged with our cloud provider and continuously monitoring the situation and the impacted services. Our cloud provider has implemented corrective actions and is closely monitoring the environment to ensure service stability. At this time, Reporting and Dashboard services are recovering, and we continue to track the situation closely. We will provide further updates as soon as additional information becomes available

3. resolved Sep 08, 2026, 07:00 AM UTC

   Corrective actions have been implemented, and following a period of monitoring, our cloud provider has confirmed that the issue has been resolved. All previously affected services are now operational, and our teams have independently validated that service functionality has been restored. If you are still experiencing issues, please contact our support teams quoting IM-1672 Root cause analysis investigations have been initiated and an RCA will be provided.

Read the full incident report →

Started Aug 14, 2026, 08:41 AM UTC· resolved Aug 14, 2026, 09:50 AM UTC

1. investigating Aug 14, 2026, 08:41 AM UTC

   We are investigating an issue affecting authentication for some customers in the APP-FR environment. Affected users may be unable to access the platform when attempting to sign in using Single Sign-On (SSO). Our engineering teams are actively investigating the issue to determine the underlying cause and identify a resolution. We will provide further updates as more information becomes available.

2. identified Aug 14, 2026, 08:54 AM UTC

   Our engineering teams have identified the underlying cause of the Single Sign-On (SSO) authentication issue. We are currently validating the corrective actions required to restore normal service and will provide a further update once implementation plans have been confirmed. We apologise for the continued disruption and appreciate your patience while we work to resolve this issue.

3. resolved Aug 14, 2026, 09:50 AM UTC

   Corrective actions have been deployed, and we confirm that the customer impact has been mitigated. If you continue to experience issues, please contact our Support team quoting IM‑1641 so we can review your case. Root cause analysis investigations have been initiated, and an RCA will be provided.

Read the full incident report →

Started Aug 11, 2026, 02:51 PM UTC· resolved Aug 11, 2026, 04:09 PM UTC

1. investigating Aug 11, 2026, 02:51 PM UTC

   We are investigating an issue affecting authentication for some customers in the UAT and UAT-DE environments. Affected users may be unable to access the platform when attempting to sign in using Single Sign-On (SSO). Our engineering teams are actively investigating the issue to determine the underlying cause and identify a resolution. We will provide further updates as more information becomes available.

2. identified Aug 11, 2026, 03:20 PM UTC

   Our engineering teams have identified the underlying cause of the Single Sign-On (SSO) authentication issue affecting the UAT and UAT-DE environments and are actively working on a resolution. We are currently validating the corrective actions required to restore normal service and will provide a further update once implementation plans have been confirmed. We apologise for the continued disruption and appreciate your patience while we work to resolve this issue.

3. resolved Aug 11, 2026, 04:09 PM UTC

   Corrective actions have been deployed, and we confirm that the customer impact has been mitigated. If you continue to experience issues, please contact our Support team quoting IM ‑1636 so we can review your case. Root cause analysis investigations have been initiated, and an RCA will be provided.

Read the full incident report →

Started Jul 22, 2026, 05:17 AM UTC· resolved Aug 02, 2026, 04:12 AM UTC

1. resolved Aug 02, 2026, 04:12 AM UTC

   Between 22 July and 2 August, an issue affecting an Azure Batch node impacted website cookie scan processing across multiple environments, causing scan tasks routed to the affected node to remain in a pending state and fail. Following investigation, Microsoft identified the affected batch node and removed it from service, restoring normal scan processing. Customers who initiated website scans during the affected period may observe scans that remain in a pending status or have failed. To complete processing, impacted scans should be stopped and re-run. No scan configurations, collected data, or customer settings were affected by this issue. If you continue to experience issues after re-running your scans, please contact OneTrust Support and reference IM-1615 . A full Root Cause Analysis (RCA) has been initiated and will be provided upon completion of the investigation.

Read the full incident report →

Started Jul 15, 2026, 03:25 PM UTC· resolved Jul 15, 2026, 03:44 PM UTC

1. investigating Jul 15, 2026, 03:25 PM UTC

   We are currently investigating an issue affecting multiple services within the APP-UK environment following the disconnection of several system monitoring components. Potential Impact Consent Receipts Customers may experience failures when retrieving Consent Receipt details through API integrations. Consent Receipt retrieval requests from CMP-configured websites and SDK implementations may also be unsuccessful. DSAR Submission of Data Subject Requests (DSARs) may fail or experience delays. Users may encounter issues accessing the Data Subject Request Portal and associated webforms. This may result in delays to request processing timelines. We’re investigating the issue and will provide an update as soon as possible.

2. resolved Jul 15, 2026, 03:44 PM UTC

   Corrective actions have been completed, and we confirm that the customer impact has been mitigated. If you continue to experience issues, please contact our Support team quoting IM ‑1585 so we can review your case. Root cause analysis investigations have been initiated, and an RCA will be provided.

Read the full incident report →

Started Jul 07, 2026, 10:33 AM UTC· resolved Jul 07, 2026, 10:53 AM UTC

1. investigating Jul 07, 2026, 10:33 AM UTC

   We are currently investigating an issue affecting multiple services within the UAT environment following the disconnection of several system monitoring components. Potential Impact Consent Receipts Customers may experience failures when retrieving Consent Receipt details through API integrations. Consent Receipt retrieval requests from CMP-configured websites and SDK implementations may also be unsuccessful. DSAR Submission of Data Subject Requests (DSARs) may fail or experience delays. Users may encounter issues accessing the Data Subject Request Portal and associated webforms. This may result in delays to request processing timelines. Preference Centre Preference Centre portals may be unavailable or fail to load for end users. Our teams are actively investigating the issue and working to restore normal service. We will provide further updates as soon as more information becomes available.

2. resolved Jul 07, 2026, 10:53 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-1573 . Root cause analysis investigations have been initiated, and an RCA will be provided.

Read the full incident report →

Started Jul 03, 2026, 01:27 PM UTC· resolved Jul 03, 2026, 01:47 PM UTC

1. investigating Jul 03, 2026, 01:27 PM UTC

   We've identified an issue affecting Consent Receipt processing and DSAR request submissions within the APP-JP environment. Users may experience: Consent Receipts Failures of Consent receipt calls from the customer API workflow. Failures of Consent receipt calls from CMP configured websites & SDKs. DSAR Failures of request submission or delays in creating the submitted request Failures in accessing the data subject portal and webform Our teams are investigating, and an update will be provided as soon as possible.

2. resolved Jul 03, 2026, 01:47 PM 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 -1570. Root cause analysis investigations have been initiated, and an RCA will be provided.

Read the full incident report →

Started Jun 18, 2026, 02:30 PM UTC· resolved Jun 18, 2026, 02:55 PM UTC

1. resolved Jun 18, 2026, 02:55 PM UTC

   Between 14:30 and 14:55 UTC, customers in the APP‑UK environment may have observed issues loading the Consent Preference Centre portal. The issue has been mitigated, and normal service has been restored. If you are still experiencing any issues, please contact our Support team and reference IM‑1545 so we can review your case promptly. A root cause analysis (RCA) is currently underway, and a further update will be provided once this has been completed.

Read the full incident report →

Started Jun 17, 2026, 04:00 PM UTC· resolved Aug 13, 2026, 03:33 PM UTC

1. investigating Jun 17, 2026, 04:00 PM UTC

   OneTrust is investigating a security incident related to a compromised Salesforce-Klue integration. We have taken immediate action to contain the issue, including disabling the affected integration, blocking malicious access, and engaging external specialists. This investigation is ongoing and we are communicating directly with our customers as we continue to assess the full scope of this incident and data impacted. At this time, there is no impact to OneTrust platform availability. Please visit my.onetrust.com for more details.

2. resolved Aug 13, 2026, 03:33 PM UTC

   We will continue to provide updates on any material developments through the OneTrust blog and the OneTrust Community. If you need additional support, please reach out to your appropriate contact at OneTrust or submit a support case , quoting IM-1547.

Read the full incident report →

Started Jun 17, 2026, 11:21 AM UTC· resolved Jun 17, 2026, 12:14 PM UTC

1. resolved Jun 17, 2026, 12:14 PM UTC

   On 17 June, from 11:21 UTC to 12:14 UTC (52 minutes), the Data Mapping module in UAT-DE experienced an outage. Impact to customer: Customers may experience the following: 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. Corrective actions have been completed, and we confirm that the customer impact has been mitigated. If you continue to experience issues, please contact our Support team quoting IM ‑1540 so we can review your case. Root cause analysis investigations have been initiated, and an RCA will be provided.

Read the full incident report →

Started Jun 03, 2026, 07:33 AM UTC· resolved Jun 03, 2026, 07:46 AM UTC

1. resolved Jun 03, 2026, 07:46 AM UTC

   Between 07:33 UTC and 07:46 UTC, customers may have experienced issues accessing the Preference Center within the APP production environment. During this time, Consent APIs may also have been impacted. Corrective actions have been implemented, and service stability has been restored. Engineering teams are conducting further investigation into the underlying platform behaviour observed during the event. If you continue to experience issues, please contact our Support team quoting IM ‑1532 . Root cause analysis investigations have been initiated, and an RCA will be provided.

Read the full incident report →

Started May 29, 2026, 04:58 AM UTC· resolved May 29, 2026, 09:50 PM UTC

1. investigating May 29, 2026, 04:58 AM UTC

   We are currently investigating a service disruption affecting the UAT-HC environment due to a third-party service outage. Our team is actively working with the provider to restore services as quickly as possible. We will continue to share updates as more information becomes available.

2. investigating May 29, 2026, 08:30 AM UTC

   We’re continuing to work closely with our third-party service provider to investigate the outage and are monitoring the situation closely. Further updates will be shared as soon as more information becomes available.

3. investigating May 29, 2026, 10:00 AM UTC

   We are continuing to investigate this issue with our third-party service provider. Based on the information available, the disruption was caused by a power event at their data center, resulting in a regional impact that is currently affecting OT services in the UAT-HC environment. Mitigation efforts are carried through to resolve this issue, and we are closely monitoring the situation. We will continue to share updates as more information becomes available.

4. monitoring May 29, 2026, 12:00 PM UTC

   Our service provider continues to work on mitigation efforts, and we are closely monitoring the situation. Services in the UAT-HC environment remain impacted due to the ongoing outage. We will continue to share updates as more information becomes available.

5. resolved May 29, 2026, 09:50 PM UTC

   We’ve received notice from our third-party provider stating that the outage has been mitigated. Our own monitoring has confirmed that their mitigation actions have been successful, resulting in this incident being considered as resolved. If you are still experiencing issues, please contact our support teams quoting IM-1526. Root cause analysis investigations have been initiated by our third-party, and an RCA will be provided.

Read the full incident report →

Started May 21, 2026, 01:36 PM UTC· resolved May 21, 2026, 02:32 PM UTC

1. investigating May 21, 2026, 01:36 PM UTC

   We’ve identified an issue affecting Consent Receipt processing, where API calls from customer workflows and integrations (including CMP-configured websites and SDKs) are failing. As a result, workflows attempting to retrieve Data Subject (DS) details via the Consent Receipt service may not complete successfully. We are actively investigating the issue and will provide a further update as soon as more information is available.

2. resolved May 21, 2026, 02:32 PM 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-1517 . Root cause analysis investigations have been initiated, and an RCA will be provided.

Read the full incident report →

Started May 05, 2026, 12:00 PM UTC· resolved May 14, 2026, 11:00 AM UTC

1. identified May 05, 2026, 12:00 PM UTC

   We have received multiple reports from users with behaviour that matches a known defect. This behaviour will be corrected in version 202605.1.0. Until this time, please review the following details on this Known Defect: Impacted users may notice that the option to launch an assessment is no longer available from the following modules: Data Mapping: Within an inventory record when accessing the context menu (three‑dot menu). This can be found in Data Mapping > Processing Activities > Assessments. Third-Party Risk Management: Within the Vendor records when accessing the context menu (three‑dot menu). Workaround While we work to implement a fix for this issue, we recommend users launch assessments either from the Inventory list view or from the Details tab of the relevant inventory record. Further information on this Known Defect can be found inside our Known Defect Database here: [DM] Known Defect: Assessment launch option is missing from both the Inventory Assessment and Vendor Records context menus | MyOneTrust

2. resolved May 14, 2026, 11:00 AM UTC

   Due to the number of reports we received, the priority of the developed fix was increased. We can now confirm that this behaviour has been resolved following the deployment of build version 202604.2.6. If you continue to experience issues, please contact our Support team quoting IM‑1510 so we can review your case. Root cause analysis investigations have been initiated, and an RCA will be provided.

Read the full incident report →

Started Apr 27, 2026, 06:07 PM UTC· resolved Apr 27, 2026, 06:45 PM UTC

1. investigating Apr 27, 2026, 06:07 PM UTC

   We are currently investigating an issue impacting the Insights & Reporting Dashboards service. Customers may experience the following: Inability to access reports/dashboards from the Reporting Module screens Failures in exporting scheduled reports Delays in the module data being reflected in reports/dashboards This issue is related to an ongoing incident with our upstream data processing provider (Databricks), which is currently reporting service disruption on their status page.

2. resolved Apr 27, 2026, 06:45 PM UTC

   The issue impacting the Insights & Reporting Dashboards service has been resolved. Customers should now be able to access reports and dashboards as expected, with scheduled exports and data updates operating normally. This issue was related to a disruption affecting a third-party data processing service. The service has now recovered, and we have confirmed normal functionality across impacted environments. If you are still experiencing issues, please contact our support teams quoting IM-1490 . Root cause analysis investigations have been initiated, and an RCA will be provided.

Read the full incident report →

Started Apr 17, 2026, 07:30 AM UTC· resolved Apr 20, 2026, 10:45 AM UTC

1. investigating Apr 17, 2026, 07:30 AM UTC

   Following the recent incident resolution, our backend teams have identified that a reporting lag still persists. Our engineering team is actively investigating and working to reduce the remaining lag in the environment. Users will still continue to see data freshness Issues on DSAR Dashboards and Reports. The impact is currently limited to users accessing the service through the APP environment. We will continue to provide updates as progress is made.

2. resolved Apr 20, 2026, 10:45 AM UTC

   Corrective actions have been deployed, and after a period of monitoring, we've confirmed that the processing lag has decreased to minimal 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.

Read the full incident report →

Started Apr 16, 2026, 03:46 PM UTC· resolved Apr 16, 2026, 04:00 PM UTC

1. resolved Apr 16, 2026, 04:00 PM UTC

   Between 1 5:46 UTC and 16:00 UTC on 16 April 2026, customers hosted within the APP-APAC production environment may have experienced issues affecting Consent Management, the HA Profiles API, and the HA Preference Center. During this period, customers may have observed failures, including: Consent Management Inability to create a 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 Privacy Management One of the following failures will start occurring, and the API will not function: /rest/api/preferences/v3/datasubjects/profile /rest/api/preferences/v3/datasubject-profiles Corrective actions have now been deployed and, following a period of monitoring, we have confirmed that service has stabilised and the incident is resolved. If you are continuing to experience issues, please contact Support and quote IM-1476. A root cause analysis is now underway, and an RCA will be provided once that investigation is complete.

Read the full incident report →

Started Apr 15, 2026, 03:06 PM UTC· resolved Apr 17, 2026, 04:30 AM UTC

1. 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.

2. 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.

3. 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.

4. 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.

Read the full incident report →