Is Didomi Down Right Now? Check if there is a current outage ongoing.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and we are reverting the changes.

We are currently investigating reports of loading issues affecting the Web CTV SDK on a limited number of devices. Our team is actively working on identifying the cause and resolving the issue. We will provide updates as soon as more information becomes available.

This incident has been resolved.

A fix has been implemented and we are monitoring the results

The issue has been identified and a fix is being implemented

We are currently investigating the issue

The incident has been resolved. During the incident, the Platform API (responsible for managing notice configurations for the Didomi Console and API clients) and the Didomi Console were temporarily impacted with higher latency or partial unavailability. All other services, including the Consents API, consent notices, and consent collection, were not affected and were operating normally.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are investigating elevated error rates. Some services such as the Didomi Console may be affected.

The incident has been resolved. During the incident, the Platform API (responsible for managing notice configurations for the Didomi Console) and the Didomi Console were temporarily impacted with higher latency or partial unavailability. All other services, including the Consents API, consent notices, and consent collection, were not affected.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are investigating elevated error rates. Some services such as the Didomi Console may be affected.

The incident has been resolved. The impact on the incident was limited to notices with some combinations of IAB TCF vendors and publisher restrictions. A more detailed incident report will be available in the following days.

Fix has been implemented, monitoring in progress

We are investigating issues with notices that include IAB TCF vendors with special features.

We identified an issue causing an elevated error rate for the Privacy Center API, which is used by our CMP for features like analytics and cross-device tracking. The incident began around 03:10 UTC and was fully resolved by 03:40 UTC. Additionally, the API was unresponsive between 03:16 UTC and 03:18 UTC. The issue has been addressed. Consent notices remained fully operational during this period, and direct calls to our API on api.didomi.io were not impacted.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are investigating an issue where users can't login or access the console due to an issue with authentication/authorization and memberships.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Our monitoring system detected a failure in the processing of analytical events starting yesterday evening.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

This incident has been resolved. After careful monitoring, we can confirm that the impact of this issue was minimal, affecting less than 1% of incoming requests.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

On 12/5/2023 from 1:36pm UTC to 04:52pm UTC, the Didomi Web SDK failed to fully load on the first page visited by users on a small number of websites with the IAB TCF and Google Additional Consent enabled. The issue was fixed by rolling back to the previous Web SDK version at 04:52pm UTC on 12/5/2023. A post-mortem analysis was done and can be obtained by reaching out to our team.

From 12/7/2023 5:16pm UTC to 12/8/2023 10:50am UTC, the Didomi Web SDK included the latest version of the lodash library. This update may cause compatibility issues for clients who were using an earlier version of lodash that loaded prior to the instantiation of the Web SDK. In such cases, the Web SDK lodash version could override the website version, potentially leading to breaking changes in some of lodash's APIs and in some functionalities of websites. This update did not impact the display of notices or the collection of consent. This issue arose following a recent release of the Web SDK. We are currently investigating to determine the root cause of these compatibility challenges and to put in place necessary processes and checks to ensure such an incident does not occur in the future.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

On August 17, 2023, we received reports from some clients that their Web SDK Google AMP notices were generating Google-related errors (e.g., 1.2, 3.3 and 2.1.A errors; also 1.1, 2.1.B and 2.2.B errors) . The cause of the errors was traced to the consent string only containing legitimate interest but without consent information being stored. As a result, the number of Limited Ads being displayed increased. We identified the root cause of the issue being a code update that was released on Aug 15, 2023 10:10am GMT+0100 related to ongoing work to improve the performance of our Web SDK. We reverted the code in order to resolve the issue on Aug 17, 2023 12:14m GMT+0100. The bug causing the issue was related to a race condition between computing the consent and storing the consent string and sending it to AMP. Any notices collecting new consent during this window of time most likely would have experienced this issue; pre-existing consent that had been given would not have been impacted. Limited Ads were only displayed for users whose consent was collected after Aug 15, 2023 10:10am GMT+0100.

This incident has been resolved.

The team is testing and deploying a fix. We'll report here as more information becomes available.

We are experiencing an issue with displaying GDPR notices to visitors loading the Web SDK from outside of EU countries. The issue only impacts notices that do not apply GDPR globally and that apply GDPR specifically to non-EU countries. We have identified the issue and are working on a fix. Mobile and other SDKs are not impacted.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Between 12:03 and 12:59 UTC, we experienced degraded performance with our Privacy Center API. We have successfully resolved the issue, and all services are now fully operational and functioning normally.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are investigating reports of a lack of new metrics being reported.

