Amplience experienced a minor incident on June 11, 2026 affecting CMS, lasting 1h 7m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jun 11, 2026, 06:20 AM UTC
We are currently investigating scheduled editions that failed to publish between 05.07 - 05.52 BST
- resolved Jun 11, 2026, 07:28 AM UTC
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.
- postmortem Jun 23, 2026, 09:59 AM UTC
**Incident Start Time:** 05.07 BST **Incident End Time:** 05.52 BST **Issue Summary:** An incident occurred with one of our back end databases. This caused degraded performance to DC-API and some Dynamic Content Editions were in a stuck status. **Root Cause:** Some inefficient queries to our back end database caused our primary node to fail over to our secondary node. **Corrective Actions:** We have already introduced corrective mitigations with additional indexes and working with MongoDB we have further improvements planned.