Amplience Outage History

Amplience is up right now

Amplience had 32 outages in the last 2 years totaling 25h 53m of downtime — averaging 1.3 incidents per month.

There were 32 Amplience outages since October 29, 2024 totaling 25h 53m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.amplience.com

Major September 24, 2026

No assets showing in Content Hub & Asset Library

Detected by Pingoru
Sep 24, 2026, 05:37 PM UTC
Resolved
Sep 24, 2026, 05:46 PM UTC
Duration
9m
Affected: Content HubDynamic Content
Timeline · 2 updates
  1. investigating Sep 24, 2026, 05:37 PM UTC

    We’re aware of an issue where assets are not displaying in Content Hub. This also impacts users importing images into content using CMS. Our teams are actively investigating the cause. At this time, we can confirm that already published assets are not impacted. Further updates will follow as soon as we have more information.

  2. resolved Sep 24, 2026, 05:46 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice September 16, 2026

Flows Processing Interruption

Detected by Pingoru
Sep 16, 2026, 12:43 PM UTC
Resolved
Sep 15, 2026, 03:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Sep 16, 2026, 12:43 PM UTC

    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.

Read the full incident report →

Minor July 6, 2026

Degraded performance with DC-API

Detected by Pingoru
Jul 06, 2026, 04:08 PM UTC
Resolved
Jul 06, 2026, 04:58 PM UTC
Duration
50m
Affected: Dynamic Content
Timeline · 3 updates
  1. investigating Jul 06, 2026, 04:08 PM UTC

    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.

  2. monitoring Jul 06, 2026, 04:17 PM UTC

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

  3. resolved Jul 06, 2026, 04:58 PM UTC

    This incident is now resolved.

Read the full incident report →

Minor June 11, 2026

Scheduled Editions not publishing

Detected by Pingoru
Jun 11, 2026, 06:20 AM UTC
Resolved
Jun 11, 2026, 07:28 AM UTC
Duration
1h 7m
Affected: Dynamic Content
Timeline · 3 updates
  1. investigating Jun 11, 2026, 06:20 AM UTC

    We are currently investigating scheduled editions that failed to publish between 05.07 - 05.52 BST

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

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

Read the full incident report →

Notice May 28, 2026

Algolia requests blocked in Dynamic Content

Detected by Pingoru
May 28, 2026, 08:53 PM UTC
Resolved
May 29, 2026, 08:00 AM UTC
Duration
11h 7m
Affected: Dynamic Content
Timeline · 5 updates
  1. investigating May 28, 2026, 08:53 PM UTC

    We are investigating an issue in Dynamic Content, search indexes are unavailable

  2. identified May 28, 2026, 08:53 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring May 28, 2026, 09:06 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved May 29, 2026, 08:00 AM UTC

    This incident has been resolved.

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

Read the full incident report →

Major May 11, 2026

Issue with switching repositories

Detected by Pingoru
May 11, 2026, 12:53 PM UTC
Resolved
May 11, 2026, 03:24 PM UTC
Duration
2h 30m
Affected: Dynamic Content
Timeline · 4 updates
  1. identified May 11, 2026, 12:53 PM UTC

    Users may experience an issue when switching repositories, where the selected repository updates but the displayed content does not reflect the newly selected repository.

  2. monitoring May 11, 2026, 01:28 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved May 11, 2026, 03:24 PM UTC

    This incident has been resolved.

  4. postmortem May 15, 2026, 11:36 AM UTC

    **Incident Start Time:** Friday, 8th May, 09.57 BST **Incident End Time:** Monday, 12th May, 14.18 BST ‌ **Issue Summary:** An incident occurred within Dynamic Content that required an immediate rollback to a previous version. Users were unable to navigate through different Repositories. ‌ **Root Cause:** The issue was introduced in the latest Content Management App release, which included a new multi-select feature for the repository library. The feature caused unintended behaviour that impacted repository navigation functionality. ‌ **Corrective Actions:** * Review release verification procedures to improve early detection of UI interaction issues.

Read the full incident report →

Notice April 22, 2026

app.amplience.net login issues

