Akeneo incident

Erroneous reference entity pagination links

Minor Resolved View vendor source →
Started
Feb 18, 2026, 11:10 AM UTC
Resolved
Feb 18, 2026, 04:23 PM UTC
Duration
5h 13m
Detected by Pingoru
Feb 18, 2026, 11:10 AM UTC

Affected components

GraphQL API

Update timeline

  1. identified Feb 18, 2026, 11:10 AM UTC

    We are currently investigating an issue affecting GraphQL API pagination links specifically for reference entity records. This issue impacts all GraphQL API users worldwide, who include reference records in their products or product models (about 1% of our customer base), since Feb 17th, 6pm CET. Workaround: To obtain a valid URL, you can manually remove the #ref_entity suffix from the returned pagination link. We have identified the root cause, and are currently deploying a fix. We apologize for the disruption to your workflow.

  2. resolved Feb 18, 2026, 04:23 PM UTC

    The fix has been successfully deployed. All GraphQL pagination links generated since 4:30 PM CET are now fully functional. We appreciate your patience and understanding while we worked to resolve this issue.

Looking to track Akeneo downtime and outages?

Pingoru polls Akeneo's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Akeneo reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Akeneo alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Akeneo for free

5 free monitors · No credit card required