Amplience incident

Degraded performance in Dynamic Content

Major Resolved View vendor source →

Amplience experienced a major incident on August 19, 2024 affecting Dynamic Content, lasting 1h 11m. The incident has been resolved; the full update timeline is below.

Started
Aug 19, 2024, 02:25 PM UTC
Resolved
Aug 19, 2024, 03:36 PM UTC
Duration
1h 11m
Detected by Pingoru
Aug 19, 2024, 02:25 PM UTC

Affected components

Dynamic Content

Update timeline

  1. investigating Aug 19, 2024, 02:25 PM UTC

    We are currently investigating degraded performance within our Dynamic Content App. Users are experiencing problems publishing and using the asset tab feature.

  2. identified Aug 19, 2024, 03:32 PM UTC

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

  3. monitoring Aug 19, 2024, 03:35 PM UTC

    A fix has been implemented and we are monitoring.

  4. resolved Aug 19, 2024, 03:36 PM UTC

    This incident is now resolved

  5. postmortem Aug 21, 2024, 04:19 PM UTC

    **Issue** An Incident occurred within Dynamic Content that necessitated an immediate rollback to a previous version. The main symptoms impacted content creation, accessing the content library and publishing. ‌ **Root Cause** A recent Dynamic Content release introduced a new header causing CORS \(Cross-Origin Resource Sharing\) errors. ‌ **Corrective Actions** To restore service, we immediately rolled back to a previous version.