Statusfield LogoStatusfield
Amplience status
Amplience logo and current status indicator

Amplience Incident History

Operational

amplience.com ↗3 top-level components

checked Oct 31, 2026 2:43 PM UTC · Amplience's official status page

Amplience is up and running.

Amplience is currently operational with all systems functioning normally.

All components operational

Be the first to know

Statusfield watches Amplience alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.

30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.

Amplience incident history

3 reports published by Amplience in the last 30 days

October 26, 2026

Broccoli2Shell vulnerability (CVE-2026-111497)

Last update

  1. resolvedOct 28 · 11:49 UTC

    Our engineering and security teams have completed their assessment of the Broccoli2Shell vulnerability (CVE-2026-111497). Appropriate mitigations have been implemented to address the identified risks. We consider this matter resolved and will continue to monitor for any further developments.

Reported by Amplience on their status page.

October 22, 2026

PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619)

Last update

  1. resolvedOct 31 · 07:03 UTC

    Our engineering and security teams have completed their assessment of the PHP2Shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619). Appropriate mitigations have been implemented to address the identified risks. We consider this matter resolved and will continue to monitor for any further developments.

Reported by Amplience on their status page.

September 24, 2026

No assets showing in Content Hub & Asset Library

Last update

  1. postmortemOct 8 · 16:18 UTC

    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.

Reported by Amplience on their status page.