Amplience incident

Unable to access Dynamic Content

Critical Resolved View vendor source →

Amplience experienced a critical incident on January 31, 2024 affecting Dynamic Content, lasting 17m. The incident has been resolved; the full update timeline is below.

Started
Jan 31, 2024, 01:02 PM UTC
Resolved
Jan 31, 2024, 01:19 PM UTC
Duration
17m
Detected by Pingoru
Jan 31, 2024, 01:02 PM UTC

Affected components

Dynamic Content

Update timeline

  1. investigating Jan 31, 2024, 01:02 PM UTC

    We are currently investigating an issue accessing Dynamic Content

  2. monitoring Jan 31, 2024, 01:16 PM UTC

    Service to Dynamic Content has been restored and we will continue monitoring

  3. resolved Jan 31, 2024, 01:19 PM UTC

    We have marked the incident as resolved. If any users continue to experience issues, please contact [email protected]

  4. postmortem Feb 02, 2024, 09:51 AM UTC

    **Incident Start Time: 12.51 GMT** **Incident End Time: 13.16 GMT** ‌ **Issue Summary** In the course of a routine release, we encountered unforeseen SSH errors and a build failure, leading to a 25-minute outage in Dynamic Content. **Root Cause** A build failed during release. Rebuilding this resolved the issue. **Corrective actions** We are enhancing the release plan by incorporating additional checkpoints and exploring alternative deployment tools. ‌ ‌If you would like to discuss this further, please contact your customer success manager \([[email protected]](mailto:[email protected])\)