Admiral outages and incidents
Outage and incident data over the last 30 days for Admiral.
There have been 0 outages or incidents for Admiral in the last 30 days.
Severity Breakdown:
Tired of searching for status updates?
Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!
Sign Up NowComponents and Services Monitored for Admiral
Outlogger tracks the status of these components for Xero:
| Component | Status |
|---|---|
| Consent | Active |
| Engage | Active |
| Measure | Active |
| Publisher Dashboard | Active |
| Reports | Active |
| Transact | Active |
Latest Admiral outages and incidents.
View the latest incidents for Admiral and check for official updates:
Engages and Consents not showing up
Description: We noticed that Engages and Consents aren't showing up for multiple customers. We rolled back a recent change and resolved the issue.
Status: Resolved
Impact: Critical | Started At: June 27, 2022, 7:30 p.m.
Updates:
-
Time: June 27, 2022, 7:53 p.m.Status: ResolvedUpdate: We noticed that Engages and Consents aren't showing up for multiple customers. We rolled back a recent change and resolved the issue.
Consent models not showing up
Description: This incident has been resolved.
Status: Resolved
Impact: Critical | Started At: June 15, 2022, 3:35 p.m.
Updates:
-
Time: June 15, 2022, 3:56 p.m.Status: ResolvedUpdate: This incident has been resolved.
-
Time: June 15, 2022, 3:41 p.m.Status: MonitoringUpdate: We've implemented a fix and we are deploying it now.
-
Time: June 15, 2022, 3:35 p.m.Status: InvestigatingUpdate: We are currently investigating an issue that's preventing Consent models from showing up
app.getadmiral.com is unavailable
Description: This incident has been resolved.
Status: Resolved
Impact: Critical | Started At: May 19, 2022, 1:01 p.m.
Updates:
-
Time: May 19, 2022, 1:21 p.m.Status: ResolvedUpdate: This incident has been resolved.
-
Time: May 19, 2022, 1:13 p.m.Status: MonitoringUpdate: A fix has been implemented and we are monitoring the results.
-
Time: May 19, 2022, 1:10 p.m.Status: IdentifiedUpdate: The issue has been identified and a fix is being implemented.
Consent Model Data not Being Reported
Description: We've rolled back a recent change which seems to have returned the data back to normal. We believe models were still being shown correctly, and only the reporting of the models being shown was affected.
Status: Resolved
Impact: Minor | Started At: May 3, 2022, 6:28 p.m.
Updates:
-
Time: May 3, 2022, 6:41 p.m.Status: ResolvedUpdate: We've rolled back a recent change which seems to have returned the data back to normal. We believe models were still being shown correctly, and only the reporting of the models being shown was affected.
-
Time: May 3, 2022, 6:28 p.m.Status: InvestigatingUpdate: We are currently investigating a drop in consent model data
Engages being shown to unexpected users
Description: **If your site was affected by this incident you will have received an email from** [**[email protected]**](mailto:[email protected]) **notifying you.** At 9:20am on March 30th we automatically migrated all customers to our new web application that had not yet done so manually. This migration unfortunately did not account for an older implementation of multi-engage Journeys that still exists on a small subset of live customer sites \(59 sites total\). This caused the second Engage in these Journeys to display to all visitors on every page view. In virtually every case this engagement was asking users to disable their adblocker. Soon after the migration we recognized the misconfiguration and began the process of restoring a backup of the database that stores Journey configurations. The backup completed at 11am and all misconfigured Journeys were restored to their original state. This rollback reverted the database to its state at 8am on the same day. Any changes made between 8am and 11am on March 30th should be resubmitted if you wish for them to persist. If you have any questions about this incident please email [[email protected]](mailto:[email protected]).
Status: Postmortem
Impact: Major | Started At: March 30, 2022, 2 p.m.
Updates:
-
Time: March 31, 2022, 3:27 p.m.Status: PostmortemUpdate: **If your site was affected by this incident you will have received an email from** [**[email protected]**](mailto:[email protected]) **notifying you.** At 9:20am on March 30th we automatically migrated all customers to our new web application that had not yet done so manually. This migration unfortunately did not account for an older implementation of multi-engage Journeys that still exists on a small subset of live customer sites \(59 sites total\). This caused the second Engage in these Journeys to display to all visitors on every page view. In virtually every case this engagement was asking users to disable their adblocker. Soon after the migration we recognized the misconfiguration and began the process of restoring a backup of the database that stores Journey configurations. The backup completed at 11am and all misconfigured Journeys were restored to their original state. This rollback reverted the database to its state at 8am on the same day. Any changes made between 8am and 11am on March 30th should be resubmitted if you wish for them to persist. If you have any questions about this incident please email [[email protected]](mailto:[email protected]).
-
Time: March 30, 2022, 4:12 p.m.Status: ResolvedUpdate: We will be restoring all affected Engages back to their original targeting
