Resolved after 5 hours 13 minutes, affecting GraphQL API, on February 18, 2026.
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.
Affected components
Update timeline
- 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.
- 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.
Your product runs on more than Akeneo
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services