Is Amplience down?

We are currently investigating scheduled editions that failed to publish between 05.07 - 05.52 BST

A third-party provider that we use for a backend service carried out emergency maintenance earlier today, which impacted some of our services. During this period, we identified a small number of Editions that failed to Publish. We have contacted the affected customers directly and provided a workaround to allow them to proceed. We also observed degraded performance impacting DC-API during the same timeframe. Our teams are continuing to monitor the situation closely while we work with the provider to understand the full impact and prevent any recurrence.

We are investigating an issue where some scheduled editions are failing to publish.

We have identified the root cause of a known issue and are currently implementing a fix. Further information to follow.

The fix has been deployed and the impact is currently being monitored.

We can confirm the fix has been released and validated

**Incident Start Time:** 13 May 2026 **Incident End Time:** 29 May 2026 ‌ Between 13 May and 29 May 2026, we identified an issue affecting a subset of assets uploaded through automated workflows, where metadata such as image dimensions, file type, and alt text was not indexed correctly within our search platform. ‌ Assets uploaded manually through the user interface were not impacted. A fix was released on 29 May 2026 to correct the indexing behaviour for newly uploaded assets. ‌ Following the release of the fix, Amplience teams completed a retrospective re-indexing activity for affected assets to restore missing metadata records. ‌ **Root Cause** ‌ The issue was traced to a change introduced in a DAM API release on 13 May 2026, which altered how metadata was written during the indexing process for certain uploaded assets. ‌ **Corrective Actions** ‌ * Increasing validation and review around indexing-related configuration changes * Improving logging and monitoring for metadata indexing processes

We are investigating an issue in Dynamic Content, search indexes are unavailable

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

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

This incident has been resolved.

**Incident Start Time:** 19.49 BST **Incident End Time:** 22.03 BST  **Issue Summary:** An incident occurred within Dynamic Content that required a rollback to a previous version. In the Development Tab of Dynamic Content, search indexes were returning zero records.  **Root Cause:** The issue was introduced in a recent Dynamic Content release, which introduced a new Content Security Policy \(CSP\) header. This header unintentionally blocked Algolia search index requests, resulting in searches returning no records.   **Corrective Actions:** * Improve validation and regression testing around CSP-related changes to ensure third-party services such as Algolia continue to function as expected.  * Whitelist the security headers in a future release.

Users may experience an issue when switching repositories, where the selected repository updates but the displayed content does not reflect the newly selected repository.

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

This incident has been resolved.

**Incident Start Time:** Friday, 8th May, 09.57 BST **Incident End Time:** Monday, 12th May, 14.18 BST ‌ **Issue Summary:** An incident occurred within Dynamic Content that required an immediate rollback to a previous version. Users were unable to navigate through different Repositories.  ‌ **Root Cause:** The issue was introduced in the latest Content Management App release, which included a new multi-select feature for the repository library. The feature caused unintended behaviour that impacted repository navigation functionality. ‌ **Corrective Actions:** * Review release verification procedures to improve early detection of UI interaction issues.