onetruststatus-1564678085559.site24x7statusiq.com
Open in
urlscan Pro
136.143.191.134
Public Scan
URL:
https://onetruststatus-1564678085559.site24x7statusiq.com/
Submission: On June 12 via manual from AU — Scanned from AU
Submission: On June 12 via manual from AU — Scanned from AU
Form analysis 2 forms found in the DOM
Name: filter.form —
<form flex="" name="filter.form" class="ng-pristine ng-valid flex">
<input type="text" placeholder="Search Components" ng-model="searchResult" ng-change="expandCompGroupSearch(searchResult,false)" class="ng-pristine ng-untouched ng-valid ng-empty" aria-invalid="false">
</form>Name: filter.form —
<form flex="" name="filter.form" class="ng-pristine ng-valid flex">
<input type="text" placeholder="Search Components" ng-model="searchResult" ng-change="expandCompGroupSearch(searchResult,false)" class="ng-pristine ng-untouched ng-valid ng-empty" aria-invalid="false">
</form>Text Content
ONETRUST STATUS Subscribe Subscribe ACTIVE INCIDENT [IM-590] DSAR REQUESTS NOTIFICATION LAG This incident has been open for 7 hours 56 mins 8 secs and was last updated 7 hours 50 sec(s) ago. Incident Start Time Jun 12, 2024 04:18:16 AM AWST Affected Components APP: Admin Portal (APP), APP: Consent Receipts (APP), APP: Data Subject Portal (APP) Incident Status Updates Investigating Our engineering teams have identified the root cause and corrective measures are being implemented. Additional updates will be provided as they become available. Posted on Jun 12, 2024 at 05:13:34 AM AWST (7 hours 50 sec(s) ago) Acknowledged We’ve identified an issue where users may encounter intermittent latency when accessing the DSAR service through the APP environment. Some users may experience failures in request submission delays in creating submitted requests, or failures in accessing datasubject portal and webform. We’re investigating the issue and will provide an update as soon as possible. Posted on Jun 12, 2024 at 04:18:16 AM AWST (7 hours 56 mins 8 secs ago) [IM-558] DASHBOARDS MISSING FROM THE REPORTS MODULE This incident has been open for 13 days 16 hours 14 mins and was last updated 10 hours 23 mins 23 secs ago. Incident Start Time May 29, 2024 08:00:00 PM AWST Affected Components APP: Admin Portal (APP), APP-DE: Admin Portal (APP-DE), APP-APAC: Admin Portal (APP-APAC), APP-EU: Admin Portal (APP-EU), APP-AU: Admin Portal (APP-AU), APP-UK: Admin Portal (APP-UK), APP-BR: Admin Portal (APP-BR), UAT: Admin Portal (UAT), UAT-DE: Admin Portal (UAT-DE), APP-CA: Admin Portal (APP-CA) and 8 more Incident Status Updates Identified Our Engineers have identified a potential solution and are evaluating corrective measures. Additional updates will be provided when available. Posted on Jun 12, 2024 at 01:51:01 AM AWST (10 hours 23 mins 23 secs ago) Investigating We’ve identified an issue where users may see some Dashboards missing from within their Reports module. The issue is specific to Dashboards that leverage the “Governance, Risk, Compliance” Data Source. This impact can be observed across all environments. We’re investigating the issue and will provide an update as soon as possible. Posted on May 29, 2024 at 08:00:00 PM AWST (13 days 16 hours 14 mins ago) COMPONENT SUMMARY Component Name Component Status APP Degraded Performance APP: Admin Portal Degraded Performance APP: Consent Receipts Degraded Performance APP: Data Subject Portal Degraded Performance APP-AE Informational APP-AE: Admin Portal Informational APP-AE: Privacy Portal Response Time : 460 ms Operational APP-APAC Informational APP-APAC: Admin Portal Informational APP-APAC: Consent Receipts Response Time : 56 ms Operational APP-APAC: Data Subject Portal Response Time : 51 ms Operational APP-AU Informational APP-AU: Admin Portal Informational APP-AU: Consent Receipts Response Time : 62 ms Operational APP-AU: Data Subject Portal Response Time : 64 ms Operational APP-BR Informational APP-BR: Admin Portal Informational APP-BR: Consent Receipts Response Time : 103 ms Operational APP-BR: Data Subject Portal Response Time : 148 ms Operational APP-CA Informational APP-CA: Admin Portal Informational APP-CA: Consent Receipt Response Time : 84 ms Operational APP-CA: Privacy Portal Response Time : 127 ms Operational APP-CH Informational APP-CH: Admin Portal Informational APP-CH: Consent Receipt Response Time : 141 ms Operational APP-CH: Privacy Portal Response Time : 53 ms Operational APP-DE Informational APP-DE: Admin Portal Informational APP-DE: Consent Receipts Response Time : 58 ms Operational APP-DE: Data Subject Portal Response Time : 50 ms Operational APP-EU Informational APP-EU: Admin Portal Informational APP-EU: Consent Receipts Response Time : 62 ms Operational APP-EU: Data Subject Portal Response Time : 59 ms Operational APP-FR Informational APP-FR: Admin Portal Informational APP-FR: Consent Receipt Response Time : 157 ms Operational APP-FR: Data Subject Portal Response Time : 143 ms Operational APP-HC (APP-NA01) Informational APP-HC: Admin Portal Informational APP-HC: Consent Receipt Response Time : 176 ms Operational APP-HC: DSAR Webform Integration Response Time : 151 ms Operational APP-IN Informational APP-IN: Admin Portal Informational APP-IN: Consent Receipt Response Time : 69 ms Operational APP-IN: Data Subject Portal Response Time : 109 ms Operational APP-JP Informational APP-JP: Admin Portal Informational APP-JP: Consent Receipt Response Time : 597 ms Operational APP-JP: Privacy Portal Response Time : 65 ms Operational APP-UK Informational APP-UK: Admin Portal Informational APP-UK: Consent Receipts Response Time : 97 ms Operational APP-UK: Data Subject Portal Response Time : 127 ms Operational CookiePro Informational CookiePro: Admin Console Informational Cookie Geolocation Service Response Time : 69 ms Operational CookiePro: Cookie Banners Response Time : 63 ms Operational UAT Informational UAT: Admin Portal Informational UAT-DE Informational UAT-DE: Admin Portal Informational UAT-HC (UAT-NA01) Informational UAT-HC: Admin Portal Informational UAT-HC: Consent Receipt Response Time : 166 ms Operational UAT-HC: DSAR Webform Integration Response Time : 154 ms Operational Vendorpedia Operational App-Vendorpedia: Login Response Time : 1.17 s Operational VENDORPEDIA: Admin Portal Response Time : 68 ms Operational Consent HA Preferences API Response Time : 244 ms Operational Cookie Banner Response Time : 55 ms Operational Mobile CMP App Data Response Time : 159 ms Operational COMPONENT STATUS HISTORY Jun 12 to Jun 6 Jun 12 to Jun 6 Component Name Uptime Jun 12Jun 11Jun 10Jun 9Jun 8Jun 7Jun 6 APP 100 % APP: Admin Portal 100 % APP: Consent Receipts 100 % APP: Data Subject Portal 99.99 % APP-AE 99.99 % APP-AE: Admin Portal 100 % APP-AE: Privacy Portal 99.98 % APP-APAC 100 % APP-APAC: Admin Portal 100 % APP-APAC: Consent Receipts 100 % APP-APAC: Data Subject Portal 100 % APP-AU 100 % APP-AU: Admin Portal 100 % APP-AU: Consent Receipts 100 % APP-AU: Data Subject Portal 100 % APP-BR 100 % APP-BR: Admin Portal 100 % APP-BR: Consent Receipts 100 % APP-BR: Data Subject Portal 100 % APP-CA 100 % APP-CA: Admin Portal 100 % APP-CA: Consent Receipt 100 % APP-CA: Privacy Portal 100 % APP-CH 100 % APP-CH: Admin Portal 100 % APP-CH: Consent Receipt 100 % APP-CH: Privacy Portal 100 % APP-DE 100 % APP-DE: Admin Portal 100 % APP-DE: Consent Receipts 100 % APP-DE: Data Subject Portal 100 % APP-EU 99.62 % APP-EU: Admin Portal 98.85 % APP-EU: Consent Receipts 100 % APP-EU: Data Subject Portal 100 % APP-FR 100 % APP-FR: Admin Portal 100 % APP-FR: Consent Receipt 100 % APP-FR: Data Subject Portal 100 % APP-HC (APP-NA01) 100 % APP-HC: Admin Portal 100 % APP-HC: Consent Receipt 100 % APP-HC: DSAR Webform Integration 100 % APP-IN 100 % APP-IN: Admin Portal 100 % APP-IN: Consent Receipt 100 % APP-IN: Data Subject Portal 100 % APP-JP 100 % APP-JP: Admin Portal 100 % APP-JP: Consent Receipt 100 % APP-JP: Privacy Portal 100 % APP-UK 100 % APP-UK: Admin Portal 100 % APP-UK: Consent Receipts 100 % APP-UK: Data Subject Portal 100 % CookiePro 100 % CookiePro: Admin Console 100 % Cookie Geolocation Service 100 % CookiePro: Cookie Banners 100 % UAT 99.93 % UAT: Admin Portal 99.93 % UAT-DE 100 % UAT-DE: Admin Portal 100 % UAT-HC (UAT-NA01) 100 % UAT-HC: Admin Portal 100 % UAT-HC: Consent Receipt 100 % UAT-HC: DSAR Webform Integration 100 % Vendorpedia 100 % App-Vendorpedia: Login 100 % VENDORPEDIA: Admin Portal 100 % Consent HA Preferences API 100 % Cookie Banner 100 % Mobile CMP App Data 100 % Operational Informational Under Maintenance Degraded Performance Partial Outage Major Outage INCIDENT HISTORY JUN 12, 2024 No incidents have been reported. JUN 11, 2024 No incidents have been reported. JUN 10, 2024 No incidents have been reported. JUN 09, 2024 No incidents have been reported. JUN 08, 2024 INTEGRATIONS WORKFLOWS STUCK IN QUEUED STATUS Incident Duration From Jun 04, 2024 06:30:00 AM AWST to Jun 08, 2024 01:38:00 AM AWST (3 days 19 hours 8 mins) Affected Components APP: Admin Portal (APP) Incident Status Updates Resolved We are pleased to inform you that the hotfix was successfully deployed at 17:00 UTC. After a period of monitoring, we have confirmed that this incident has been resolved. If you are still experiencing issues, please contact our support teams quoting IM-578. Root cause analysis investigations have been initiated and an RCA will be provided. Posted on Jun 08, 2024 at 01:38:00 AM AWST Identified The hotfix has completed testing and deployment to the APP- environment will conclude within the next 120 minutes. Posted on Jun 07, 2024 at 11:23:27 PM AWST Identified Engineering teams have developed a hotfix to address the current issue. The hotfix is undergoing thorough regression testing to ensure its effectiveness, with a planned release on Friday, June 7th. We will provide a more accurate release timeframe tomorrow morning upon the successful completion of testing. Posted on Jun 07, 2024 at 04:57:24 AM AWST Identified We have identified the root cause of the issue affecting integration events submitted between 22:30 UTC on June 3rd and 23:30 UTC on June 4th. Our team is currently evaluating a permanent fix to reprocess the queued integration traffic. Following thorough testing, we will determine the timeline for deploying the corrective measures and will provide additional information and updates on Thursday, June 6th. Posted on Jun 06, 2024 at 05:52:34 AM AWST Identified Integration workflows and events submitted after 23:30 UTC on June 4th are processing as expected. The source of the problem for integration events submitted between 22:30 UTC on 03rd and 23:30 UTC on 04rd June has been identified through our collaboration with Azure. We are now working on determining the corrective actions required to resolve the processing of integration workflows and events submitted between 22:30 UTC on June 03rd to 23:30 UTC on June 4th. Posted on Jun 06, 2024 at 03:29:50 AM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. We are actively working with Microsoft Azure to troubleshoot and identify the root cause of the current issue affecting integration workflows stuck in queued status. Posted on Jun 05, 2024 at 10:32:17 PM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. We are actively working with Microsoft Azure to troubleshoot and identify the root cause of the current issue affecting integration workflows stuck in queued status. Posted on Jun 05, 2024 at 09:58:16 PM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. We have engaged MS Azure to help troubleshoot the root cause. Posted on Jun 05, 2024 at 07:48:14 PM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. Our engineering teams are actively analyzing error traffic to identify the root cause. Posted on Jun 05, 2024 at 04:52:20 PM AWST Observing Our team is still monitoring these queued integrations and will provide updates as soon as they become available. Posted on Jun 05, 2024 at 10:22:02 AM AWST Observing Corrective measures have been deployed, ensuring the successful processing of new integration workflows/events. Integrations submitted before the deployment of corrective measures will remain in a queued status until further notice. Our team is actively monitoring these queued integrations and will provide updates as soon as they become available. Posted on Jun 05, 2024 at 08:04:19 AM AWST Identified Our engineers are in the final stages of deploying corrective measures and are currently validating the results to resolve the ongoing service disruption. Posted on Jun 05, 2024 at 07:38:19 AM AWST Investigating Our engineering team is actively deploying corrective measures to address the ongoing interruption in service. Further updates will be provided as the deployment progresses. Posted on Jun 05, 2024 at 05:53:48 AM AWST Investigating The execution of integration workflows has encountered an interruption. Our engineering teams are deploying corrective measures to restore normal service operations. Posted on Jun 05, 2024 at 04:47:50 AM AWST Investigating We're continuing to analyze error traffic to determine the source of the issue. While the errors persist, we want to assure you that customer traffic is still processing. However, you may notice a reduction in processing rates during this time. Posted on Jun 05, 2024 at 04:42:34 AM AWST Investigating We're continuing to analyze error traffic to determine the source of the issue. Further updates will be provided as soon as possible. Posted on Jun 05, 2024 at 04:16:37 AM AWST Acknowledged We’ve identified an issue where users may observe integration workflows and events stuck in a queued status. The impact is limited to users accessing the service through the APP- environment. We’re investigating the issue and will provide an update as soon as possible. Posted on Jun 05, 2024 at 03:28:35 AM AWST JUN 07, 2024 INTEGRATIONS WORKFLOWS STUCK IN QUEUED STATUS Incident Duration From Jun 04, 2024 06:30:00 AM AWST to Jun 08, 2024 01:38:00 AM AWST (3 days 19 hours 8 mins) Affected Components APP: Admin Portal (APP) Incident Status Updates Resolved We are pleased to inform you that the hotfix was successfully deployed at 17:00 UTC. After a period of monitoring, we have confirmed that this incident has been resolved. If you are still experiencing issues, please contact our support teams quoting IM-578. Root cause analysis investigations have been initiated and an RCA will be provided. Posted on Jun 08, 2024 at 01:38:00 AM AWST Identified The hotfix has completed testing and deployment to the APP- environment will conclude within the next 120 minutes. Posted on Jun 07, 2024 at 11:23:27 PM AWST Identified Engineering teams have developed a hotfix to address the current issue. The hotfix is undergoing thorough regression testing to ensure its effectiveness, with a planned release on Friday, June 7th. We will provide a more accurate release timeframe tomorrow morning upon the successful completion of testing. Posted on Jun 07, 2024 at 04:57:24 AM AWST Identified We have identified the root cause of the issue affecting integration events submitted between 22:30 UTC on June 3rd and 23:30 UTC on June 4th. Our team is currently evaluating a permanent fix to reprocess the queued integration traffic. Following thorough testing, we will determine the timeline for deploying the corrective measures and will provide additional information and updates on Thursday, June 6th. Posted on Jun 06, 2024 at 05:52:34 AM AWST Identified Integration workflows and events submitted after 23:30 UTC on June 4th are processing as expected. The source of the problem for integration events submitted between 22:30 UTC on 03rd and 23:30 UTC on 04rd June has been identified through our collaboration with Azure. We are now working on determining the corrective actions required to resolve the processing of integration workflows and events submitted between 22:30 UTC on June 03rd to 23:30 UTC on June 4th. Posted on Jun 06, 2024 at 03:29:50 AM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. We are actively working with Microsoft Azure to troubleshoot and identify the root cause of the current issue affecting integration workflows stuck in queued status. Posted on Jun 05, 2024 at 10:32:17 PM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. We are actively working with Microsoft Azure to troubleshoot and identify the root cause of the current issue affecting integration workflows stuck in queued status. Posted on Jun 05, 2024 at 09:58:16 PM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. We have engaged MS Azure to help troubleshoot the root cause. Posted on Jun 05, 2024 at 07:48:14 PM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. Our engineering teams are actively analyzing error traffic to identify the root cause. Posted on Jun 05, 2024 at 04:52:20 PM AWST Observing Our team is still monitoring these queued integrations and will provide updates as soon as they become available. Posted on Jun 05, 2024 at 10:22:02 AM AWST Observing Corrective measures have been deployed, ensuring the successful processing of new integration workflows/events. Integrations submitted before the deployment of corrective measures will remain in a queued status until further notice. Our team is actively monitoring these queued integrations and will provide updates as soon as they become available. Posted on Jun 05, 2024 at 08:04:19 AM AWST Identified Our engineers are in the final stages of deploying corrective measures and are currently validating the results to resolve the ongoing service disruption. Posted on Jun 05, 2024 at 07:38:19 AM AWST Investigating Our engineering team is actively deploying corrective measures to address the ongoing interruption in service. Further updates will be provided as the deployment progresses. Posted on Jun 05, 2024 at 05:53:48 AM AWST Investigating The execution of integration workflows has encountered an interruption. Our engineering teams are deploying corrective measures to restore normal service operations. Posted on Jun 05, 2024 at 04:47:50 AM AWST Investigating We're continuing to analyze error traffic to determine the source of the issue. While the errors persist, we want to assure you that customer traffic is still processing. However, you may notice a reduction in processing rates during this time. Posted on Jun 05, 2024 at 04:42:34 AM AWST Investigating We're continuing to analyze error traffic to determine the source of the issue. Further updates will be provided as soon as possible. Posted on Jun 05, 2024 at 04:16:37 AM AWST Acknowledged We’ve identified an issue where users may observe integration workflows and events stuck in a queued status. The impact is limited to users accessing the service through the APP- environment. We’re investigating the issue and will provide an update as soon as possible. Posted on Jun 05, 2024 at 03:28:35 AM AWST JUN 06, 2024 PRIVACY MANAGEMENT - ASSESSMENT AUTOMATION SERVICE DEGRADATION Incident Duration From Jun 06, 2024 07:11:00 AM AWST to Jun 06, 2024 09:07:00 AM AWST (1 hr 56 mins 0 secs) Affected Components APP-EU: Admin Portal (APP-EU) Incident Status Updates Resolved Between 23:11 UTC on Jun 05th, and 01:07 UTC on June 06th (1 hour 55 mins), users may have observed degraded performance while accessing the Assessment Automation module or associated APIs when accessing the service through the APP-EU environment. The issue was resolved and an RCA will be provided. Posted on Jun 06, 2024 at 09:07:00 AM AWST INTEGRATIONS WORKFLOWS STUCK IN QUEUED STATUS Incident Duration From Jun 04, 2024 06:30:00 AM AWST to Jun 08, 2024 01:38:00 AM AWST (3 days 19 hours 8 mins) Affected Components APP: Admin Portal (APP) Incident Status Updates Resolved We are pleased to inform you that the hotfix was successfully deployed at 17:00 UTC. After a period of monitoring, we have confirmed that this incident has been resolved. If you are still experiencing issues, please contact our support teams quoting IM-578. Root cause analysis investigations have been initiated and an RCA will be provided. Posted on Jun 08, 2024 at 01:38:00 AM AWST Identified The hotfix has completed testing and deployment to the APP- environment will conclude within the next 120 minutes. Posted on Jun 07, 2024 at 11:23:27 PM AWST Identified Engineering teams have developed a hotfix to address the current issue. The hotfix is undergoing thorough regression testing to ensure its effectiveness, with a planned release on Friday, June 7th. We will provide a more accurate release timeframe tomorrow morning upon the successful completion of testing. Posted on Jun 07, 2024 at 04:57:24 AM AWST Identified We have identified the root cause of the issue affecting integration events submitted between 22:30 UTC on June 3rd and 23:30 UTC on June 4th. Our team is currently evaluating a permanent fix to reprocess the queued integration traffic. Following thorough testing, we will determine the timeline for deploying the corrective measures and will provide additional information and updates on Thursday, June 6th. Posted on Jun 06, 2024 at 05:52:34 AM AWST Identified Integration workflows and events submitted after 23:30 UTC on June 4th are processing as expected. The source of the problem for integration events submitted between 22:30 UTC on 03rd and 23:30 UTC on 04rd June has been identified through our collaboration with Azure. We are now working on determining the corrective actions required to resolve the processing of integration workflows and events submitted between 22:30 UTC on June 03rd to 23:30 UTC on June 4th. Posted on Jun 06, 2024 at 03:29:50 AM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. We are actively working with Microsoft Azure to troubleshoot and identify the root cause of the current issue affecting integration workflows stuck in queued status. Posted on Jun 05, 2024 at 10:32:17 PM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. We are actively working with Microsoft Azure to troubleshoot and identify the root cause of the current issue affecting integration workflows stuck in queued status. Posted on Jun 05, 2024 at 09:58:16 PM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. We have engaged MS Azure to help troubleshoot the root cause. Posted on Jun 05, 2024 at 07:48:14 PM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. Our engineering teams are actively analyzing error traffic to identify the root cause. Posted on Jun 05, 2024 at 04:52:20 PM AWST Observing Our team is still monitoring these queued integrations and will provide updates as soon as they become available. Posted on Jun 05, 2024 at 10:22:02 AM AWST Observing Corrective measures have been deployed, ensuring the successful processing of new integration workflows/events. Integrations submitted before the deployment of corrective measures will remain in a queued status until further notice. Our team is actively monitoring these queued integrations and will provide updates as soon as they become available. Posted on Jun 05, 2024 at 08:04:19 AM AWST Identified Our engineers are in the final stages of deploying corrective measures and are currently validating the results to resolve the ongoing service disruption. Posted on Jun 05, 2024 at 07:38:19 AM AWST Investigating Our engineering team is actively deploying corrective measures to address the ongoing interruption in service. Further updates will be provided as the deployment progresses. Posted on Jun 05, 2024 at 05:53:48 AM AWST Investigating The execution of integration workflows has encountered an interruption. Our engineering teams are deploying corrective measures to restore normal service operations. Posted on Jun 05, 2024 at 04:47:50 AM AWST Investigating We're continuing to analyze error traffic to determine the source of the issue. While the errors persist, we want to assure you that customer traffic is still processing. However, you may notice a reduction in processing rates during this time. Posted on Jun 05, 2024 at 04:42:34 AM AWST Investigating We're continuing to analyze error traffic to determine the source of the issue. Further updates will be provided as soon as possible. Posted on Jun 05, 2024 at 04:16:37 AM AWST Acknowledged We’ve identified an issue where users may observe integration workflows and events stuck in a queued status. The impact is limited to users accessing the service through the APP- environment. We’re investigating the issue and will provide an update as soon as possible. Posted on Jun 05, 2024 at 03:28:35 AM AWST JUN 05, 2024 INTEGRATIONS WORKFLOWS STUCK IN QUEUED STATUS Incident Duration From Jun 04, 2024 06:30:00 AM AWST to Jun 08, 2024 01:38:00 AM AWST (3 days 19 hours 8 mins) Affected Components APP: Admin Portal (APP) Incident Status Updates Resolved We are pleased to inform you that the hotfix was successfully deployed at 17:00 UTC. After a period of monitoring, we have confirmed that this incident has been resolved. If you are still experiencing issues, please contact our support teams quoting IM-578. Root cause analysis investigations have been initiated and an RCA will be provided. Posted on Jun 08, 2024 at 01:38:00 AM AWST Identified The hotfix has completed testing and deployment to the APP- environment will conclude within the next 120 minutes. Posted on Jun 07, 2024 at 11:23:27 PM AWST Identified Engineering teams have developed a hotfix to address the current issue. The hotfix is undergoing thorough regression testing to ensure its effectiveness, with a planned release on Friday, June 7th. We will provide a more accurate release timeframe tomorrow morning upon the successful completion of testing. Posted on Jun 07, 2024 at 04:57:24 AM AWST Identified We have identified the root cause of the issue affecting integration events submitted between 22:30 UTC on June 3rd and 23:30 UTC on June 4th. Our team is currently evaluating a permanent fix to reprocess the queued integration traffic. Following thorough testing, we will determine the timeline for deploying the corrective measures and will provide additional information and updates on Thursday, June 6th. Posted on Jun 06, 2024 at 05:52:34 AM AWST Identified Integration workflows and events submitted after 23:30 UTC on June 4th are processing as expected. The source of the problem for integration events submitted between 22:30 UTC on 03rd and 23:30 UTC on 04rd June has been identified through our collaboration with Azure. We are now working on determining the corrective actions required to resolve the processing of integration workflows and events submitted between 22:30 UTC on June 03rd to 23:30 UTC on June 4th. Posted on Jun 06, 2024 at 03:29:50 AM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. We are actively working with Microsoft Azure to troubleshoot and identify the root cause of the current issue affecting integration workflows stuck in queued status. Posted on Jun 05, 2024 at 10:32:17 PM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. We are actively working with Microsoft Azure to troubleshoot and identify the root cause of the current issue affecting integration workflows stuck in queued status. Posted on Jun 05, 2024 at 09:58:16 PM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. We have engaged MS Azure to help troubleshoot the root cause. Posted on Jun 05, 2024 at 07:48:14 PM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. Our engineering teams are actively analyzing error traffic to identify the root cause. Posted on Jun 05, 2024 at 04:52:20 PM AWST Observing Our team is still monitoring these queued integrations and will provide updates as soon as they become available. Posted on Jun 05, 2024 at 10:22:02 AM AWST Observing Corrective measures have been deployed, ensuring the successful processing of new integration workflows/events. Integrations submitted before the deployment of corrective measures will remain in a queued status until further notice. Our team is actively monitoring these queued integrations and will provide updates as soon as they become available. Posted on Jun 05, 2024 at 08:04:19 AM AWST Identified Our engineers are in the final stages of deploying corrective measures and are currently validating the results to resolve the ongoing service disruption. Posted on Jun 05, 2024 at 07:38:19 AM AWST Investigating Our engineering team is actively deploying corrective measures to address the ongoing interruption in service. Further updates will be provided as the deployment progresses. Posted on Jun 05, 2024 at 05:53:48 AM AWST Investigating The execution of integration workflows has encountered an interruption. Our engineering teams are deploying corrective measures to restore normal service operations. Posted on Jun 05, 2024 at 04:47:50 AM AWST Investigating We're continuing to analyze error traffic to determine the source of the issue. While the errors persist, we want to assure you that customer traffic is still processing. However, you may notice a reduction in processing rates during this time. Posted on Jun 05, 2024 at 04:42:34 AM AWST Investigating We're continuing to analyze error traffic to determine the source of the issue. Further updates will be provided as soon as possible. Posted on Jun 05, 2024 at 04:16:37 AM AWST Acknowledged We’ve identified an issue where users may observe integration workflows and events stuck in a queued status. The impact is limited to users accessing the service through the APP- environment. We’re investigating the issue and will provide an update as soon as possible. Posted on Jun 05, 2024 at 03:28:35 AM AWST JUN 04, 2024 INTEGRATIONS WORKFLOWS STUCK IN QUEUED STATUS Incident Duration From Jun 04, 2024 06:30:00 AM AWST to Jun 08, 2024 01:38:00 AM AWST (3 days 19 hours 8 mins) Affected Components APP: Admin Portal (APP) Incident Status Updates Resolved We are pleased to inform you that the hotfix was successfully deployed at 17:00 UTC. After a period of monitoring, we have confirmed that this incident has been resolved. If you are still experiencing issues, please contact our support teams quoting IM-578. Root cause analysis investigations have been initiated and an RCA will be provided. Posted on Jun 08, 2024 at 01:38:00 AM AWST Identified The hotfix has completed testing and deployment to the APP- environment will conclude within the next 120 minutes. Posted on Jun 07, 2024 at 11:23:27 PM AWST Identified Engineering teams have developed a hotfix to address the current issue. The hotfix is undergoing thorough regression testing to ensure its effectiveness, with a planned release on Friday, June 7th. We will provide a more accurate release timeframe tomorrow morning upon the successful completion of testing. Posted on Jun 07, 2024 at 04:57:24 AM AWST Identified We have identified the root cause of the issue affecting integration events submitted between 22:30 UTC on June 3rd and 23:30 UTC on June 4th. Our team is currently evaluating a permanent fix to reprocess the queued integration traffic. Following thorough testing, we will determine the timeline for deploying the corrective measures and will provide additional information and updates on Thursday, June 6th. Posted on Jun 06, 2024 at 05:52:34 AM AWST Identified Integration workflows and events submitted after 23:30 UTC on June 4th are processing as expected. The source of the problem for integration events submitted between 22:30 UTC on 03rd and 23:30 UTC on 04rd June has been identified through our collaboration with Azure. We are now working on determining the corrective actions required to resolve the processing of integration workflows and events submitted between 22:30 UTC on June 03rd to 23:30 UTC on June 4th. Posted on Jun 06, 2024 at 03:29:50 AM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. We are actively working with Microsoft Azure to troubleshoot and identify the root cause of the current issue affecting integration workflows stuck in queued status. Posted on Jun 05, 2024 at 10:32:17 PM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. We are actively working with Microsoft Azure to troubleshoot and identify the root cause of the current issue affecting integration workflows stuck in queued status. Posted on Jun 05, 2024 at 09:58:16 PM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. We have engaged MS Azure to help troubleshoot the root cause. Posted on Jun 05, 2024 at 07:48:14 PM AWST Observing Integration workflows and events submitted after 23:30 UTC on June 4th are now processing as expected. However, integrations submitted prior to the migration will remain queued until further notice. Our engineering teams are actively analyzing error traffic to identify the root cause. Posted on Jun 05, 2024 at 04:52:20 PM AWST Observing Our team is still monitoring these queued integrations and will provide updates as soon as they become available. Posted on Jun 05, 2024 at 10:22:02 AM AWST Observing Corrective measures have been deployed, ensuring the successful processing of new integration workflows/events. Integrations submitted before the deployment of corrective measures will remain in a queued status until further notice. Our team is actively monitoring these queued integrations and will provide updates as soon as they become available. Posted on Jun 05, 2024 at 08:04:19 AM AWST Identified Our engineers are in the final stages of deploying corrective measures and are currently validating the results to resolve the ongoing service disruption. Posted on Jun 05, 2024 at 07:38:19 AM AWST Investigating Our engineering team is actively deploying corrective measures to address the ongoing interruption in service. Further updates will be provided as the deployment progresses. Posted on Jun 05, 2024 at 05:53:48 AM AWST Investigating The execution of integration workflows has encountered an interruption. Our engineering teams are deploying corrective measures to restore normal service operations. Posted on Jun 05, 2024 at 04:47:50 AM AWST Investigating We're continuing to analyze error traffic to determine the source of the issue. While the errors persist, we want to assure you that customer traffic is still processing. However, you may notice a reduction in processing rates during this time. Posted on Jun 05, 2024 at 04:42:34 AM AWST Investigating We're continuing to analyze error traffic to determine the source of the issue. Further updates will be provided as soon as possible. Posted on Jun 05, 2024 at 04:16:37 AM AWST Acknowledged We’ve identified an issue where users may observe integration workflows and events stuck in a queued status. The impact is limited to users accessing the service through the APP- environment. We’re investigating the issue and will provide an update as soon as possible. Posted on Jun 05, 2024 at 03:28:35 AM AWST JUN 03, 2024 No incidents have been reported. JUN 02, 2024 No incidents have been reported. JUN 01, 2024 No incidents have been reported. MAY 31, 2024 No incidents have been reported. MAY 30, 2024 APP-APAC-PROD MONITORS DOWN Incident Duration From May 30, 2024 01:26:38 AM AWST to May 30, 2024 02:05:22 AM AWST (38 mins 44 secs) Affected Components APP-APAC: Admin Portal (APP-APAC), APP-APAC: Consent Receipts (APP-APAC), APP-APAC: Data Subject Portal (APP-APAC) Incident Status Updates Resolved We’ve identified an issue where users may have experienced Gateway failures, Notifications (emails) delivery delays/failures, Missing Translations, scheduled events not triggering, exports/uploads/downloads of documents failing, or being unable to access the environment when accessing the service through the APP-APAC environment. If you are still experiencing issues, please contact our support teams quoting IM-571. Root cause analysis investigations have been initiated and an RCA will be provided. Posted on May 30, 2024 at 02:05:22 AM AWST Show postmortem MAY 29, 2024 No incidents have been reported. MAY 28, 2024 UAT-DE CONSENT MANAGEMENT AND INCIDENT MODULE SERVICE DEGRADATION Incident Duration From May 28, 2024 03:21:49 PM AWST to May 28, 2024 04:01:00 PM AWST (39 mins 11 secs) Affected Components UAT-DE: Admin Portal (UAT-DE) Incident Status Updates Resolved We’ve identified an issue where users may experience the following behaviours when accessing the Consent Management portal through the UAT-DE environment. Failure in one of the following areas will occur: * Customers will be unable to load their preference centre portal * Authentication token requests will fail, rendering customers unable to utilize any of the main application APIs * Users will be unable to verify the status of the latest transactions for receipts * /api/consentmanager/v1/datasubjects will not be funtional * /api/consentmanager/v1/datasubjects/profiles will not be functional We’ve determined that the issue has been resolved. If you are still experiencing issues, please get in touch with our support teams quoting IM-567. Posted on May 28, 2024 at 04:01:00 PM AWST MAY 27, 2024 No incidents have been reported. MAY 26, 2024 No incidents have been reported. MAY 25, 2024 [IM - 565] CONNECTIVITY ISSUES WITH MYOT WEBSITE Incident Duration From May 24, 2024 10:38:00 PM AWST to May 25, 2024 02:53:44 AM AWST (4 hours 15 mins 44 secs) Affected Components APP: Admin Portal (APP), APP-DE: Admin Portal (APP-DE), APP-APAC: Admin Portal (APP-APAC), APP-EU: Admin Portal (APP-EU), APP-AU: Admin Portal (APP-AU), APP-UK: Admin Portal (APP-UK), APP-BR: Admin Portal (APP-BR), APP-CA: Admin Portal (APP-CA), APP-CH: Admin Portal (APP-CH), APP-FR: Admin Portal (APP-FR) and 4 more Incident Status Updates Resolved The issue has been resolved. If you are still experiencing issues, please contact our support teams quoting IM-565. Root cause analysis investigations have been initiated and an RCA will be provided. Posted on May 25, 2024 at 02:53:44 AM AWST Investigating We’re continuing to investigate the issue and will provide updates as the investigation progresses. Posted on May 25, 2024 at 01:57:27 AM AWST Investigating Our engineers continuing to investigate the configuration change made to the my.onetrust.com website. Further updates will be provided as soon as possible Posted on May 25, 2024 at 12:57:41 AM AWST Investigating We've identified that a recent configuration change to the my.onetrust.com website may be impacting a user’s ability to view Article pages. Affected users will be prompted with an “Oops” page, asking them to log in. We're validating the configuration change is the root cause before we attempt any corrective actions. We will provide updates as the investigation progresses. Posted on May 24, 2024 at 11:57:14 PM AWST Acknowledged We’ve identified that some users are experiencing connectivity issues when attempting to navigate the MyOT website. We’re investigating the issue and will provide an update as soon as possible. Posted on May 24, 2024 at 10:38:00 PM AWST MAY 24, 2024 [IM - 565] CONNECTIVITY ISSUES WITH MYOT WEBSITE Incident Duration From May 24, 2024 10:38:00 PM AWST to May 25, 2024 02:53:44 AM AWST (4 hours 15 mins 44 secs) Affected Components APP: Admin Portal (APP), APP-DE: Admin Portal (APP-DE), APP-APAC: Admin Portal (APP-APAC), APP-EU: Admin Portal (APP-EU), APP-AU: Admin Portal (APP-AU), APP-UK: Admin Portal (APP-UK), APP-BR: Admin Portal (APP-BR), APP-CA: Admin Portal (APP-CA), APP-CH: Admin Portal (APP-CH), APP-FR: Admin Portal (APP-FR) and 4 more Incident Status Updates Resolved The issue has been resolved. If you are still experiencing issues, please contact our support teams quoting IM-565. Root cause analysis investigations have been initiated and an RCA will be provided. Posted on May 25, 2024 at 02:53:44 AM AWST Investigating We’re continuing to investigate the issue and will provide updates as the investigation progresses. Posted on May 25, 2024 at 01:57:27 AM AWST Investigating Our engineers continuing to investigate the configuration change made to the my.onetrust.com website. Further updates will be provided as soon as possible Posted on May 25, 2024 at 12:57:41 AM AWST Investigating We've identified that a recent configuration change to the my.onetrust.com website may be impacting a user’s ability to view Article pages. Affected users will be prompted with an “Oops” page, asking them to log in. We're validating the configuration change is the root cause before we attempt any corrective actions. We will provide updates as the investigation progresses. Posted on May 24, 2024 at 11:57:14 PM AWST Acknowledged We’ve identified that some users are experiencing connectivity issues when attempting to navigate the MyOT website. We’re investigating the issue and will provide an update as soon as possible. Posted on May 24, 2024 at 10:38:00 PM AWST MAY 23, 2024 No incidents have been reported. MAY 22, 2024 No incidents have been reported. MAY 21, 2024 No incidents have been reported. MAY 20, 2024 No incidents have been reported. MAY 19, 2024 No incidents have been reported. MAY 18, 2024 No incidents have been reported. MAY 17, 2024 MS EXCHANGE SMTP FAILURES Incident Duration From May 16, 2024 01:46:56 AM AWST to May 17, 2024 06:24:09 PM AWST (1 day 16 hours 37 mins) Affected Components APP-DE: Admin Portal (APP-DE), APP-DE: Consent Receipts (APP-DE), APP-DE: Data Subject Portal (APP-DE), APP-UK: Admin Portal (APP-UK), APP-UK: Consent Receipts (APP-UK), APP-UK: Data Subject Portal (APP-UK), APP-BR: Data Subject Portal (APP-BR), APP-BR: Consent Receipts (APP-BR), APP-BR: Admin Portal (APP-BR) Incident Status Updates Resolved The issue has been resolved. If you are still experiencing issues, please contact our support teams quoting IM-544. Root cause analysis investigations have been initiated and an RCA will be provided. Posted on May 17, 2024 at 06:24:09 PM AWST Observing The issue has been resolved. If you are still experiencing issues, please contact our support teams quoting IM-544. Root cause analysis investigations have been initiated and an RCA will be provided. Posted on May 17, 2024 at 05:12:37 PM AWST Observing The intermittent issues with e-mail delivery are ongoing. We continue to work with the impacted customers to restore full service. Updates will be provided upon milestones. Posted on May 17, 2024 at 04:36:09 AM AWST Identified Our support teams are reaching out to affected customers to help recreate their connection to the service. Further updates will be provided as soon as possible. Posted on May 16, 2024 at 03:33:40 PM AWST Identified Our engineering teams have identified that some customers have changed their custom SMTP configuration and hence getting authentication errors when attempting to transmit emails, this issue is not from our end, we are continuing to investigate and further updates will be provided as soon as possible. Posted on May 16, 2024 at 01:30:17 PM AWST Investigating Our engineering teams continue to investigate and further updates will be provided as soon as possible. Posted on May 16, 2024 at 11:00:43 AM AWST Investigating Our Engineering teams have identified this as an issue with Microsoft. We are currently engaged with their support team to resolve this issue. Posted on May 16, 2024 at 04:36:06 AM AWST Acknowledged Some customers on APP-DE, APP-UK, and APP-BR may be facing intermittent issues with email delivery, we have engaged with Microsoft to investigate and resolve this problem. Posted on May 16, 2024 at 01:46:56 AM AWST Show postmortem MAY 16, 2024 MS EXCHANGE SMTP FAILURES Incident Duration From May 16, 2024 01:46:56 AM AWST to May 17, 2024 06:24:09 PM AWST (1 day 16 hours 37 mins) Affected Components APP-DE: Admin Portal (APP-DE), APP-DE: Consent Receipts (APP-DE), APP-DE: Data Subject Portal (APP-DE), APP-UK: Admin Portal (APP-UK), APP-UK: Consent Receipts (APP-UK), APP-UK: Data Subject Portal (APP-UK), APP-BR: Data Subject Portal (APP-BR), APP-BR: Consent Receipts (APP-BR), APP-BR: Admin Portal (APP-BR) Incident Status Updates Resolved The issue has been resolved. If you are still experiencing issues, please contact our support teams quoting IM-544. Root cause analysis investigations have been initiated and an RCA will be provided. Posted on May 17, 2024 at 06:24:09 PM AWST Observing The issue has been resolved. If you are still experiencing issues, please contact our support teams quoting IM-544. Root cause analysis investigations have been initiated and an RCA will be provided. Posted on May 17, 2024 at 05:12:37 PM AWST Observing The intermittent issues with e-mail delivery are ongoing. We continue to work with the impacted customers to restore full service. Updates will be provided upon milestones. Posted on May 17, 2024 at 04:36:09 AM AWST Identified Our support teams are reaching out to affected customers to help recreate their connection to the service. Further updates will be provided as soon as possible. Posted on May 16, 2024 at 03:33:40 PM AWST Identified Our engineering teams have identified that some customers have changed their custom SMTP configuration and hence getting authentication errors when attempting to transmit emails, this issue is not from our end, we are continuing to investigate and further updates will be provided as soon as possible. Posted on May 16, 2024 at 01:30:17 PM AWST Investigating Our engineering teams continue to investigate and further updates will be provided as soon as possible. Posted on May 16, 2024 at 11:00:43 AM AWST Investigating Our Engineering teams have identified this as an issue with Microsoft. We are currently engaged with their support team to resolve this issue. Posted on May 16, 2024 at 04:36:06 AM AWST Acknowledged Some customers on APP-DE, APP-UK, and APP-BR may be facing intermittent issues with email delivery, we have engaged with Microsoft to investigate and resolve this problem. Posted on May 16, 2024 at 01:46:56 AM AWST Show postmortem MAY 15, 2024 APP-JP MULTIPLE MODULE SERVICE DEGRADATION Incident Duration From May 15, 2024 11:05:00 PM AWST to May 15, 2024 11:41:00 PM AWST (36 mins 0 secs) Affected Components APP-JP: Admin Portal (APP-JP) Incident Status Updates Resolved Between 15:05 and 15:41 UTC, users may have observed degradation within the Vendor Risk Management, GRC, DSAR, and Reporting modules. The incident occurred due to a scheduled event which took place outside of a maintenance window. If you are still experiencing issues, please contact our support teams quoting IM-548. Root cause analysis investigations have been initiated and an RCA will be provided. Posted on May 15, 2024 at 11:41:00 PM AWST MAY 14, 2024 No incidents have been reported. Time shown is in your local time zone- Australia/Perth. Change Time zone Home Incident History Powered by Site24x7 StatusIQ