Intermittent delivery of Dynamic Content

Incident Report for Amplience

Postmortem

Update 03/03/2025

Incident Start Time: 17.15 GMT 

Incident End Time: 20.30 GMT 

Issue summary

An incident occurred where some customers using C1 for Content Delivery experienced 403 errors on localized content. 

Root cause

Despite extensive investigation, we were unable to determine a definitive root cause. Logs and historical data did not reveal a consistent triggering event or anomaly in platform behavior.

We’ve taken some actions:

  • Implemented enhanced monitoring to proactively detect the issue and prevent customer disruption.
  • Created a run book outlining diagnostic steps for a quicker triage in case of reoccurance 

Next Steps

  • Continue monitoring for any recccurences 
  • The incident has been escalated to our Engineering team, with a focus on improving platform reliability and performance.
  • Root Cause Analysis will be revisited if new evidence emerges.

While the root cause remains unknown, the steps above will help mitigate future occurrences. 

‌If you would like to discuss this further, please contact your customer success manager (csteam@amplience.com)

==============================================

20/02/2025 Update: The investigation into the root cause is still ongoing. We have identified some contributing factors, but we have not yet confirmed the root cause.

We will provide an update once the investigation is complete and RCA is finalised.

We appreciate your patience.

Posted Feb 20, 2025 - 09:31 GMT

Resolved

This incident has been resolved.
Posted Feb 13, 2025 - 20:17 GMT

Monitoring

A fix has been implemented and we are monitoring the results.
Posted Feb 13, 2025 - 20:10 GMT

Identified

The issue has been identified and a fix is being implemented.
Posted Feb 13, 2025 - 19:43 GMT

Update

Our Operations team are still investigating the issue
Posted Feb 13, 2025 - 18:59 GMT

Investigating

We are currently investigating reports of intermittent delivery of Dynamic Content.
Posted Feb 13, 2025 - 18:04 GMT
This incident affected: Dynamic Content.