Amplience incident

Degraded performance in Content Delivery

Minor Resolved View vendor source →

Amplience experienced a minor incident on February 20, 2023 affecting Dynamic Content, lasting 1h 27m. The incident has been resolved; the full update timeline is below.

Started
Feb 20, 2023, 01:12 PM UTC
Resolved
Feb 20, 2023, 02:40 PM UTC
Duration
1h 27m
Detected by Pingoru
Feb 20, 2023, 01:12 PM UTC

Affected components

Dynamic Content

Update timeline

  1. identified Feb 20, 2023, 01:12 PM UTC

    We have identified an issue with degraded performance with our Content delivery Service.

  2. identified Feb 20, 2023, 02:22 PM UTC

    We have implemented a fix and are currently monitoring

  3. resolved Feb 20, 2023, 02:40 PM UTC

    This incident has been resolved.

  4. postmortem Feb 22, 2023, 10:20 AM UTC

    **Issue summary** On the morning of February 20th, we experienced latency in our Content Delivery V2 service. **Root Causes** We were alerted to the increase in traffic and based on our threshold metric the service had started to autoscale but we reached some limits. The majority of traffic was coming from the EU region so we were able to direct traffic to a different region whilst working to increase those limits. **Corrective actions** In the short term, we are reviewing our quotas and alerts. In the long term as part of our continued service improvement process, our Engineering team are reviewing the Content Delivery v2 service ‌If you would like to discuss this further, please contact your customer success manager \([email protected]\)