This incident has been resolved.

Our cloud provider has resolved the issue and Compliance Reports are now available again.

The outage is a result of issues faced by our cloud provider that have impacted the infrastructure on which our services rely. Our engineering team is in close coordination with our cloud provider to understand the extent of the problem and to ensure that services are restored in the shortest timeframe possible.

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

The incident has been resolved. It was caused by a new feature that we released. We will be conducting a post-mortem of this incident to analyze its root cause and ensure that it does not happen again. Clients that may have been impacted by the incident will be contacted directly by our team.

A fix has been implemented and we are monitoring the results. Notices can now be published without any issue.

We are still investigating the source of the incident.

Custom vendors with only IAB purposes are not showing in notices after publishing consent notices. Consent notices that were already published prior to the incident are not impacted. We are currently investigating the issue and will update here as more information becomes available.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are investigating reports of delayed/unprocessed webhook integration events

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are investigating reports of higher than average response time for the Consents API

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are investigating reports of higher than average response time for the Consents API

This incident has been resolved.

Some of the notices deployed between 10:30 and 12:30 UTC are no longer showing in the Console. This is a visual bug. The data is safe and we are working on making them visible again.

This incident has been resolved.

A fix has been implemented. We are monitoring the results.

We have identified an issue which has impacted the performance of our API as well as the usage of the Console. We are working on a fix.

Between 7/6/2022 1am CET and 7/7/2022 1pm CET, new data was not collected and shown in Compliance Reports due to an issue with our proxy provider. Compliance Reports were still available with data collected before 7/6/2022. The issue is now fixed.

Due to our authentication provider experiencing an outage the Didomi console could not be accessed for 10 minutes between 09:00 and 09:10 CET. The outage was resolved and the console is now accessible again.

This incident has been resolved.

The issue was identified and we are now processing the backlog

We are currently investigating reports of delayed/unprocessed webhook integration events

This incident has been resolved.

Fix worked. We are monitoring the situation as it settles. We expect all data to be available throughout the next 2 hours.

A fix has been deployed. The ETA for the missing metrics being available is 6 hours.

The issue has been identified. We are working on a fix.

We are investigating reports of a lack of new metrics being reported.

This incident has been resolved. Some more details on the timing: We correlated a deployment that took place around 3:45-3:55pm CET with our monitoring and reports of customers experiencing issues that we started receiving around 5:00pm CET. To be on the safe side, we decided to rollback the code changes around 5:20pm CET. Since this time, our customers who had reported the issue confirmed the issue had been resolved on their side, and we also ceased to see errors on our side. We are working to ensure that it does not happen again.

We have identified some notices not displaying consistently on Web and Mobile platforms starting 4pm CET due to the notice configuration not loading. The issue was due to rate limitations after cache was cleared and affected a limited number of users and websites/mobile apps. The issue is fixed and we are monitoring the situation. We will update with more details soon.

The issue has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented. We will continue to monitor.

The issue has been identified and we are working on fix.

We are currently investigating an issue with the console load. This issue does not affect any of Didomi's APIs.

Issue is now resolved.

We have identified the issue and are working on a solution at the moment.

We are investigating reports of downtime in our console and admin API. Consents API and SDKs are not affected.

This incident has been resolved.

The system is back to normal, we are investigating the incident.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We have identified the source of the issue and we are working on a fix.

We have identified a possible issue when trying to invite users to an organization. We are investigating.

