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 Oct 12, 4:53 AM UTC.

Current Status

All Systems Operational

View Amplience status page ↗

Components

DAM
Operational
Support
Operational
Dynamic Media
Operational
Documentation hub
Operational
CMS
Operational
Workforce
Operational

Recent Incidents

No assets showing in Content Hub & Asset Library

major

Sep 24, 2026 · resolved Sep 24

**Incident Start Time** 24 September 2026, 18:23 BST **Incident End Time** 24 September 2026, 18:45 BST ‌ **Issue Summary** ‌ On 24 September 2026, users experienced an issue accessing assets within DAM and the CMS Asset Library. Whilst existing published content was not impacted, users were unable to view assets within DAM, and asset libraries appeared empty in CMS when attempted to import assets into content. ‌ **Root Cause** ‌ Our investigation identified a failure within one of the shards of our search and indexing service \(SOLR\), which is responsible for making assets discoverable within DAM and the CMS Asset Library. Recovering the affected shard restored functionality.  Further investigation identified that indexing larger text-based files contributed to increased memory consumption, which we believe caused the service failure. ‌ **Corrective Actions** * We have reviewed and updated our monitoring and alerting to improve our ability to detect and respond to potential issues. * We have identified a change to the indexing process that will reduce memory consumption. This fix is currently being prioritised for release. * We will continue monitoring indexing activity and memory consumption to assess the effectiveness of these improvements.

Flows Processing Interruption

none

Sep 15, 2026 · resolved Sep 15

During a routine release of improved Workforce & Flows features, we experienced a brief interruption between 16:08 and 16:12 BST. During this period, some Flows failed to complete as expected. The issue was short-lived, and normal processing resumed once the release activity completed. The impact was limited in duration, with no ongoing service degradation identified following the release.

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.

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 Oct 12, 4:53 AM 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