Detected by Pingoru
Apr 22, 2026, 07:05 PM UTC
Resolved
Apr 22, 2026, 07:24 PM UTC
Duration
19m
Affected: Dynamic Content
Timeline · 3 updates
  1. monitoring Apr 22, 2026, 07:05 PM UTC

    We experienced a minor outage with app.amplience.com logging into Dynamic Content. The spike to performance has since subsided and we a now monitoring the situation. We can confirm that Dynamic Content is now accessible.

  2. resolved Apr 22, 2026, 07:24 PM UTC

    The issue is resolved. app.amplience.net logins are working as expected

  3. postmortem Apr 29, 2026, 09:19 AM UTC

    **Incident Start Date** 19:40 BST **Incident End Date** 19:54 BST ‌ **Issue Summary** On Wednesday evening, users were unable to log into [app.amplience.net](http://app.amplience.net) for a period of 14 minutes. ‌ **Root Cause** Our third-party authentication provider, Auth0, experienced a DNS outage caused by a misconfiguration on their side. This incident also impacted some of our alerting capabilities, which we are currently reviewing with our partners. ‌ **Resolution** Auth0 resolved their DNS issue, restoring normal authentication services. **Corrective Actions** * Review and strengthen alerting to ensure visibility is maintained during third-party DNS-related incidents * Work with Auth0 to understand the full scope of the misconfiguration and their preventative measures

Read the full incident report →

Minor February 19, 2026

Content Hub Not Displaying Assets

Detected by Pingoru
Feb 19, 2026, 04:07 PM UTC
Resolved
Feb 19, 2026, 04:07 PM UTC
Duration
—
Timeline · 1 update
  1. monitoring Feb 19, 2026, 04:07 PM UTC

    Feb 19, 16:07 GMT Resolved - We have monitored this issue and confirm we are fully operational Feb 19, 15:19 GMT Monitoring - We have identified the issue and Content Hub is now displaying assets, we are continuing to monitor the situation. Feb 19, 15:01 GMT Investigating - We are currently investigating an issue with assets not displaying on Content Hub

Read the full incident report →

Minor January 22, 2026

Issue Editing Nested, Localized Content

Detected by Pingoru
Jan 22, 2026, 05:02 PM UTC
Resolved
Jan 22, 2026, 05:02 PM UTC
Duration
—
Timeline · 1 update
  1. monitoring Jan 22, 2026, 05:02 PM UTC

    Jan 22, 17:02 GMT Resolved - A patch has now been released. Jan 22, 15:27 GMT Update - We are continuing to work on a fix for this issue. Jan 22, 15:23 GMT Identified - The issue has been identified and a fix is being implemented. Jan 22, 15:23 GMT Investigating - Users may experience issue editing nested content within the content form.

Read the full incident report →

Minor December 5, 2025

Platform Access Issues

Detected by Pingoru
Dec 05, 2025, 10:17 AM UTC
Resolved
Dec 05, 2025, 09:00 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Dec 05, 2025, 10:17 AM UTC

    Some users may have experienced issues accessing ondemand.amplience.com and support.amplience.com. Email [email protected] remained operational during this time. To minimise any impact, we temporarily rerouted ondemand traffic away from the affected service. Traffic has now been restored to the normal route. Both issues were caused by a disruption affecting a third-party service. All issues are now resolved.

Read the full incident report →

Minor November 25, 2025

Issues with Dynamic Media Purging

Detected by Pingoru
Nov 25, 2025, 10:44 AM UTC
Resolved
Nov 25, 2025, 10:44 AM UTC
Duration
—
Timeline · 1 update
  1. monitoring Nov 25, 2025, 10:44 AM UTC

    Nov 25, 10:44 GMT Resolved - This incident has been resolved, and purging functionality is now operating as expected Nov 25, 10:09 GMT Monitoring - We are currently observing an issue with one of our upstream partners, Akamai, which is experiencing an outage. As a result this will impact purging functionality within the Dynamic Media app. Our team is actively monitoring the situation and will provide further updates as they become available.

Read the full incident report →

Minor November 18, 2025

Dynamic Imaging Performance Issues

Detected by Pingoru
Nov 18, 2025, 07:27 PM UTC
Resolved
Nov 18, 2025, 07:27 PM UTC
Duration
—
Timeline · 1 update
  1. monitoring Nov 18, 2025, 07:27 PM UTC

    Nov 18, 19:27 GMT Resolved - We are satisfied the Cloudflare outage is resolved after our extended monitoring period. We can confirm we were not impacted and did not see any degraded performance. Our platform traffic is stable and we will continue to monitor our healthy service to ensure we remain operational. Nov 18, 13:25 GMT Monitoring - We continue to monitor our own infrastructure and can confirm that our own delivery services are not impacted. Traffic remains diverted away from Cloudflare. Nov 18, 12:15 GMT Identified - We are currently observing an issue with one of our upstream partners, Cloudflare, which is experiencing an outage. As a preventative measure, our platform is actively rebalancing traffic. Our systems continue to operate as expected, and customers may experience some intermittent performance degradation during this period. We are closely monitoring the situation and will continue to track Cloudflare’s recovery.

Read the full incident report →

Minor October 22, 2025

Unable to remove components from Dynamic Content

Detected by Pingoru
Oct 22, 2025, 03:09 PM UTC
Resolved
Oct 22, 2025, 03:09 PM UTC
Duration
—
Timeline · 1 update
  1. monitoring Oct 22, 2025, 03:09 PM UTC

    Oct 22, 16:09 BST Resolved - We can confirm that the affected feature has been rolled back and functionality has returned to normal. Oct 22, 16:06 BST Identified - We’ve identified an issue with a recent release that’s impacting content creation. Our team is currently rolling back the affected feature, and we’ll confirm once the rollback is complete

Read the full incident report →

Minor October 20, 2025

Delayed messages when contacting Support

Detected by Pingoru
Oct 20, 2025, 09:44 AM UTC
Resolved
Oct 20, 2025, 09:44 AM UTC
Duration
—
Timeline · 1 update
  1. monitoring Oct 20, 2025, 09:44 AM UTC

    Oct 20, 10:44 BST Resolved - The incident has been resolved. Oct 20, 09:57 BST Investigating - Users may be experiencing slower than normal response times when contacting support. We are working with our provider to resolve this as soon as possible.

Read the full incident report →

Minor October 20, 2025

Content Delivery Performance Issues

Detected by Pingoru
Oct 20, 2025, 09:43 AM UTC
Resolved
Oct 20, 2025, 09:43 AM UTC
Duration
—
Timeline · 1 update
  1. monitoring Oct 20, 2025, 09:43 AM UTC

    Oct 20, 10:43 BST Resolved - This incident is now resolved. Oct 20, 10:32 BST Monitoring - Our upstream partners have restored service, and we are monitoring. Oct 20, 10:04 BST Identified - We are currently seeing degraded Content Delivery performance in one region. Traffic is being redirected away from the affected region, and we are working with our upstream partners to restore normal service.

Read the full incident report →

Major September 19, 2025

Media Delivery (assets) disruption

Detected by Pingoru
Sep 19, 2025, 08:42 PM UTC
Resolved
Sep 19, 2025, 09:54 PM UTC
Duration
1h 12m
Affected: Content HubDynamic Media
Timeline · 4 updates
  1. identified Sep 19, 2025, 08:42 PM UTC

    We are experiencing an outage with our Media Delivery (assets) service, which impacts published assets. We have identified the fault and now investigating the fix

  2. monitoring Sep 19, 2025, 08:51 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Sep 19, 2025, 09:54 PM UTC

    The incident has been resolved

  4. postmortem Sep 22, 2025, 03:26 PM UTC

    Incident Start Time: 21:22 BST Incident End Time: 21:39 BST **Issue Summary:** ‌ On 19th September, we experienced a disruption to our media delivery service. Impacted customers saw images failing to load. ‌ **Root Cause:** ‌ Amplience operates a multi-layer CDN infrastructure to ensure continuous delivery. A change related to Cloudflare affected approximately 0.04% of our daily requests. ‌ Our automatic failover logic initiated during this incident, diverting traffic away from Cloudflare to Akamai. ‌ ‌ **Corrective Actions:** ‌ * While the overall percentage of requests impacted was low, the experience for affected customers was significant. We are fine-tuning our process to make the failover more efficient. * We are awaiting a full root cause analysis \(RCA\) from our provider, Cloudflare. ‌ ‌ If you have any questions or would like to discuss this further, please reach out to your Customer Success Manager or contact us at [[email protected]](mailto:[email protected]).

Read the full incident report →

Critical May 13, 2025

Freshservice outage

Detected by Pingoru
May 13, 2025, 02:36 PM UTC
Resolved
May 13, 2025, 03:00 PM UTC
Duration
23m
Affected: Support
Timeline · 3 updates
  1. investigating May 13, 2025, 02:36 PM UTC

    We are currently investigating this issue.

  2. monitoring May 13, 2025, 02:40 PM UTC

    Freshservice is now working as normal

  3. resolved May 13, 2025, 03:00 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 7, 2025

Manual Upload not available in Content Hub

Detected by Pingoru
Apr 07, 2025, 10:32 AM UTC
Resolved
Apr 07, 2025, 10:39 AM UTC
Duration
6m
Affected: Content Hub
Timeline · 3 updates
  1. investigating Apr 07, 2025, 10:32 AM UTC

    We are currently investigating an issue with a third-party provider that is impacting manual uploads within Content Hub. Please note that bulk ingestion via FTP remains operational and can be used as an alternative in the meantime.

  2. monitoring Apr 07, 2025, 10:35 AM UTC

    Service appears to be restored by the third party, and we will continue to observe

  3. resolved Apr 07, 2025, 10:39 AM UTC

    This Incident is resolved

Read the full incident report →