Akeneo incident

Failing product import jobs

Minor Resolved View vendor source →

Akeneo experienced a minor incident on October 20, 2025 affecting UI and REST API, lasting 1d 4h. The incident has been resolved; the full update timeline is below.

Started
Oct 20, 2025, 07:24 AM UTC
Resolved
Oct 21, 2025, 12:21 PM UTC
Duration
1d 4h
Detected by Pingoru
Oct 20, 2025, 07:24 AM UTC

Affected components

UIREST API

Update timeline

  1. investigating Oct 20, 2025, 09:24 AM UTC

    We detected an issue with product import jobs unduly failing. All our regions are impacted, with about 10% of our customers experiencing the issue. We will provide further information along our investigation. Thank you for your patience and understanding.

  2. identified Oct 20, 2025, 09:53 AM UTC

    The issue has been identified, and a fix will be deployed shortly.

  3. identified Oct 20, 2025, 02:17 PM UTC

    The deployment of the fix is taking longer than expected, given the context of the in-progress outage on AWS services today (https://health.aws.amazon.com/health/status), impacting one of our upstream service providers. We'll continue monitoring the deployment, and provide updates as more information becomes available. Thank you for your patience and understanding.

  4. identified Oct 20, 2025, 04:02 PM UTC

    The deployment of the fix is still delayed by the open incident on AWS (https://health.aws.amazon.com/health/status) impacting one of our upstream third party service providers. A workaround is applicable for customers experiencing the unduly failing jobs. In such a case, you can restart the job, and it will run normally, with a usual execution time, as our PIM production infrastructure is not impacted by the AWS incident. We'll continue monitoring the deployment, and provide updates as more information becomes available. Thank you for your patience and understanding.

  5. monitoring Oct 21, 2025, 10:46 AM UTC

    The fix is deployed, we keep monitoring the PIM platform. Thanks for your patience and understanding.

  6. resolved Oct 21, 2025, 12:21 PM UTC

    This incident is now resolved, with all import jobs now running as expected. Thanks for your patience and understanding.