Amplience incident

Scheduled Editions not publishing

Minor Resolved View vendor source →

Amplience experienced a minor incident on June 11, 2026 affecting Dynamic Content, lasting 1h 7m. The incident has been resolved; the full update timeline is below.

Started
Jun 11, 2026, 06:20 AM UTC
Resolved
Jun 11, 2026, 07:28 AM UTC
Duration
1h 7m
Detected by Pingoru
Jun 11, 2026, 06:20 AM UTC

Affected components

Dynamic Content

Update timeline

  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.