On Dec 9th, 2021, the "log4j vulnerability" (https://www.f5.com/labs/articles/threat-intelligence/explaining-the-widespread-log4j-vulnerability) was disclosed that allows remote code execution on many common Java-based applications. Didomi mostly uses Node.js for our backend systems and, after conducting an audit, we have determined that we are not affected by this vulnerability. We are monitoring AWS' fixes on the topic (https://aws.amazon.com/security/security-bulletins/AWS-2021-006/) and most critical services that Didomi uses in production (EC2, S3, Cloudfront, etc.) have already been patched.

We have finished processing the backlog. Integrations are back to normal.

The processing of the event backlog is ongoing.

We have scaled up our infrastructure to expedite the processing of the event backlog.

We are seeing a delay in the delivery of events towards integrations.

We are currently investigating this issue.

The Consents API reported an increased average response time on 9/3 and 9/4, between 10pm UTC and 5am UTC. The increased latency was due to a small number of requests being particularly slow to process as they were impacting users with a very high number of consents events, As a result, we saw an increase in our average latency. Most organizations were not impacted and the average latency for most organizations was stable. The issue has been resolved. We will be implementing more monitoring and safeguards to ensure that this issue does not happen again in the coming days.

The Didomi Console was unavailable from ~4pm UTC to ~4:50pm UTC on 9/6. We identified the source cause as being a deployment of a new module that introduced an error and fixed it. Everything is back to normal and the Console is now operating normally. We will be investigating how to add more monitoring and testing to ensure that the issue does not happen again.

Between 2021/7/7 6:16pm CET and 2021/7/8 4:13pm CET, some websites were affected by a JavaScript Error that was preventing the notice from closing when the user clicked the Agree or Disagree buttons. A new version of the Web SDK that caused the error was deployed to production on 2021/7/7 at 6:16pm CET. The previous version of the Web SDK was restored and deployed back to production on 2021/7/8 at 4:13pm CET. Affected clients' websites were confirmed as working properly after the rollback. The cause for the error was an interaction of a polyfills library (prototype.js v1.7) with our SDK where the polyfills library overloaded the standard JavaScript Array filter method with a non standard findAll function. It looks like the version 1.7 of this library has a bug because the current version 1.7.3 is not conflicting with our SDK. What we are improving on our side to ensure it does not happen again: - Include the affected client’s polyfills library in out automated regression tests for the Web SDK to make sure that overloads of standard JavaScript methods are not creating issues; - Create automated tests for our clients websites that we can run before we deploy a new version of our SDK to the production environment.

Analytics are now loading normally in the Console.

The Analytics dashboard provider (Cluvio) that we are using is having a major outage. We are monitoring the situation with them.

The analytics dashboards are not loading. We are investigating the issue.

This incident has been resolved.

We have fixed the issue and are monitoring the results. Emails are being sent correctly at the moment.

We are currently investigating an issue where users are unable to log into a Preference Center using their email address.

This incident has been resolved.

We have processed all the queued events and we are now operating normally. We will continue monitoring the situation.

The Consents API latency is now back to normal (< 100ms) and we are currently processing the consent events that were queued.

We are continuing to work on a fix for this issue.

Due to AWS experiencing issues in eu-central-1, we are currently seeing an increased average response time for the Consents API. Consent events are also delayed for webhooks and other integrations. We are working on mitigating the impact of AWS' unavailability. There is no impact on Consent Notices or Preference Centers.

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

Our scrapers for compliance reports are currently down. Compliance reports are still working properly on data collected before today but are not updated with new data at the moment. We are investigating the issue.

This incident has been resolved.

The issue has been fixed and we are now monitoring the systems. Our analytics is now current. Our advanced analytics (beta) has partial data Fri 5/28 that will be recovered next week.

We have identified the source of the issue and are working on a fix.

Our analytics in the Console are currently delayed. We are investigating the root cause.

This incident has been resolved and the Console is now back up and running!

The Didomi Console is showing "Didomi is loading..." and not loading correctly. We are currently investigating the issue.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

We are currently investigating this issue.

Google Consent Mode (https://support.google.com/analytics/answer/9976101?hl=en) was accidentally enabled for Web notices published between April 8th, ˜5pm CET and April 9th, 12pm CET. As Google Consent Mode was enabled without a Google Analytics vendor associated, the Didomi Web SDK signaled to Google Analytics that consent was not given and analytics was disabled for users, resulting in a loss of analytics data. For web notices published before April 8th, ˜5pm CET or after April 9th, 12pm CET, the issue was not present. For notices published between April 8th, ˜5pm CET and April 9th, 12pm CET and not published again after April 9th, 12pm CET, the issue was fixed on April 14th and customers can expect loss of analytics data for the full period from April, 8th to April, 14th. Didomi will conduct a full post-mortem on the issue to understand why it happened and update our internal processes to ensure that such issues do not happen again.

This incident has been resolved.

The situation has been stable since our last update and the incident is now fully resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified (some long-running queries are using all the IO resources of our analytics cluster) and we are working on fixing it.

We are currently investigating an issue with report generation in our analytics platform. Reports in the Didomi Console are currently very slow to display or not displaying at all. Events collection is not impacted and there is no data loss.