Admiral Status | Status

Admiral Status | Status

Back
Feb 9, 2026 9:57 AM EST Resolved after 11d

Script Delivery Impacting Multiple Services

Impacted:
Connect
Measure
Transact
Engage
Consent

Updates

  • Feb 20, 2026 2:37 PM EST

    We appreciate your patience. After an in-depth analysis by our team we've published the following postmortem for the incident:

     

    Overview

    On February 9th, 2026 between 9:36am ET and 10:23am many of Admiral's services were impacted by an internal critical service failure preventing the functionality of our visitor-facing products.

     

    Incident Summary

    When our JavaScript does not load core functionality across Measure, Engage, Connect, Transact, Visitor Copilot and Consent was unavailable. The design of our JavaScript snippet ensured that visitors were not shown errors and did not experience extended load times.

     

    Root Cause Analysis

    An internal service change led to a critical database cluster becoming degraded preventing the service from responding to requests. This service was necessary for serving our publisher-customized JavaScript and the underlying failure caused JavaScript requests to fail.

     

    Mitigation Steps

    A rollback of the recent change was attempted but did not complete as a result of the database degradation. The offending database traffic was blocked allowing the database to recover and for the rollback to complete.

     

    Preventive Measures

    Admiral's platform relies on many mitigations to prevent downstream service failures from affecting public traffic and these mitigations were initially effective in masking the degradation, however, they were insufficient for the duration of the incident. We have prioritized and completed significant improvements to ensure our platform can operate unaffected during longer periods of instability. We sincerely apologize for any inconvenience caused by this incident.

    Resolved
  • Feb 9, 2026 11:24 AM EST (1 week, 4 days, 3 hours, and 13 minutes earlier)

    The affected services have fully recovered as of 15:23 UTC.

    Resolved
  • Feb 9, 2026 10:22 AM EST (1 hour and 2 minutes earlier)

    The incident has been successfully mitigated resulting in traffic returning to normal. We are continuing to monitor.

    Monitoring
  • Feb 9, 2026 10:11 AM EST (10 minutes earlier)

    We've identified the issue and are applying mitigations to restore service as quickly as possible.

    Identified
  • Feb 9, 2026 9:57 AM EST (14 minutes earlier)

    We are currently investigating issues across several services.

    Investigating