Is Amplience down?

We're currently experiencing an elevated level of API errors and are actively investigating the issue. During this time, customers may experience slower response times or intermittent API errors. We apologise for the disruption and will provide further updates as soon as we have more information.

Service has been restored, and we are continuing to monitor the platform closely to ensure stability.

This incident is now resolved.

We are aware that a subset of legacy processing jobs are experiencing intermittent issues. We have identified the cause and are working to restore normal service. We will provide further updates as progress continues.

We have successfully implemented a fix.

**Incident Start Time** 9 June 2026, 00:00 UTC **Incident End Time** 30 June 2026, 17:37 UTC ‌ **Issue Summary** A small number of legacy Processing Jobs intermittently failed to run at their scheduled times. As a result, some automated asset processing tasks, such as set creation and metadata updates, were not completed as expected. ‌ **Root Cause** The issue was caused by a planned authentication change introduced by Bitbucket as part of the retirement of its app password authentication method. During scheduled transition periods, authentication requests using the deprecated method were temporarily rejected, preventing some Processing Jobs from downloading the scripts required to execute. ‌ **Corrective Actions** We have implemented a permanent fix to remove the dependency on the deprecated authentication method. As a result, these Processing Jobs are no longer affected by Bitbucket's scheduled transition periods. We have identified all Processing Jobs impacted during the incident and are replaying them where appropriate to ensure the expected processing is completed. If you have any questions or believe your workflows require additional review, please contact our Support team at [support.amplience.com](http://support.amplience.com).

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.

**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.

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