Admiral Status | Status

Admiral Status | Status

Back
Apr 10, 2026 10:50 AM EDT Resolved after 4d

CSProtect Showing to Non-Blockers

Impacted:
Engage

Updates

  • Apr 14, 2026 5:04 PM EDT

    A postmortem for the incident is below. Please reach out to Support for further questions.

     

    Overview

    On April 10th between 10:36am and 10:51am ET some non-adblocking visitors were shown a Client-Side Protect (CSProtect) anti-adblocking message incorrectly. This incident was isolated to a small portion of our network and in most cases users could bypass this message by clicking a continue button.

     

    Incident Summary

    Admiral continuously improves the effectiveness of its products. An improvement to our CSProtect feature was deployed on April 9th. Following reports of a few minor issues, and out of an abundance of caution, we initiated a rollback on April 10th. Unfortunately this rollback introduced an incompatibility issue with the newer install tag and the previous script version, causing the engagement to trigger for a large percentage of visitors.

     

    Root Cause Analysis

    The CSProtect improvements required specific, non-backwards-compatible updates to the code that publishers embed on their website. Although the initial deployment safely handled this compatibility, the subsequent rollback caused an incompatible mix of versions. This accidental incompatibility caused the CSProtect message to display incorrectly.

     

    Mitigation Steps

    The incompatible rollback was completed at 10:36am ET. An investigation began at 10:40am and once the incompatibility was identified, the correct, compatible version was immediately redeployed at 10:47am. This re-deployment completed at 10:51am, successfully ending the incident and returning CSProtect impressions baseline numbers.

     

    Preventive Measures

    We are immediately prioritizing several processes and improvements to prevent future deployment incompatibilities. Going forward, version compatibility will be verified throughout the deployment and rollback process and rollbacks will undergo increased scrutiny to ensure safety for all publishers. We sincerely apologize for this incident. We hold ourselves to a high standard and a technical error of this nature is unacceptable. We understand the trust you place in us as a technology partner, and we're dedicated to preventing this kind of issue in the future.

    Resolved
  • Apr 10, 2026 11:24 AM EDT (4 days, 5 hours, and 39 minutes earlier)

    We're confident new visitors are not seeing CSProtect without an adblocker. If you're still seeing it we recommend you refreshing your browser cache and trying again.

    Resolved
  • Apr 10, 2026 10:57 AM EDT (27 minutes earlier)

    The fix has finished rolling out and we CSProtect is no longer showing to non-adblockers. We will continue to monitor.

    Monitoring
  • Apr 10, 2026 10:50 AM EDT (6 minutes earlier)

    We're aware of an issue starting at 10:40am ET where some non-adblocking visitors are seeing CSProtect. We've already deployed a fix and it's rolling out to all visitors now.

    Identified