Amplience Status Page

May 29, 2026 · resolved May 29

We can confirm the fix has been released and validated

May 28, 2026 · resolved May 29

This incident has been resolved.

May 11, 2026 · resolved May 11

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

Apr 22, 2026 · resolved Apr 22

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

Feb 19, 2026 · resolved Feb 19

# Issue Content Hub Assets Not Displaying ## Postmortem **Issue Summary** On Thursday, 19 February 2026, our monitoring systems detected an issue affecting the loading of assets within the platform. Shortly after, we received customer support tickets reporting problems with Content Hub and asset loading. This issue did not affect any live, published content. Our team immediately began investigating the cause and worked to restore normal performance as quickly as possible. ‌ **Root Cause** A query that consumed a large amount of memory caused a temporary issue with asset loading in the platform. Our team has reviewed the issue and has taken steps to reduce the likelihood of similar issues in the future. ‌ **Resolution** Our engineering team quickly restarted the affected service, restoring full platform functionality. ‌ **Corrective Actions** * We’ve reviewed our processes to strengthen system reliability and ensure faster recovery if any unexpected issues arise in the future.