Amplience experienced a notice incident on May 28, 2026 affecting CMS, lasting 11h 7m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 28, 2026, 08:53 PM UTC
We are investigating an issue in Dynamic Content, search indexes are unavailable
- identified May 28, 2026, 08:53 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring May 28, 2026, 09:06 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved May 29, 2026, 08:00 AM UTC
This incident has been resolved.
- postmortem Jun 08, 2026, 03:05 PM UTC
**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.