Amplience logo

Amplience Status Page

Content Management · monitored by Alert24

amplience.com
All Systems Operational

Is Amplience down right now?

No — Amplience is up. All systems operational as of Jul 13, 11:45 PM UTC.

Current Status

All Systems Operational

View Amplience status page ↗

Components

Content Hub
Operational
Dynamic Content
Operational
Dynamic Media
Operational
Support
Operational
Documentation hub
Operational
Workforce AI
Operational

Recent Incidents

Degraded performance with DC-API

minor

Jul 6, 2026 · resolved Jul 6

This incident is now resolved.

Processing Job's Intermittent Failures

minor

Jun 30, 2026 · resolved Jun 30

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

Scheduled Editions not publishing

minor

Jun 11, 2026 · resolved Jun 11

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

Bulk indexing degraded performance

none

May 29, 2026 · resolved May 29

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

Algolia requests blocked in Dynamic Content

none

May 28, 2026 · resolved May 29

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

Get alerted when Amplience goes down

Alert24 monitors Amplience and 3,700+ other cloud and SaaS providers. When an outage is detected, it updates your status page automatically and pages your on-call team. No manual updates at 2 AM.

Start free — no credit card

Amplience status — frequently asked questions

Is Amplience down right now?

No — Amplience is up. All systems operational as of Jul 13, 11:45 PM UTC.

What is Amplience's current status?

Amplience: All Systems Operational. Alert24 checks Amplience's status page continuously and can notify you the moment it changes.

How do I get alerted when Amplience goes down?

Alert24 monitors Amplience and 3,700+ other cloud and SaaS providers. When an outage is detected it updates your status page automatically and pages your on-call team — no manual checks. Start free at alert24.net.

More Content Management status pages